Accessibility audit of pasted HTML with WCAG fixes
Reviews a page's HTML for problems that block screen reader, keyboard and low-vision users, names the WCAG success criterion for each one, and returns the corrected markup. Use it before a launch or after an accessibility complaint, on forms, menus, modals and image-heavy pages.
The output this prompt produced, unedited.
The prompt
What to give
HTML of the page or component: [paste]
Related CSS for colours and focus styles: [paste, or none]
What the component does: [e.g. a checkout form with an address modal]
Target level: [e.g. WCAG 2.2 AA]
Check
Images: meaningful alt text, or empty alt for decoration.
Headings: one main heading and no skipped levels.
Forms: every input has a visible label tied to it; errors are announced and say how to fix.
Buttons and links: real elements, with names that make sense out of context.
Keyboard: every control reachable in a logical order, with a visible focus style.
Modals and menus: focus moves in, stays inside, and returns on close; Escape closes.
Colour: text contrast meets the target level; colour is never the only signal.
ARIA: used only where native HTML cannot do the job, and never in conflict with it.
The corrected HTML in one code block, with changed lines marked by a short comment.
Three manual tests to run with a keyboard and a screen reader.
Guardrails
Judge only the code given; mark anything needing a live test as unverified.
Prefer native elements over ARIA roles.
accessibility auditwcag checklistweb accessibilityaria labelsscreen reader testingaccessible html
How to run this
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.