SkillPublic
qa-accessibility
Test WCAG 2.2 AA accessibility with axe-core plus manual keyboard, focus, screen-reader, contrast, and zoom checks. Use for any customer-facing UI.
68
Quality
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Securityby
Passed
No findings from the security scan
Accessibility
Automated scans catch only part of the problem: axe-core finds about 57% of WCAG issues. Manual checks are required.
Procedure
- Run axe-core with WCAG 2.0, 2.1, and 2.2 A/AA tags on every route and state (open dialogs, errors shown). Review results marked "incomplete".
- Keyboard-only primary journey: logical tab order, visible focus (search the CSS for
:focus-visible, see pattern D7), no traps, Escape closes dialogs. - Screen reader spot check (VoiceOver on iOS/macOS): headings, landmarks, button names, and announced form errors.
- Contrast in light and dark themes, zoom to 200% and 400% reflow, and a 320px width.
- Forms: real labels (axe-core accepts a placeholder as the accessible name, so check labels separately), autocomplete attributes, and error text tied with aria-describedby.
- Motion: respect
prefers-reduced-motion.
Exit criteria
No serious or critical axe violations, and the manual checklist is recorded per route.
- Repository
itsablabla/qa-bug-agent-skills
- Revision
9a6f628
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.