Accessibility Audit — WCAG & EAA Compliance Checker

Accessibility Audit loads your published pages in a frame inside wp-admin and checks the rendered result — the page a visitor actually sees, not the HTML your server sent. Nothing is uploaded anywhere, there is no scanning API and no account to create.

See it on WPBay

What it checks

25 automated checks. Colour contrast is measured on resolved styles, which is the only way to catch text over a translucent overlay or a colour inherited from a parent. Findings are grouped by rule rather than by page, so twelve contrast failures caused by one theme colour read as one fix.

Honest about the numbers

Eighteen of the 25 map to a WCAG 2.2 success criterion, across fourteen distinct criteria at levels A and AA. The other seven are recommended practice, and the report labels them as such. A tool that presents every finding as a WCAG failure inflates its own numbers and yours — and yours is the one that ends up in a published conformance claim.

The European Accessibility Act document

With a licence the plugin builds the information required by Annex V of Directive (EU) 2019/882: a description of the service in accessible formats, what someone needs in order to understand how it works, how the Annex I requirements are met, and how your delivery process keeps it that way. If you are a public sector body it builds the other document instead, the model in Implementing Decision (EU) 2018/1523. Most tools conflate the two.

Free and licensed

Without a licence: 20 checks, up to five pages per scan, the full report and the comparison between scans. A licence adds every page, five further checks, unlimited history and the document generator. One download either way.

What it does not do

Automated testing finds roughly a third of real accessibility barriers. A clean report is a good sign, not a conformance statement, and keyboard and screen reader testing by a person is still required. Publishing a page is not a filing, and none of this is legal advice.

See it on WPBay

Latest writing

• WordPress Accessibility Checker: Why You Need Rendered Page Scans

  Discover why traditional API-based WordPress accessibility checkers fail on modern sites and why you must test the rendered page your visitors actually see.

• Public Sector WordPress Accessibility: Building the EU 2018/1523 Document

  Ensure your public sector WordPress site is compliant. Learn how to audit for WCAG 2.2 and generate the mandatory Implementing Decision (EU) 2018/1523 accessibility statement.

• European Accessibility Act (EAA) for WooCommerce: How to Audit Your Store

  Prepare your WooCommerce store for the European Accessibility Act (EAA). Learn why rendered page scans are essential and how to build your Annex V accessibility document.

• How to Generate an EAA Annex V Accessibility Statement in WooCommerce

  The European Accessibility Act requires an Annex V accessibility statement for e-commerce sites. Learn how to generate an honest, compliant statement for your WooCommerce store.

• WCAG 2.1 or 2.2 for the European Accessibility Act? The directive names neither.

  The EAA does not mention WCAG anywhere. It requires Annex I, and a WCAG version only enters the picture through a harmonised standard whose reference is published in the Official Journal. Which one that is, and why claiming the higher number is not automatically the safer choice.

• Does the European Accessibility Act apply to you? If you employ fewer than 10 people, probably not.

  Article 4(5) of Directive (EU) 2019/882 exempts microenterprises providing services from the accessibility requirements and from every obligation attached to them. Almost nobody selling EAA compliance tools mentions this, including, for a while, me.

• Your audit report says 2.1.1 fails on every element. Here is how to tell whether that is real.

  A vendor's keyboard test marks every control on the page as a Keyboard (2.1.1) failure. You unplug the mouse and everything works. Both of you can be honestly reporting what you saw — and the criterion does not mean what most reports assume it means.

• A reviewer found three wrong WCAG criteria in my accessibility plugin. I went looking, and found eight.

  A marketplace review rejected my WordPress accessibility scanner for citing WCAG criteria that were wrong, obsolete, or unrelated to what the check tested. Auditing all 25 rules found more than the reviewer did — and the wrong numbers were ending up in a legal document.

• Most "EAA accessibility statement" tools build the wrong document

  Implementing Decision (EU) 2018/1523 is the model statement for public sector bodies under Directive 2016/2102. The European Accessibility Act asks a business for something else entirely — Annex V. Mine got this wrong until a reviewer caught it.

• Accessibility Audit: A Practical WordPress Plugin for Finding WCAG Issues Before Your Visitors Do

  A WordPress plugin that finds WCAG issues before your visitors do, separates success criteria from recommended practice, and builds the Annex V information the European Accessibility Act requires.