First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3706600,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3706600,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3706604,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3706604,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3706600,"resolution":"1","location":"assets","locale":"","width":1280,"height":800},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3706600,"resolution":"2","location":"assets","locale":"","width":1280,"height":800},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3706600,"resolution":"3","location":"assets","locale":"","width":1280,"height":800}},"screenshots":{"1":"The scan result: confirmed failures separated from checks that need a person.","2":"A finding expanded, with the WordPress-specific fix ready to copy.","3":"The honesty panel listing what automated testing cannot determine."}},"plugin_section":[],"plugin_tags":[1447,1953,8533,14361,1956],"plugin_category":[34],"plugin_contributors":[281953],"plugin_business_model":[],"class_list":["post-368384","plugin","type-plugin","status-publish","hentry","plugin_tags-a11y","plugin_tags-accessibility","plugin_tags-audit","plugin_tags-compliance","plugin_tags-wcag","plugin_category-accessibility","plugin_contributors-limenae","plugin_committers-limenae"],"banners":{"banner":"https:\/\/ps.w.org\/limen-accessibility-audit\/assets\/banner-772x250.png?rev=3706604","banner_2x":"https:\/\/ps.w.org\/limen-accessibility-audit\/assets\/banner-1544x500.png?rev=3706604","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/limen-accessibility-audit\/assets\/icon-128x128.png?rev=3706600","icon_2x":"https:\/\/ps.w.org\/limen-accessibility-audit\/assets\/icon-256x256.png?rev=3706600","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/limen-accessibility-audit\/assets\/screenshot-1.png?rev=3706600","caption":"The scan result: confirmed failures separated from checks that need a person."},{"src":"https:\/\/ps.w.org\/limen-accessibility-audit\/assets\/screenshot-2.png?rev=3706600","caption":"A finding expanded, with the WordPress-specific fix ready to copy."},{"src":"https:\/\/ps.w.org\/limen-accessibility-audit\/assets\/screenshot-3.png?rev=3706600","caption":"The honesty panel listing what automated testing cannot determine."}],"raw_content":"\n
Limen Accessibility Audit checks your published pages against WCAG 2.1 Level AA<\/strong> and, for every failure it finds, shows you the specific code that fixes it in WordPress or WooCommerce.<\/p>\n\n It is built around one uncomfortable fact that most accessibility tools skate over: automated testing finds roughly a third of accessibility barriers.<\/strong> 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<\/em> from what a person still has to check, and never issues a conformance claim.<\/p>\n\n The scan runs entirely inside your browser tab. The plugin fetches your own pages from your own site \u2014 same origin, no proxy \u2014 and audits them in JavaScript on your machine.<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n 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.<\/p>\n\n All of the code is included in the plugin, unminified. The audit engine lives in the There is nothing to configure.<\/p>\n\n\n 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 \u2014 not that your site is accessible. The plugin tells you exactly which questions it could not answer.<\/p><\/dd>\n No. The plugin adds nothing whatsoever to your front end \u2014 no scripts, no styles, no database queries for visitors. It only runs inside wp-admin, and only while you are looking at its screen.<\/p><\/dd>\n 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.<\/p><\/dd>\n 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.<\/p><\/dd>\n Anyone who can edit posts, because the people who introduce accessibility problems are usually the people writing content. The capability is filterable via 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 \u2014 none of which an external scanner can reach.<\/p><\/dd>\n WCAG 2.1 Level A and AA. Not 2.2, and not 2.0 \u2014 27 rules implemented against 2.1, and the plugin does not claim coverage it does not have.<\/p><\/dd>\n\n<\/dl>\n\n\nWhat it does<\/h4>\n\n
\n
Your pages are never uploaded<\/h4>\n\n
Everything here is free<\/h4>\n\n
Stores nothing, contacts nothing<\/h4>\n\n
Source code<\/h4>\n\n
engine\/<\/code> folder as readable JavaScript.<\/p>\n\n\n\n
\n
Does this make my site accessible?<\/h3><\/dt>\n
Does it slow my site down?<\/h3><\/dt>\n
Is this an accessibility overlay or widget?<\/h3><\/dt>\n
Will it edit my theme for me?<\/h3><\/dt>\n
Who can run a scan?<\/h3><\/dt>\n
exhibit_a_capability<\/code>.<\/p><\/dd>\nDoes it work on a site that is not public yet?<\/h3><\/dt>\n
What standard does it check?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n