In Accessibility Nightmare: The Compliance Engine, the checkout components are repaired and the legal team needs proof of continuous compliance for next week’s EAA audit. The accessibility gate has passed every merge for months. But one complaint from the original legal notice was never reproduced: a user following any link had no idea where they had landed, because their screen reader carried on as though nothing had changed.
Your mission? Widen the gate to every step a customer takes, find the navigation barrier no scan has ever reported, fix it, and produce a report proving each step was audited and passed.
Expert: The Compliance Engine
In this level, you will find out what a green gate was actually measuring, and add the testing layer it was missing.
What You’ll Learn:
- Gate Coverage: Why a passing accessibility check means nothing until you know which pages and states it tested.
- Scanner Limits: Why faults that only appear when a user does something are invisible to axe-core, and which layer catches them instead.
- SPA Navigation: How client-side routing can silently break the contract assistive technology depends on, and what it takes to restore it.
- Compliance Evidence: How to turn test results into a report that records what was tested, how it was tested, and that it passed.
The Tech Stack:
- React & Vite
- Playwright with the JSON reporter and test annotations
- Guidepup Virtual Screen Reader
- axe-core
- WCAG 2.2
Verify your solution inside your Codespace and generate a Certificate of Completion.
Ready to Start?
Start the Challenge
A green check only proves what it looked at.