Tuesday, August 21, 2012

Section 508 Accessibility Compliance

In July I haven't committed a single line of code

Rescue Time indicated that I was using Word and Outlook (hate with passion) most of the time to produce some documentation. Here is extract from Section 508 (wiki):
Amendment that requires Federal agencies to make their electronic and information technology accessible to people with disabilities comparable to the access to and use of the information and data by Federal employees who are not individuals with disabilities; 

Among many other things it required each element to accessible using keyboard. I actually suggested to surround divs an tag rather than assigned a tabindex (that would require changing the tabindex of all elements present on the website).

After giving it a second thought I realized there must be some kind of tabindex=auto. And here we are tabindex=0 is your friend, my friend!

Here is jsFiddle:

And here is insightful discussion on StackOverflow with critical examples when it breaks IE. General advice: use your common sense:
Finally HTML5 offers pretty much no guarantees about the tab order between elements that have a tabindex of 0, merely stating that it should follow platform conventions.
Following platform conventions is enough reason for me, don't really need to worry about reinventing the wheel. 

PS. Here is my "normal" efficiency graph:
Yeah, just signup using this link.

0 komentarze:

Post a Comment