3. • easily understandable valuable content
• semantically rich markup
• the >right< semantic markup (if you think
you found a wicket cool new use for a
definition list - think again...)
Saturday, March 7, 2009
4. • good “speaking” URLs
• Link-texts that make sense by themselves
• valuable alternative texts on Images
Saturday, March 7, 2009
5. You know Usability?
Accessibility === Usability!
except it’s for everyone...
Saturday, March 7, 2009
6. • use the tab and enter key only
- can you navigate your site?
• disable Javascript
- are you still able to do everything?
• zoom the page in the Browser (yes IE6 too)
does the Layout still work?
Saturday, March 7, 2009
7. • zoom the screen
are you able to realize all the changes?
• close your eyes
...
Saturday, March 7, 2009
12. • used in the wrong way CSS can reduce
accessibility
• display:none and visibility:hidden
hide content - also from Screenreaders
• does your hidden content show up
on :focus or only on :hover?
• CSS only Dropdown Navigation is a misuse!
CSS is for design. Javascript is for behavior.
Saturday, March 7, 2009
14. • it’s evil - right?
• nope...
• ... not necessarily
Saturday, March 7, 2009
15. • used correctly, Javascript is not only nicely
accessible but can even enhance accessibility
• subtile animations can make otherwise
confusing workflows easier to understand
(subtile! Or motion sickness kicks in...)
• hiding currently unused elements and
highlighting the important ones can make
your layout appear far less complex
Saturday, March 7, 2009
16. • progressively enhance the default non-js
layout and hijack the existing controls to do
their job in the browser instead on the
server
• create new interaction elements, that offer
functionality only available with Javascript,
by Javascript and make sure they are tab-
able
• don’t break the natural tab order by setting
a positive tab index. A tab index of 0 can
make non tab-able elements accessible too!
Saturday, March 7, 2009
18. • is there still someone believing that?
• most Screenreaders actually handle
Javascript very well!
• they just don’t know if you don’t tell them
Saturday, March 7, 2009
19. • inform Screenreaders about what’s
happening
• a logic and understandable workflow is the
easiest thing to test without a Screenreader
• focus() the next logical element
Saturday, March 7, 2009