Automated accessibility checkers can catch missing alt text or bad contrast. They cannot tell you whether a page actually makes sense when someone navigates it with a screen reader. For Pure Contrast Tools, we test with real screen readers so the experience works for people who use them every day.
We Use Real Screen Readers
We test our pages with popular screen readers on the platforms we support. That includes NVDA on Windows, VoiceOver on macOS and iOS, and TalkBack on Android where relevant. We do not rely on automated tools alone. We turn the screen reader on, tab and swipe through the interface, and fix anything that is confusing, silent, or out of order.
What We Check
We focus on the things that affect real use:
- Semantic HTML: Headings, lists, buttons, and links are marked correctly so the screen reader can announce structure and let users jump by heading or landmark.
- Labels and names: Every control has a clear, announced name (visible label,
aria-label, oraria-labelledby). Nothing is "button" or "link" with no context. - Focus order: Keyboard and screen-reader focus move in a logical order. No invisible focus traps and no big jumps that skip content.
- Live regions: When something changes on the page (for example, a result or a theme change), we use
aria-liveso the screen reader announces it instead of staying silent. - Skip links and landmarks: Where it helps, we provide ways to skip repeated content and move by region (main, navigation, etc.).
No Automation-Only Testing
Automated checks are useful for catching obvious issues. They cannot tell you if a heading order is misleading, if a button is announced in a way that makes sense, or if a dynamic update is announced at all. We run automated checks as part of our workflow, but we always validate with a real screen reader before we call a page done.
High Contrast and Keyboard Too
Screen reader testing sits alongside our other checks. We test keyboard navigation (tab order, no keyboard traps, visible focus). We test our high-contrast themes so that low-vision users who use a screen reader part of the time still get clear, readable visuals. We aim for WCAG 2.1 Level AA and treat screen reader usability as a core requirement, not an afterthought.
Feedback From Real Users
We also listen. If someone tells us that a tool is hard to use with their screen reader, we treat that as a bug and fix it. Our feedback form is on the site, and we do not track you. If you hit a problem, tell us and we will improve the experience for everyone.
Testing with screen readers is how we make sure Pure Contrast Tools is not just "technically" accessible, but actually usable. We will keep doing it for every new tool and every major change.