Test With People and Tools
Test with a keyboard, a screen reader, and an automated checker, include disabled people, and avoid shortcuts that do not work.
What you will learn
By the end of this lesson, you can run three free accessibility tests on a page and explain why one-click "fix" tools are not enough.
Three tests you can run today
1. The keyboard test
Put your mouse away. Press Tab to move forward and Shift plus Tab to move back. Press Enter or Space to use buttons.
- Can you reach every link, button, and field?
- Can you always see where you are?
- Does the order make sense?
- Can you get out of every pop-up?
2. The screen reader test
Screen readers come free with most devices. VoiceOver is built into iPhones and Macs. TalkBack is built into Android. Narrator is built into Windows, and NVDA is a free download for Windows.
Turn one on and listen to your page. Do the images make sense? Do form fields say what they are? Learning a screen reader takes practice, so start with a simple page.
3. The automated checker
Free tools such as WAVE (from WebAIM) or the accessibility check in browser developer tools scan a page and flag problems like missing alt text and low contrast.
Automated checkers are useful but limited. They can tell you an image has alt text. They cannot tell you if the alt text is accurate. Many problems can only be found by a person.
Test with disabled people
The best test is watching disabled people use what you built. Invite them early, not after launch. Respect their time and expertise, and thank them. Do not assume one person speaks for every disability.
The overlay trap
Some companies sell "accessibility overlays," which are scripts that claim to make any website accessible automatically. Many disabled users and accessibility experts say these tools do not fix the real problems and can get in the way of screen readers. In 2025, the Federal Trade Commission ordered one overlay company to stop claiming its tool could make any website meet accessibility standards.
Do not rely on an overlay. Fix the actual code and content. There is no one-click shortcut to accessibility.
When not to ship
Accessibility is not a final polish step. Hold the launch when:
- Core tasks, like signing up or getting help, cannot be done with a keyboard or screen reader.
- Videos with key information have no captions.
- Forms have no labels or unclear errors.
My accessibility test plan
0 of 5 doneGo deeper: Accessibility: Build Products Everyone Can Use (and Love)
Quiz: Module 9 Quiz: Accessibility
Discussion
Ask. Answer. Build together.
Loading…