Zero Axe Violations, Four Real Bugs: What AI Catches That Automated Accessibility Testing Misses
Rule-based accessibility scanners check that markup is well-formed, not that it's true. I built a demo site engineered to pass axe-core with zero violations on every page, then built a second Playwright suite that uses Claude to judge alt-text accuracy, DOM-vs-visual reading order, real focus behaviour, and error-message clarity - and it failed on every seeded defect, including one in the demo's own 'control' case I hadn't noticed myself.