Accessibility Audit
Use when
Auditing a page, component, flow, or design system for accessibility.
Procedure
- Prefer rendered inspection over source-only inference when runtime/browser access exists.
- Check semantic structure, names/roles/values, heading hierarchy, landmarks, labels and descriptions.
- Check full keyboard operation, focus order, focus visibility, traps, and escape behavior.
- Check text/non-text contrast and state-specific contrast against the project's target WCAG level.
- Check pointer target sizing and alternatives to drag/gesture-only interactions.
- Check errors, status messages, loading states, validation, and dynamic announcements.
- Check reduced motion and content that depends on animation.
- Check responsive/reflow behavior at narrow widths and zoom-sensitive layouts.
- Separate automated findings from manual/behavioral findings.
Output
Prioritize findings by user impact and release risk. Every finding should include evidence, affected surface, remediation, and verification method.
Failure conditions
An automated scanner passing is not equivalent to WCAG conformance. Do not state that a surface is accessible solely because axe or another automated tool reports zero violations.
1---2name: accessibility-audit3description: Accessibility Audit4---5# Accessibility Audit67## Use when89Auditing a page, component, flow, or design system for accessibility.1011## Procedure12131. Prefer rendered inspection over source-only inference when runtime/browser access exists.142. Check semantic structure, names/roles/values, heading hierarchy, landmarks, labels and descriptions.153. Check full keyboard operation, focus order, focus visibility, traps, and escape behavior.164. Check text/non-text contrast and state-specific contrast against the project's target WCAG level.175. Check pointer target sizing and alternatives to drag/gesture-only interactions.186. Check errors, status messages, loading states, validation, and dynamic announcements.197. Check reduced motion and content that depends on animation.208. Check responsive/reflow behavior at narrow widths and zoom-sensitive layouts.219. Separate automated findings from manual/behavioral findings.2223## Output2425Prioritize findings by user impact and release risk. Every finding should include evidence, affected surface, remediation, and verification method.2627## Failure conditions2829An automated scanner passing is not equivalent to WCAG conformance. Do not state that a surface is accessible solely because axe or another automated tool reports zero violations.
devotionn