Skip to content

Accessibility checker:Can everyone use your website?

See the WCAG 2.2 issues on your page grouped by impact, with the exact elements to fix, from colour contrast and form labels to tap targets and zoom.

Device
  • Free, no account
  • Results in under a minute
  • Audits against WCAG 2.2 A and AA
Example result

example-shop.hr

WordPress 6.8

Sample shop · homepage · mobile Chrome · the same check you get for your own site

Run it on your site
Accessibility

7 passed · 3 failed · 3 warnings. Biggest issue: 1 critical accessibility violation.

axe-core 4.13.0:1 critical2 serious0 moderate0 minor· 38 rules passed

What we found

3 failed3 warnings7 passed
Show 7 passed checks

Fix these first

From the example above. Check your own site to get the fixes that apply to it.

  1. Problem: 1 critical accessibility violation

    Critical issues stop some visitors from using the page at all, for example buttons a screen reader cannot name or forms that cannot be filled in.

    How to fix it: Open the technical detail to see each rule and the elements affected.
  2. Problem: 2 serious accessibility violations

    Serious issues make parts of the page very hard to use with a screen reader, keyboard or zoomed-in display, so some visitors give up before they buy or get in touch.

    How to fix it: Open the technical detail to see each rule and the elements affected.
  3. Problem: 1 link or button has no accessible name

    Icon-only links and buttons are read out as "link" or "button" with nothing else, so screen reader users cannot tell the cart from the search.

    How to fix it: Add visible text, or aria-label="…" on the link or button, that says where it goes or what it does.

What this tool checks

axe-core plus our own checks, run on the page as Chromium renders it.

  • Critical accessibility issues

    Finds issues that stop some visitors from using the page at all, like unnamed buttons.

  • Serious accessibility issues

    Finds issues that make parts of the page very hard to use with a screen reader or keyboard.

  • Moderate accessibility issues

    Finds issues that slow visitors down, such as headings out of order or unnamed page regions.

  • Minor accessibility issues

    Finds small inconsistencies that add friction for people using assistive technology.

  • Text colour contrast

    Checks text stands out enough from its background to read on a phone or with weaker colour vision.

  • Page landmarks

    Checks for header, navigation, main and footer areas that screen reader users jump between.

  • Skip to content link

    Checks keyboard users can jump past the menu to the main content in one keystroke.

  • Form field labels

    Checks every form field has a label, so screen readers can say what each one is for.

  • Link and button names

    Checks icon-only links and buttons have a name that screen readers can read out.

  • Image alt text

    Checks images have alternative text for screen readers, broken images and image search.

  • Tab order

    Checks keyboard focus follows the order things appear on screen, without forced jumps.

  • Page language

    Checks the page declares its language, so screen readers use the right pronunciation.

Show 10 more checks
  • Text colour contrast

    Checks text stands out enough from its background to read on a phone or with weaker colour vision.

  • Page landmarks

    Checks for header, navigation, main and footer areas that screen reader users jump between.

  • Skip to content link

    Checks keyboard users can jump past the menu to the main content in one keystroke.

  • Form field labels

    Checks every form field has a label, so screen readers can say what each one is for.

  • Link and button names

    Checks icon-only links and buttons have a name that screen readers can read out.

  • Image alt text

    Checks images have alternative text for screen readers, broken images and image search.

  • Tab order

    Checks keyboard focus follows the order things appear on screen, without forced jumps.

  • Page language

    Checks the page declares its language, so screen readers use the right pronunciation.

  • Zoom on phones

    Checks visitors can pinch to zoom the page on their phone to read small text.

  • Tap target size

    Checks links and buttons are at least 24×24 px, so visitors don't mis-tap on phones.

Show 2 more checks
  • Zoom on phones

    Checks visitors can pinch to zoom the page on their phone to read small text.

  • Tap target size

    Checks links and buttons are at least 24×24 px, so visitors don't mis-tap on phones.

How it works

  1. Render the page

    Your page is loaded in Chromium, so the audit sees what visitors see after scripts run.

  2. Run axe-core

    The page is audited with axe-core against WCAG 2.2 A and AA. Violations are grouped by impact, from critical to minor, with the CSS selectors of the affected elements.

  3. Add our own checks

    On top of axe we check colour contrast, landmarks, a skip link, form labels, link and button names, alt text, tab order, page language, mobile zoom and tap-target size.

Automated checks find about a third of WCAG issues. Keyboard and screen-reader testing by a person covers the rest.

Questions

Is this really free?

Yes. getReport is funded by donations, not plans. This tool runs the full report and shows you the part it is about; the complete report with all seven modules is one click away, also free.

Does a clean axe result mean the site is WCAG compliant?

No. Automated tools catch roughly 30–40 % of WCAG criteria. A clean result means the common mistakes are gone; keyboard and screen-reader testing by a person covers the rest.

Which axe-core version do you run?

The version is printed in the report next to the counts. It follows the axe-core releases within a few weeks.

Can I run this on many sites?

You can check 10 sites every 10 minutes and 50 a day from one connection. For more at once, the bulk URL checker and the bulk PageSpeed checker take lists of URLs; a free API is in development. Cached reports never count against the limit.

Why does accessibility matter?

Around one in six people has a disability that affects how they use the web, and everyone uses a phone in bright sun with one thumb. Accessible pages are simply usable pages. It is also law: the European Accessibility Act has applied since 28 June 2025 to online shops, banking, transport and other consumer services in the EU; micro-enterprises (under 10 staff and €2 million turnover) are exempt. Automated checks find about a third of WCAG issues, the most common third.

All 41 tools →

Free, funded by the people who use it

€0 of €75 this month. At €75, site crawl up to 500 pages + weekly re-check switches on for everyone.

Chip in