Title: Limen Accessibility Audit Author: limenae Published: September 22, 2026 Last modified: September 22, 2026 --- Search plugins ![](https://ps.w.org/limen-accessibility-audit/assets/banner-772x250.png?rev=3706604) ![](https://ps.w.org/limen-accessibility-audit/assets/icon-256x256.png?rev=3706600) # Limen Accessibility Audit By [limenae](https://profiles.wordpress.org/limenae/) [Download](https://downloads.wordpress.org/plugin/limen-accessibility-audit.1.0.0.zip) * [Details](https://wordpress.org/plugins/limen-accessibility-audit/#description) * [Reviews](https://wordpress.org/plugins/limen-accessibility-audit/#reviews) * [Installation](https://wordpress.org/plugins/limen-accessibility-audit/#installation) * [Development](https://wordpress.org/plugins/limen-accessibility-audit/#developers) [Support](https://wordpress.org/support/plugin/limen-accessibility-audit/) ## 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 [⌊The scan result: confirmed failures separated from checks that need a person.⌉⌊ The scan result: confirmed failures separated from checks that need a person.⌉[ The scan result: confirmed failures separated from checks that need a person. [⌊A finding expanded, with the WordPress-specific fix ready to copy.⌉⌊A finding expanded, with the WordPress-specific fix ready to copy.⌉[ A finding expanded, with the WordPress-specific fix ready to copy. [⌊The honesty panel listing what automated testing cannot determine.⌉⌊The honesty panel listing what automated testing cannot determine.⌉[ The honesty panel listing what automated testing cannot determine. ## Installation 1. Install and activate the plugin. 2. Open **Accessibility** in the admin menu. 3. 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. ### 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 * [ limenae ](https://profiles.wordpress.org/limenae/) [Translate “Limen Accessibility Audit” into your language.](https://translate.wordpress.org/projects/wp-plugins/limen-accessibility-audit) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/limen-accessibility-audit/), check out the [SVN repository](https://plugins.svn.wordpress.org/limen-accessibility-audit/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/limen-accessibility-audit/) by [RSS](https://plugins.trac.wordpress.org/log/limen-accessibility-audit/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.0 * First release. 27 WCAG 2.1 A/AA checks, WordPress and WooCommerce remediation, in-browser scanning, no front-end footprint. ## Meta * Version **1.0.0** * Last updated **1 day ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.1.2** * PHP version ** 7.4 or higher ** * Tags * [a11y](https://wordpress.org/plugins/tags/a11y/)[accessibility](https://wordpress.org/plugins/tags/accessibility/) [audit](https://wordpress.org/plugins/tags/audit/)[compliance](https://wordpress.org/plugins/tags/compliance/) [wcag](https://wordpress.org/plugins/tags/wcag/) * [Advanced View](https://wordpress.org/plugins/limen-accessibility-audit/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/limen-accessibility-audit/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/limen-accessibility-audit/reviews/) ## Contributors * [ limenae ](https://profiles.wordpress.org/limenae/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/limen-accessibility-audit/)