Accessibility Patterns for the Web
This book will assist frontend developers in building accessible e-commerce websites and components. It is a living document - so please expect continual edits and updates.
The book is work-in-progress. Some patterns are complete, but gaps in the documentation still remain. We are addressing these gaps as quickly as we can.
These patterns will assist developers with accessibility, but are not considered to be final, packaged code!
Each pattern follows a Progressive Enhancement strategy (where applicable) and aims to conform to WCAG 2.0 Level AA.
There are 4 main groups of patterns:
These groups spell out the MIND acronym. If you ever wonder what group does a pattern fall into - then use your MIND!
Three other important groups complement our patterns: Structure, Anti-Patterns and Techniques.
Every pattern includes:
- Working examples
- Best practices
- Interaction design
- Developer guide
- ARIA Reference
The book also contains an appendix section with a list of ARIA Essentials, References, Utilities and FAQ.
There are 4 guiding principles of accessibility, collectively know as POUR:
- Perceivable: People experience content in different ways (sight, hearing, and touch). Content needs to be transferable into recognizable (or perceivable) formats.
- Operable: Content needs to be navigable (or operable) by multiple methods—not just a mouse
- Understandable: Web content needs to be understandable. Language should be simple and concise; functionality should be consistent and intuitive.
- Robust: Create web content that works for all (or most!) technologies. This includes operating systems, browsers, and mobile devices.
From a developer perspective, Operable and Robust are the most important principles!
Don't feel like reading? You can, if you wish, dive straight into the working examples.