1 Reply Latest reply on Feb 9, 2010 11:09 AM by blankfield

    Key redundant input mechanisms for accessibility


      Dreamveaver CS4 Mac OS 10.4.11


      I have all accessibility choices (4) checked in the preferences.


      When I insert images I don’t get a dialogue box that asks for a key redundant input mechanisms as I’m led to believe I should.


      When I run the accessibility validation report I get problems with my nav bar and an Angie’s list link supplied by the company.


      The info bubble says I should have “onmousedown paired with onkeydown”. I assume there is supposed to be a key value in there somewhere as well.


      I don’t know how to “pair” things in code.


      Is there a way to call up the accessibility features after a graphic has been placed to fill in a onkeydown value?


        • 1. Re: Key redundant input mechanisms for accessibility
          blankfield Level 1

          Thank You for responding


          part 1


          I don't know about the tab key for accessibility. I thought that when one has the preferences turned on for accessibility one should get a dialogue box to enter an onkeydown equivalent for a onclick instruction when inserting a navigation bar. The book I'm learning from says "prompts you to add Accessibility tags and attributes". I guess attributes doesn't include onkeydown info.


          part 2


          A sample of the code that needs to have onkeydown access:


          <td width="47%"><a href="javascript:;" target="_top" onclick="MM_nbGroup('down','group1','Home','images/button_2_home_down.jpg',1)" onmouseover="MM_nbGroup('over','Home','images/button_2_home_over.jpg','',1)" onmouseout="MM_nbGroup('out')"><img src="images/button_2_home.jpg" alt="Home" name="Home" hspace="3" border="0" id="Home"  /></a></td>


          I looked at the w3school logical operators (thank you for the link, I didn't find that before). Does that mean I should use the "or" which is "||" operator for onkeydown?


          And so something like this?


          onclick="MM_nbGroup('down','group1','Home','images/button_2_home_down.jpg',1) || onkeydown= "MM_nbGroup('down','group1','Home','F1')


          Where "F1" is the function key.


          I realize this is probably laughable, but it's hard to find specific examples.


          As far as tag inspector - behaviors panel, I kind of thought that might be it but so far I couldn't figure it out.


          Thanks again