Description
Limen Accessibility Audit checks your published pages against WCAG 2.1 Level AA and, for every failure it finds, shows you the specific code that fixes it in WordPress or WooCommerce.
It is built around one uncomfortable fact that most accessibility tools skate over: automated testing finds roughly a third of accessibility barriers. No scanner can tell whether your alt text is accurate, whether your headings actually describe the content, or whether a keyboard user can finish checkout. This plugin says so plainly, separates what it proved from what a person still has to check, and never issues a conformance claim.
What it does
- Scans your home page and a sample of each content type — posts, pages, products, custom types
- Reports 27 checks across WCAG 2.1 Level A and AA
- Separates confirmed failures from checks that need a human, and never counts the second group in your score
- Shows the fix as WordPress-specific code you can copy, not generic advice
- Orders findings by what actually appears in legal complaints, not by scanner severity
- Lists explicitly what it could not determine
Your pages are never uploaded
The scan runs entirely inside your browser tab. The plugin fetches your own pages from your own site — same origin, no proxy — and audits them in JavaScript on your machine.
There is no server in the path. This is not a privacy promise bolted on afterwards; it is how the plugin is built, and it means the tool also works on staging sites, password-protected pages, and logged-in views that an external crawler could never reach.
Everything here is free
Every check, every score and every fix snippet is free and fully enabled, permanently. Nothing is held back, and there is no paid version of this plugin.
Stores nothing, contacts nothing
The plugin writes nothing to your database: no options, no tables, no transients, no scheduled tasks. It makes no requests to any external service. The only network requests it makes are to your own site, from your own browser, to fetch the pages it audits.
Source code
All of the code is included in the plugin, unminified. The audit engine lives in the engine/ folder as readable JavaScript.
Screenshots
Installation
- Install and activate the plugin.
- Open Accessibility in the admin menu.
- Press Scan my site.
There is nothing to configure.
FAQ
-
Does this make my site accessible?
-
No, and be wary of anything that claims it will. It finds and explains a specific set of failures. Fixing them is real work, and a clean result here means the automated checks passed — not that your site is accessible. The plugin tells you exactly which questions it could not answer.
-
Does it slow my site down?
-
No. The plugin adds nothing whatsoever to your front end — no scripts, no styles, no database queries for visitors. It only runs inside wp-admin, and only while you are looking at its screen.
-
Is this an accessibility overlay or widget?
-
No. Overlays attempt to patch your site at runtime for visitors and have been widely shown not to work; one major vendor has faced FTC action. This plugin changes nothing on your site. It tells you what is broken and shows you how to fix it properly, in your own theme.
-
Will it edit my theme for me?
-
No, deliberately. It shows you the code and where it goes. A plugin that rewrote your templates automatically would be one bad guess away from breaking your site, and it would also disqualify the tool from being an evaluation tool at all.
-
Who can run a scan?
-
Anyone who can edit posts, because the people who introduce accessibility problems are usually the people writing content. The capability is filterable via
exhibit_a_capability. -
Does it work on a site that is not public yet?
-
Yes. Because the scan runs in your browser using your own session, it works on staging sites, sites behind HTTP auth, and pages that require login — none of which an external scanner can reach.
-
Does it help with the European Accessibility Act or the ADA?
-
It helps with the part of both that can be tested automatically. The European Accessibility Act, in force since 28 June 2025 for online shops selling to EU consumers, points to WCAG 2.1 Level AA through the standard EN 301 549, and US accessibility claims under the ADA almost always cite WCAG too. This plugin tests 27 WCAG 2.1 A and AA rules and shows how to fix each failure. It cannot tell you that your site complies with either law, and nothing automated can: about two thirds of barriers need a person to judge them.
-
Does it check WooCommerce product and checkout pages?
-
It scans your home page and a sample of each public content type, including WooCommerce products, and its fixes cover WooCommerce templates. The cart and checkout depend on a shopping session, so check those with the free Limen Chrome extension, which audits a page exactly as your browser shows it, including logged-in and checkout pages: https://chromewebstore.google.com/detail/limen-accessibility-audit/ghiolennoknelppjjicdmnhgkhogicol
-
What standard does it check?
-
WCAG 2.1 Level A and AA. Not 2.2, and not 2.0 — 27 rules implemented against 2.1, and the plugin does not claim coverage it does not have.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“Limen Accessibility Audit” is open source software. The following people have contributed to this plugin.
Contributors
Translate “Limen Accessibility Audit” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.2
- The plugin’s description, tags and FAQ now say plainly what it is: a free accessibility checker for WordPress and WooCommerce. New answers on the European Accessibility Act, the ADA, and WooCommerce checkout pages.
- A single line under the scan results invites a review on WordPress.org. It is part of the plugin’s own screen only: no admin notice, no pop-up, and nothing stored.
- No change to the checks or their results.
1.0.1
- Fix: a link inside aria-hidden=”true” that also has tabindex=”-1″ is no longer reported as a focusable hidden element. This is the recommended pattern for a redundant product-card image link, and it matches axe-core. A plain link or a tabindex=”0″ element inside aria-hidden is still reported.
- Fix: fewer false reports. A control inside