Accessibility

Accessibility scans your site against common WCAG failure patterns and fixes what can safely be fixed automatically.

What it checks

• Images without alternative text.
• Colour contrast below the required ratio.
• Heading structure (skipped levels, multiple H1s).
• Links and buttons without a discernible name.
• Form fields without labels.
• Missing language attribute and document landmarks.
• Keyboard focus and focus visibility issues.

Step-by-step

1. Run the scan from the Accessibility page.
2. Read the score and the issue list, grouped by severity and by how many pages are affected.
3. Fix the automatable issues — alt text, link names, language attribute and landmarks can be handled by automations.
4. Send the rest to your developer: contrast, focus states and structural markup usually need theme changes. Each issue includes the selector and the affected URLs.
5. Re-scan to confirm the fixes landed.
6. Keep the accessibility automations on so new pages and products do not reintroduce the same problems.

Prioritising

1. Blockers for keyboard and screen-reader users (missing names, no labels, focus traps).
2. Contrast issues on primary actions.
3. Heading and landmark structure.
4. Cosmetic or low-frequency issues.

Note

Automated testing catches a meaningful share of issues but not all of them. Manual checks with a keyboard and a screen reader remain necessary before claiming conformance.