QA
Accessibility audit on PR
Run axe-core against each PR's changed UI, block critical accessibility violations, and annotate the lines that need fixes.
accessibilitywcaga11yaxe-corepr-gateqa
[ workflow / qa ]
Accessibility audit on PR
Accessibility defects are cheaper to fix before they ship. On UI PRs, Cosmos renders the changed surfaces in a headless browser and runs an axe-core WCAG 2.1 AA scan. Critical violations block merge with line-level fixes; warnings post as non-blocking review comments.
06 nodes
04 edges
Trigger[trigger]
PR opened / updated
UI files changed
AI Agent step[mount]
Mount components
Headless browser render
AI Agent step[scan]
axe-core WCAG 2.1 AA scan
Critical · serious · moderate
Decision
Critical violations?
No
Output / Result[warn]
Post warning comment
Non-blocking summary
Decision
Critical violations?
Output / Result[warn]
Post warning comment
Non-blocking summary
YES
Output / Result[block]
Block PR + inline annotations
Line-level fix suggestions
Workflow prompt
Paste this into Augment to reproduce the workflow end-to-end.
Cosmos, on every pull request that changes files under src/components, src/pages, or src/app, mount the affected components in a headless browser and run axe-core with WCAG 2.1 AA rules. For each critical violation, post an inline PR comment on the offending line with the violation ID, a plain-English description, and a recommended fix code snippet. For serious and moderate violations, post a summary comment without blocking. Add a 'fail' check status to the PR if any critical violations are present; otherwise add a 'pass' status. Do not merge until critical violations are resolved.