Route-level semantics
Catch duplicated landmarks, heading gaps, unnamed controls, and DOM relationships after composition.
For engineering teams
Test the rendered Next.js app, not just its components
Component tests matter, but routes can still combine into inaccessible pages. Scan deployed output, fix the source, and check it again after release.
Typical Next.js work
Client-side state
Review forms, dialogs, navigation, and loading states with automated evidence plus keyboard and screen-reader checks.
Release regressions
Schedule scans of saved routes and compare trends when design-system or feature changes ship.
Put accessibility checks into the release loop
Use targeted re-checks, CI, comparable-run diffs, and authenticated journeys to keep concrete evidence near engineering work.
Pull request
Run the shipped GitHub Action or GitLab CLI with an explicit new-finding policy.
Targeted verification
Re-scan the changed route and keep the rule, selector, source snippet, and affected-page evidence together.
Regression diff
Compare completed runs only when the page set and standard are comparable.
Authenticated states
Model repeatable checkpoints for product states that a public crawl cannot reach.
What automation can support
Rendered-rule checks, configured CI policy, reached-page counts, comparable-run changes, and checkpoint findings.
What still needs people
Interaction quality, task completion, assistive-technology behavior, content meaning, and a conformance assessment.
See the evidence before signing up
The sample is a real report view: severity, affected element, rule, and a practical direction for the fix. Automated coverage is clearly separated from manual review.
Platform questions
Do I need to install a plugin?
No. wcagc scans the rendered public website, so it does not require a platform plugin.
Will the scan find every accessibility issue?
No. Automated tests find only part of WCAG issues. Theme semantics, content quality, keyboard flows, and assistive-technology behavior also need manual review.
Can I verify a change after fixing it?
Yes. Re-scan the affected page or saved site and compare current evidence while keeping manual checks in the workflow.