Accessible by design
“ Accessibility is a requirement. It’s not a feature or a nice-to-have.”
Start with the end in mind
We achieve the best outcome when we make accessibility a project requirement instead of a check before launching a website. Sites are easier to change because code hasn't been written to fix existing problems. As a result, sites are easier to test—fewer lines of code mean fewer bugs.
Test categories
- Mobile devices
- Keyboard navigation
- Voice navigation
- Color contrast and color blindness
- Screen readers
- JAWS
- NVDA
- VoiceOver
Automated testing
Autmated tests are a great way to ensure a baseline of compliance. Unit tests check small snippets of code like a shopping cart or a navigation bar. Integration tests make sure units are working together. End-to-end tests confirm user actions from beginning to end. Visual regression tests make sure your site layout has not changed unexpectedly.
Manual testing
Some accessibility testing can be automated, but there are key things that a person must test. Computers do a great job repeating the same task, asking if anything has changed. But it takes a person to answer “How does this website, how does this application work? Can I use it without getting frustrated or discouraged? Does it make me feel good about this purchase?”