While traditionally accessibility focuses on making the web more accessible for users with permanent disabilities, a focus on accessibility can deliver an improved user experience for everyone, including those with a temporary or circumstantial disability.
Accessibility should permeate the entire design and development process, rather than being something that you only think about after everything else has been defined and implemented. You should focus on accessibility when you are:
While the accessibility of some of the existing Vanilla design patterns is still being improved, all new and updated patterns should meet WCAG 2.0level AA.
Ideally, prototypes should be tested with real users with real accessibility issues, but that is not always possible.
If you are not able to test design patterns with real users, have a look at Anne Gibson’s "Accessibility Alphabet" to consider a few real-world scenarios that might hamper a user’s accessibility. Can you improve these users’ access to content and features?
Use the following checklist to make sure your design patterns are designed and built to be accessible*:
The amount of different documents that revolve around the WCAG 2.0 guidelines can be disorienting. These are the official W3C documents, in order of relevance, that we think you should refer to when learning about and implementing accessibility:
The web is abundant in tools that help to create and test for accessible sites. These are a few of the ones we consider the best and most useful ones: