I built a free WCAG 2.2 checker that's honest about what automated scans miss
Agencies get asked "is our site accessible?" all the time. Most answers are either vague ("we follow WCAG") or a five-figure manual audit. I built something in between: A11yKeeper — paste a URL, it runs axe-core across that page plus up to 9 linked pages (~1 min), groups issues by severity, and gives a plain-English fix for each. What I tried to get right It says clearly that a clean scan ≠…
Agencies often inquire about their website's accessibility, but answers frequently fall short—some are vague, offering only a general statement about following WCAG, while others require a costly manual audit. A11yKeeper, an independent tool, bridges this gap: users simply input a URL, and the platform scans the page and up to nine linked pages (taking about one minute).
Issues are organized by severity, and each receives a straightforward, plain-English fix suggestion. Crucially, A11yKeeper emphasizes that a clean scan does not equate to accessibility. Based on Deque's 2021 data, automated detection identifies approximately 57% of issues by volume; every report concludes by highlighting the necessity for human verification—checking keyboard functionality, screen reader compatibility, and content clarity.
The tool is free with three scans per day, requiring no sign-up to view results. Agencies have the option to brand white-label PDF reports for their clients. On the W3C's intentionally flawed demo site, A11yKeeper detected 353 issues across 10 pages. Seeking five founding agencies to help schedule recurring checks and provide read-only client links, the platform offers a 50% discount for subscribers as long as they stay subscribed. Feedback on false positives or confusing fix instructions is welcome.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
