Issue library
These pages mirror what automated scanners often report. Each one pairs with a live scan so you can see the same rules on your own URL.
For CMS and framework-specific write-ups, open any issue and use the platform chips, or start from WordPress accessibility hub. Quick links: WordPress example · Shopify example · React example · Next.js example.
Visual & contrast
Color, images, and what people see—or do not get from pixels alone.
- Missing alternative text on images
Images without text alternatives are invisible to many assistive technologies unless they are purely decorative.
- Low color contrast
Text that blends into the background is hard to read for people with low vision and in bright sunlight.
Forms & controls
Labels, buttons, and interactive components.
- Missing form labels
Placeholder text is not a substitute for labels.
- Empty buttons
Icon-only buttons need visible text or `aria-label`.
Structure & identity
Headings, landmarks, and duplicate IDs.
- Heading structure problems
Headings create an outline; random levels harm navigation.
- Duplicate IDs
IDs must be unique in the DOM.
Keyboard & ARIA
Focus, traps, and assistive roles or attributes.
- Keyboard traps
If focus cannot escape a component, keyboard users are stuck.
- ARIA mistakes
Use ARIA sparingly; prefer native HTML.
- Missing focus indicator
Do not remove outlines without replacing them.
Links & readable text
Link purpose and text that should be programmatically available.
- Missing or vague link text
Link purpose should be clear from text alone where possible.