Accessibility checks in a real browser
Accessible sites rank better, convert better and reduce legal risk. ZORO renders your pages and tests them with axe-core against WCAG 2.2 AA.

The issues that block real people
Low colour contrast, images without alt text, buttons and form fields without labels, missing landmarks, disabled zoom, unclear link text and more.
- WCAG 2.2 AA rules — run with axe-core
- Real rendering — JavaScript, mobile viewport
- Element-level detail — which elements fail and why
Why it matters for SEO
Alt text, headings, labels and clear link text help search engines and AI understand your pages — accessibility and SEO overlap far more than most people think.
Accessibility checks (WCAG 2.2)
Real-browser accessibility testing with axe-core: contrast, alt text, labels, landmarks, keyboard and zoom.
Colour contrast (WCAG 1.4.3)
Raise text contrast to at least 4.5:1 against its background (3:1 for large text).
Images have text alternatives
Give every meaningful image an alt text that describes it; use alt="" for decorative images.
Form fields have labels
Connect a visible <label for> (or aria-label) to every input, select and textarea.
Buttons have accessible names
Give icon-only buttons visible text or an aria-label that says what they do.
Links have discernible text
Make every link's text (or aria-label) describe its destination.
Page language declared
Set <html lang="…"> so screen readers use the right pronunciation.
Page has a title element
Give every page a unique, descriptive <title>.
Headings in logical order
Don't skip heading levels; use one H1 and nest H2–H6 in order.
Main landmark present
Wrap the primary content in <main> and keep other content inside header, nav and footer landmarks.
Skip link to main content
Add a "Skip to content" link as the first focusable element on the page.
Valid ARIA attributes and roles
Use only valid ARIA roles and attributes, and include the attributes each role requires.
Unique element IDs
Make every id attribute unique on the page, especially those referenced by ARIA.
Website accessibility testing with WCAG 2.2
Around one in six people live with a disability. An accessible website reaches more customers, works better for everyone and lowers legal risk — and many accessibility fixes also improve SEO.
What WCAG 2.2 covers
The Web Content Accessibility Guidelines (WCAG) 2.2 are the international standard for accessible websites. Level AA — the level most laws and policies refer to — covers text alternatives for images, sufficient colour contrast, keyboard access, visible focus, clear labels and instructions, consistent navigation, and content that works when zoomed or read by a screen reader.
How ZORO tests accessibility
ZORO renders your key pages in a real browser on a mobile viewport and runs axe-core, the widely used open-source accessibility engine, against WCAG 2.0, 2.1 and 2.2 A and AA rules plus best practices. It reports which rules fail, how many elements are affected and examples of the failing elements, alongside 18 accessibility checks in the audit.
Where accessibility and SEO overlap
- Alt text helps screen-reader users and helps search engines understand images.
- Heading structure gives both assistive technology and crawlers a clear outline of the page.
- Descriptive link text beats “click here” for users and for anchor-text relevance.
- Language attributes, labels and landmarks make content easier to parse for people and machines.
Frequently asked questions
Is this a full WCAG compliance audit?
It is an automated audit. Automated testing catches a large share of common WCAG failures quickly; a full compliance review also needs manual testing with assistive technology.
Which pages are tested in the browser?
Your homepage and the most important pages found during the crawl are rendered and tested on a mobile viewport.
How do I check if my website is accessible?
Run an automated audit to catch common WCAG failures quickly — contrast, alt text, labels, landmarks, zoom — then test key journeys with a keyboard and a screen reader. ZORO handles the automated part in every audit.
Is WCAG compliance a legal requirement?
In many places accessibility is required by law or regulation for some organisations — for example under the ADA in the US or the European Accessibility Act in the EU. Requirements vary, so check what applies to you.
Does accessibility affect SEO rankings?
Accessibility is not a direct ranking factor, but many of the same fixes — alt text, headings, link text, page structure — help search engines understand your content and improve user signals.
Can automated tools find every accessibility problem?
No. Automated testing catches a large share of common issues fast, but some criteria need human judgement, such as whether alt text is meaningful or a focus order makes sense.
What is a colour contrast ratio?
The difference in brightness between text and its background. WCAG AA requires at least 4.5:1 for normal text and 3:1 for large text.
See what’s holding your site back
Run a free audit in minutes: every SEO, AI-visibility, accessibility and security issue, ranked by impact, with the fix for your platform.