Accessibility Audit (WCAG)
By casey w · Published · Updated
Checks a page or component against WCAG 2.1 AA and returns a ranked list of failures, each with the rule, the evidence and a concrete fix.
Prompt template
## Accessibility Audit (WCAG) Audit this interface for WCAG 2.1 AA. - What is being audited: [text: Page or component name] - Markup or description: [textarea: Paste the HTML or describe the layout and states] - Design colours: [textarea: Text and background colour pairs with sizes] - Platform: [dropdown: Website, Web app, Mobile web, Design mockup] - Assistive tech in scope: [multi: Screen reader, Keyboard only, Voice control, Zoom, Reduced motion] - Audience notes: [textarea: Known user needs or legal requirements] Work through four areas in order. Contrast: compute the ratio for each pair given and flag text under 4.5 to 1 (3 to 1 for large text and UI borders). Keyboard and focus: check that every control is reachable, the order follows the visual order, focus is visible, and nothing traps focus. Labels and structure: look for inputs without labels, images without useful alt text, vague link text, skipped heading levels and missing landmarks. Screen reader: read the markup as an announcement and note where state, errors or live updates would be silent. For each failure give the WCAG criterion number, the evidence, severity (blocker, serious or minor) and a specific fix, ideally with corrected code. Say plainly what you could not check from the supplied material, such as real device behaviour.