Skip to main content

Issue library

Each guide explains what automated tools flag, why it blocks people, and what to change in code or your CMS. Use them after a scan so findings on your URL map to plain-language fixes.

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.

Who it affects: People with low vision, color blindness, and anyone on bright screens or poor displays.

  • 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.

Who it affects: Screen reader users, keyboard-only users, and people who rely on clear errors and labels.

Structure & identity

Headings, landmarks, and duplicate IDs.

Who it affects: Screen reader users navigating by headings and landmarks, and voice control users.

Keyboard & ARIA

Focus, traps, and assistive roles or attributes.

Who it affects: Keyboard-only users, switch users, and people using screen readers with custom components.

Links & readable text

Link purpose and text that should be programmatically available.

Who it affects: Screen reader users scanning links out of context and people who need predictable link text.