Free Accessibility Testing Tool: Meet WCAG 2.1 and DOJ Compliance Deadlines with Vision
- Last Edited April 17, 2026
- by Garenne Bigby
The DOJ’s April 2024 Final Rule is here. If your state or local government serves 50,000 people or more, your website has to be accessible by April 24, 2026. That’s a few months away. Smaller entities get until April 26, 2027.
Miss the deadline and you’re looking at legal risk, federal funding headaches, and a much worse outcome: residents who can’t use the services you’re supposed to provide.
We built something to help. It’s called Vision, it’s free, and it’s ready today.
What the DOJ actually requires
The Final Rule for Title II of the ADA doesn’t leave much room to wiggle. Here’s what it says, in plain terms:
Your sites and mobile apps have to meet WCAG 2.1 Level AA. Not “best effort.” Not “substantial conformance.” The standard.
There’s no easy out. “Fundamental alteration” and “undue burden” exceptions exist, but you have to document them and provide alternative access. They are not a shortcut.
And enforcement is real. The DOJ has been pursuing cases. Settlements tend to involve significant remediation costs and ongoing monitoring, which is expensive and slow.
Here’s the thing though. Compliance is the floor. Roughly 27% of American adults have a disability. When your site breaks for them, you’re telling a huge chunk of your community they don’t get equal access to government. That should bother us more than the lawsuit risk.
Meet Vision
Vision is a modern web accessibility evaluation tool. It analyzes pages against WCAG 2.1, and it does something most automated checkers don’t: it tests your site the way a real person would actually use it.
Most tools fetch a static HTML snapshot and run rules against it. Fast, clean, and wrong. Real websites have carousels that rotate, accordions that expand, menus that open on hover, content that loads as you scroll. A static snapshot misses all of that.
Vision renders pages with full JavaScript execution. Scripts run. Interactive elements work. Dynamic content loads. You test what your visitors actually see.
What Vision checks
Over 30 automated checks against WCAG 2.1 A and AA, grouped into categories that make sense:
- Errors. Missing alt text, unlabeled form inputs, broken heading structure, empty links. The stuff that definitively fails.
- Contrast issues. Text contrast ratios measured precisely, with AA and AAA thresholds called out.
- Alerts. The gray areas. Suspicious alt text, missing skip links, generic link text. Things that need your eyes on them.
- ARIA issues. Invalid roles, missing required attributes, broken ID references, focusable elements hidden from screen readers.
- Structural issues. Page titles, landmark regions, heading hierarchy.
- Features. The good stuff. Properly labeled elements, language attributes, semantic landmarks. So you know what’s working, not just what’s broken.
See your page the way assistive tech does
Lists of issues are useful. Seeing the issues on the page is better.
Vision puts color-coded badges directly on the problem elements, with counts for each one. Click an issue in the sidebar, and the page scrolls to it and highlights it. Click any element on the page, even elements with no detected issues, and you get the full accessibility story for that element.
There’s a Styles Off mode you should try on your own site today. It strips all CSS and shows the actual DOM reading order. That’s the sequence a screen reader walks through. If it looks chaotic with styles off, that’s what screen reader users experience.
Six panels for digging in
The sidebar is organized around what you’re actually trying to do:
- Overview. Dashboard view. Issue counts by category, severity, plus badges for what’s working.
- Findings. The full issue list. Filter by type, severity, or search to zero in on what you need.
- Structure. Heading hierarchy, landmarks, reading order, hidden elements. The semantic skeleton.
- Contrast. Visual previews of your color combinations, exact ratios, AA/AAA status.
- Code. The HTML and XPath for each issue, matching what Chrome DevTools shows. If you’re a developer, this saves you a lot of time.
- Explain and Fix. Plain-language explanations of each issue, WCAG references, and an ignore option when you need to focus.
Export in the format your team uses
One report won’t work for everyone. Your stakeholders want a shareable link. Your auditor wants a PDF. Your dev team wants JSON. Your PM wants to drop the issues into a spreadsheet.
Vision exports all four: HTML, PDF, JSON, and CSV. Same data, different shapes.
Other things worth mentioning
- Responsive testing at Desktop (1920px), Tablet (768px), and Mobile (375px).
- Cookie popup handling for over 40 consent platforms, so you’re testing content instead of banners.
- Dark mode with WCAG AA contrast throughout.
- English and Spanish interface support.
- Configurable rules for background images, visually hidden text, disabled elements, and minimum text size.
- Ignore system so you can mark false positives and move on.
- Resizable sidebar that remembers your preference.
An honest note about automated testing
You should know this before you run a single scan. Automated accessibility tools catch somewhere between 30% and 40% of WCAG issues. The rest needs human judgment. Does this alt text actually describe the image? Does this heading make sense without sight? Is this form usable end-to-end with a screen reader? Vision can’t answer those questions. Nothing can, except a person.
So use Vision for what it’s good at: catching the automatable bugs fast, so your human review time goes to the things that actually need humans. Think of it as the first sweep, not the last word.
Why accessibility pays off beyond compliance
You get some nice side effects when you build accessible sites:
- Better SEO. Most accessibility practices line up with search engine best practices.
- Better mobile. Accessible layouts tend to be more flexible, which helps on every device.
- Lower support load. Clear, well-structured content means fewer phone calls.
- Code that ages well. Accessible markup is semantic markup, and semantic markup adapts to whatever comes next.
Your deadline, clearly
| Entity type | Deadline |
| Population of 50,000 or more | April 24, 2026 |
| Population under 50,000 | April 26, 2027 |
This applies to all web content and mobile apps, including third-party content you’ve embedded in your site. That widget you added in 2019? Yes, that too.
Get started
No registration. No usage limits. No watermarks on your reports. You paste a URL, you get results.
If you’re a developer fixing issues, a compliance officer documenting your posture, an IT manager assessing where you stand, or an elected official making sure your residents are actually being served, Vision will help.
The deadlines aren’t going to move. Don’t wait for a complaint to land in your inbox.
Accessibility isn’t only a legal box to check. It’s what you owe the people you serve. We’d like to help you get there.
Categories
- Last Edited April 17, 2026
- by Garenne Bigby