What are website accessibility checks?
Accessibility checks test whether everyone, including people using screen readers or keyboards, can use your site. ZORO runs 18 WCAG 2.2 AA checks with axe-core in a real browser, covering colour contrast, alt text, form labels, landmarks, zoom and keyboard focus, and lists each affected element with its fix.
Each check shows its impact on your score — High Medium Low — and how to fix it. Click a check for its step-by-step guide.
- Colour contrast (WCAG 1.4.3)HighRaise text contrast to at least 4.5:1 against its background (3:1 for large text).
- Images have text alternativesHighGive every meaningful image an alt text that describes it; use alt="" for decorative images.
- Form fields have labelsHighConnect a visible <label for> (or aria-label) to every input, select and textarea.
- Buttons have accessible namesHighGive icon-only buttons visible text or an aria-label that says what they do.
- Valid ARIA attributes and rolesHighUse only valid ARIA roles and attributes, and include the attributes each role requires.
- WCAG 2.2 AA violations overallHighFix the violations listed here, starting with the critical and serious ones.
- Links have discernible textMediumMake every link's text (or aria-label) describe its destination.
- Page language declaredMediumSet <html lang="…"> so screen readers use the right pronunciation.
- Page has a title elementMediumGive every page a unique, descriptive <title>.
- Main landmark presentMediumWrap the primary content in <main> and keep other content inside header, nav and footer landmarks.
- Zooming not disabledMediumRemove user-scalable=no and maximum-scale from the viewport meta tag.
- Video captionsMediumProvide captions (a <track kind="captions">) for videos with speech.
- Headings in logical orderLowDon't skip heading levels; use one H1 and nest H2–H6 in order.
- Skip link to main contentLowAdd a "Skip to content" link as the first focusable element on the page.
- Unique element IDsLowMake every id attribute unique on the page, especially those referenced by ARIA.
- Lists structured correctlyLowOnly put <li> elements directly inside <ul> or <ol>.
- Frames have titlesLowGive every iframe a title attribute describing its content.
- No positive tabindexLowRemove tabindex values above 0 so keyboard focus follows the page order.
Accessibility checks (WCAG 2.2)
Tested in a real browser
ZORO renders your pages and runs axe-core against WCAG 2.2 A and AA rules, so issues that only appear after JavaScript runs are caught too.
Why it matters
Accessible websites serve more customers, reduce legal risk and are easier for search engines and AI systems to understand.
Frequently asked questions
What are the most common accessibility errors?
Low colour contrast, images without alt text, form fields without labels, empty links and buttons, missing page language and disabled zoom.
What does WCAG 2.2 add over WCAG 2.1?
New criteria including focus not obscured, dragging alternatives, minimum target size, consistent help, redundant entry and accessible authentication.
Does accessibility help AI and search engines?
Yes — text alternatives, headings, labels and clear structure make content easier for machines to parse as well as for people.
Check your site for all 18 Accessibility issues
Run a free audit in minutes: every SEO, AI-visibility, accessibility and security issue, ranked by impact, with the fix for your platform.