The Accessibility Toolkit: Testing Tools and Resources We Actually Use


These are the tools and references our team at Graceful Web Studio uses on real client work. Most are free. None of them are accessibility overlays or widgets, because those do not make a site accessible. Automated tools only catch part of what matters, often a third to half of the issues on a page, so the rest of this list covers the manual testing and design thinking that fills the gap.
These run in the browser and give you a fast read on the issues automation can reliably find.
A free Chrome extension from TPGi that scans a page and flags issues against WCAG and Section 508. We use it for a quick first pass on heading structure, landmarks, and ARIA before any manual testing begins.
A free bookmarklet built by the U.S. Social Security Administration. It shows how interactive elements will be announced to a screen reader and points to specific fixes. It runs in any browser with no install required.
A free browser extension powered by Deque's axe-core engine, the same engine behind many automated checkers. It is fast and accurate, and it is our default for catching the issues automation can find on its own.
TPGi's free desktop app for checking color contrast. The eyedropper samples any color on screen, so we can confirm text and non-text contrast meets WCAG 2.2 Level AA without guessing.
Download the Colour Contrast Analyser
A free tool for building color combinations that pass contrast checks before they ever reach a design file. Catching contrast problems this early saves rework later in the build.
Try the Accessible Color Matrix
Tools find symptoms. A repeatable method makes sure nothing gets missed.
WebAIM is a nonprofit known for clear, reliable accessibility guidance. Their checklist restates the WCAG success criteria in plain language, which makes it a practical reference to work from during a build or review.
Open the WebAIM WCAG 2 Checklist
The Trusted Tester process was developed by the Department of Homeland Security and is used across U.S. federal agencies for consistent, repeatable manual testing. I am a certified Trusted Tester, and the methodology shapes how we test every site we touch, government or not.
See the Trusted Tester process
No automated tool can tell you how a page sounds or whether it works by keyboard alone. You have to test it yourself, with the tools real people use.
A free, open-source screen reader for Windows. Because it is free and widely used, it is the screen reader we test with first on Windows.
The most widely used commercial screen reader on Windows. Testing with JAWS matters because many people who rely on assistive technology use it every day.
Apple's built-in screen reader, included on every Mac, iPhone, and iPad. We use it to test the experience for the large share of people on Apple devices.
Google's built-in screen reader for Android. Testing with TalkBack covers mobile users on Android, which automated tools cannot evaluate for you.
A short guide from The A11Y Project for turning on full keyboard navigation in Safari and Firefox on macOS. Without these settings, keyboard testing on a Mac gives misleading results.
Set up macOS keyboard navigation
The best accessibility work happens in the design phase, before a single line of code is written. These references help you think inclusively from the start.
A framework from CAST for designing experiences that work for the widest range of people. The guidelines are a useful lens well beyond education.
A short introduction to universal design for developers, produced by GSA and Digital.gov. A solid starting point for teams new to the idea.
Watch the Universal Design intro
A typical review runs in a few passes. We start with an automated scan in the ARC Toolkit to clear the obvious problems. Then we test by keyboard alone, checking that everything is reachable and the focus order makes sense. Next we run the page through a screen reader, usually NVDA on Windows or VoiceOver on Mac, to hear how it is announced. Finally we check color contrast with the Colour Contrast Analyser and review the design against inclusive UX principles. The goal throughout is WCAG 2.2 Level AA conformance, confirmed by hand rather than assumed from a scanner score.
If this list feels like a lot to manage on your own, that is normal. Manual accessibility testing takes time and training. We offer Webflow accessibility remediation and consulting for teams that want an expert review, and we build conformance in from day one on every new site. If you want a starting point, reach out for a quote or a free homepage evaluation.
Written by Crystal Scott, CPWA and certified Section 508 Trusted Tester at Graceful Web Studio
We would love to meet with you face-to-face. Whether virtually or for a coffee. Book a call, and let’s find the right solution for you! We review your site, map goals, and then deliver a clear plan and quote.
