Manual Checks is the review queue for checks automation cannot safely classify, including tester instructions, expected observations, selectors, and evidence requirements.
This section is where the extension refuses to bluff. If something needs a person, it should be labelled as manual review and given enough context for that person to do the check well.
What this feature is for
Manual Checks is the review queue for checks automation cannot safely classify, including tester instructions, expected observations, selectors, and evidence requirements.
Feature coverage
- Displays manual-review tasks generated from scan outputs.
- Receives axe incomplete results and other review-required outputs.
- Shows rule/source, why automation could not safely classify the item, and instructions for the tester.
- Shows keyboard path where relevant, what to listen/check for, pass condition, fail condition, evidence to capture, and selector.
- Highlights affected elements and adds Manual Checks to the QA report.
WCAG and accessibility importance
Manual Checks keeps WCAG review honest for criteria that automation cannot safely decide alone, including keyboard journeys, screen-reader behaviour, dynamic updates, form instructions, dialogs, reading order, and context-dependent content alternatives.
This matters because many accessibility failures only appear during real tasks. The feature preserves what to test, what evidence to capture, and what pass or fail should mean instead of forcing uncertain issues into automated pass/fail buckets.
Technical notes
- Manual findings are generated from scanner evidence, responsive checks, heuristics, and feature-specific review paths.
- The classification is preserved so manual review is not accidentally reported as an automated confirmed failure.
- Selectors and snippets are included to make the work reproducible for QA, content, design, or engineering owners.
Desktop tutorial video
Where to learn more
Official A11Y Cat documentation: https://carlashub.github.io/a11y-cat-extension/