I struggled for a while to find specifically which 12 were being referred to. That may be because the above linked page seems to have been written specifically to be as in coherent to follow as possible (this could be sleep tiredness kicking in.) So I think I've clocked them from the contents and relisted them here for future use.
- Perceivable : Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language
- Perceivable: Provide alternatives for time-based media.
- Perceivable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
- Perceivable: Make it easier for users to see and hear content including separating foreground from background.
- Operable: Make all functionality available from a keyboard.
- Operable:Provide users enough time to read and use content.
- Operable: Do not design content in a way that is known to cause seizures.
- Operable: Provide ways to help users navigate, find content, and determine where they are.
- Understandable: Make text content readable and understandable.
- Understandable: Make Web pages appear and operate in predictable ways.
- Understandable: Help users avoid and correct mistakes.
- Robust: Maximize compatibility with current and future user agents, including assistive technologies.
Now I have already talkeed about this but I'm a big 'Keyboard' advocate, I find it weird that peoople make things that cannot be worked only by the keyboard. This especially true of very specific use software. I think that by taking this into consideration you're designing and getting your solution working for a whole host of people: power users, blind people, people with mobility issues. There are such a vast number of reasons why mouse and tracker ball usage can exclude people that I always think this seems like a no brainer, however it's not always easy to convince a team.
No comments:
Post a Comment