Title: Lodestone Accessibility Audit – Accessibility Checker Author: Lodestone Published: 9 de setembre de 2026 Last modified: 23 de setembre de 2026 --- Cerca extensions ![](https://ps.w.org/lodestone-accessibility-audit/assets/banner-772x250.png?rev =3687404) ![](https://ps.w.org/lodestone-accessibility-audit/assets/icon.svg?rev=3687404) # Lodestone Accessibility Audit – Accessibility Checker Per [Lodestone](https://profiles.wordpress.org/loureiro70/) [Baixa](https://downloads.wordpress.org/plugin/lodestone-accessibility-audit.1.0.12.zip) [Previsualitza](https://ca.wordpress.org/plugins/lodestone-accessibility-audit/?preview=1) * [Detalls](https://ca.wordpress.org/plugins/lodestone-accessibility-audit/#description) * [Ressenyes](https://ca.wordpress.org/plugins/lodestone-accessibility-audit/#reviews) * [Desenvolupament](https://ca.wordpress.org/plugins/lodestone-accessibility-audit/#developers) [Suport](https://wordpress.org/support/plugin/lodestone-accessibility-audit/) ## Descripció Lodestone Accessibility Audit is an accessibility checker for the person who maintains the site. It scans a page and tells you what is wrong, which WCAG 2.2 success criterion it fails, which element is at fault, and how to fix it — then keeps the record of what you found, what you fixed, and what you decided to leave alone and why. It is a scanner and a reporter, not a widget bolted onto the front end for visitors. Scanning runs in your own browser using axe-core, the same open-source engine behind most professional accessibility tooling. Your pages and your results are never sent anywhere. No account, no API key, no scanning service, no setup wizard. Activate the plugin and scan a page immediately. #### This is not an accessibility overlay Overlay widgets promise to «fix» accessibility with a line of JavaScript that rewrites your page for visitors. They are rejected by the disability community, they have been the subject of lawsuits, and they do not work. This plugin adds nothing to your front end for visitors. It shows you what is broken so that you can fix it properly, in your content and your theme. #### Which standard, and which law WCAG is the standard the rules point at, so WCAG 2.2 is what this tests against: * The **European Accessibility Act** reaches it through EN 301 549, the harmonised European standard, which incorporates WCAG. * **Section 508** incorporates WCAG 2.0 Level AA for US federal agencies and their suppliers. * Under the **ADA**, the Department of Justice’s 2024 rule adopted WCAG 2.1 Level AA for state and local government. For private businesses no rule names a version, and WCAG is the reference courts have generally worked from. WCAG 2.2 contains everything in 2.0 and 2.1, so testing against it covers all three. What no automated tool can do — this one included — is tell you that you _meet_ any of them. See the questions below. #### The accessibility statement Most of these regimes expect a published statement: what you tested, when, what you found, and what you have not fixed yet. The plugin generates one as a normal page you can edit, dated, and carrying a paragraph that says plainly which parts of the site were checked automatically and that automated testing does not cover everything. That paragraph is not configurable, because a statement that overstates what you know is worse than no statement. The free statement already carries the feedback route visitors are meant to have. Pro adds the rest of the EU model accessibility statement (Commission Implementing Decision (EU) 2018/1523): the non-compliance and disproportionate-burden sections, what is out of scope, how the assessment was made and on what date, and the enforcement body a visitor can escalate to. #### What the free version does, permanently * Scan any post, page or custom post type on demand, from the row action in your lists or from the block editor sidebar. * Re-scan automatically when you save a post in the block editor. * Full detail on every issue: the axe rule, its impact level, the WCAG 2.2 success criterion it maps to, the CSS selector, the offending markup, and a link to the fix documentation. * «Show on page»: open any issue on the real page with the element outlined and the problem named beside it. Only you see it — it is signed for you and for that issue, and checked against your permission to edit that post. * The checks axe-core cannot decide on its own, listed by name, with how many elements each one covers and a link to how to check it by hand. * A dashboard across everything you have scanned: open issues, a breakdown by severity, and the worst offending pages. * Ignore an individual issue, with a required written reason recorded against your name and the date. * Generate a plain accessibility statement page. There is no page limit, no scan quota, no trial period, and nothing that switches itself off later. If you never buy the Pro version, nothing you use today stops working. #### What Pro adds Pro is for people who have to _prove_ the work was done: a full ignore log with author, date and reason, exportable; history and trend lines showing regressions; CSV and printable audit exports; and the rest of the EU model accessibility statement. It also adds a queue that scans every published post and page from one screen, weekly or monthly re-scan scheduling, a small set of genuinely safe server-side fixes ( all off by default), WP-CLI commands for status, exports and starting a run, and a multisite network dashboard. Scans always run in a browser, because the checks need one — nothing scans unattended. #### One notice, and one menu The plugin shows exactly one dismissible admin notice, ever. It tells you where the plugin lives and retires itself the moment you open that screen. It registers one top-level menu and nothing else: every screen is a tab inside it. No banners, no countdown timers, no nags on other people’s screens, no onboarding wizard, and nothing installed or suggested that you did not ask for. We ask you for exactly one thing, once. After the scanner has completed a few scans, a panel on the plugin’s own scan screen asks whether you would rate it on WordPress. org. It is not an admin notice, it is only ever shown to editors and administrators, and whichever button you press — including «No thanks» — it never appears again. There is no activation step and no consent screen in your way. Licensing is handled by the Freemius SDK, which starts switched off: nothing is registered and nothing is transmitted unless you go and opt in, and everything works whether you ever do or not. The one thing not in our hands is that opening the upgrade page adds a Freemius« Upgrade» item under the menu while you are on it. ## Captures [⌊The dashboard: open issues by severity and the worst offending pages, across everything you have scanned.⌉⌊The dashboard: open issues by severity and the worst offending pages, across everything you have scanned.⌉[ The dashboard: open issues by severity and the worst offending pages, across everything you have scanned. [⌊Issue detail: what is wrong, the WCAG success criterion it fails, the element and the markup at fault.⌉⌊Issue detail: what is wrong, the WCAG success criterion it fails, the element and the markup at fault.⌉[ Issue detail: what is wrong, the WCAG success criterion it fails, the element and the markup at fault. [⌊"Show on page": the element outlined on the real page, with the problem named beside it. Only you see it.⌉⌊"Show on page": the element outlined on the real page, with the problem named beside it. Only you see it.⌉[ «Show on page»: the element outlined on the real page, with the problem named beside it. Only you see it. [⌊The checks axe-core could not decide on its own, listed by name, with how to check each by hand.⌉⌊The checks axe-core could not decide on its own, listed by name, with how to check each by hand.⌉[ The checks axe-core could not decide on its own, listed by name, with how to check each by hand. [⌊Ignoring an issue requires a written reason, recorded with your name and the date.⌉⌊ Ignoring an issue requires a written reason, recorded with your name and the date .⌉[ Ignoring an issue requires a written reason, recorded with your name and the date. [⌊The block editor panel: open issues for the post you are editing, and a scan from where you are.⌉⌊The block editor panel: open issues for the post you are editing, and a scan from where you are.⌉[ The block editor panel: open issues for the post you are editing, and a scan from where you are. [⌊The generated accessibility statement, dated, saying plainly what automated testing can and cannot tell you.⌉⌊The generated accessibility statement, dated, saying plainly what automated testing can and cannot tell you.⌉[ The generated accessibility statement, dated, saying plainly what automated testing can and cannot tell you. ## PMF ### Does this make my site WCAG compliant? No, and be sceptical of any tool that says it does. Automated testing detects only a portion of accessibility barriers — commonly estimated at around a third. It is very good at the things machines can check: missing alternative text, insufficient colour contrast, unlabelled form fields, broken heading structure, invalid ARIA. It cannot tell you whether your alt text is _meaningful_, whether your page makes sense when read aloud in order, or whether a custom component actually works with a screen reader. This plugin finds the automatable third and is honest about the rest, including in the statement it generates for you. What the automated part cannot catch, and how to check it by hand, is written up at https://madebylodestone.com/what-automated-accessibility-testing-misses ### Does it cover the ADA, Section 508 or the European Accessibility Act? All three point at WCAG, and this tests against WCAG 2.2, which contains WCAG 2.0 and 2.1. So the issues it finds are issues under all three. It does not decide whether you meet any of them, and no automated tool can: the ADA has no regulation naming a version for private businesses, Section 508 incorporates WCAG 2.0 Level AA, and the European Accessibility Act works through EN 301 549. What the plugin gives you is the automatable part of the evidence — what was tested, when, what was found, and a written reason against anything you chose not to fix. ### Is this an accessibility overlay or a toolbar? No. It adds nothing to your front end for visitors — the only things it ever loads there are the scanner and «Show on page», and only for a signed-in editor who asked for them. Overlays inject JavaScript that alters your pages for visitors at runtime, which is a different product with a bad reputation it has earned — they frequently break the assistive technology they claim to help, and the disability community has been consistently clear that they are not a substitute for accessible markup. This plugin only reads your pages and reports on them. ### What is the European Accessibility Act? The EAA is EU legislation, in force since June 2025, that requires a range of products and services — including many websites and e-commerce operations — to meet accessibility requirements. In practice conformance is assessed against EN 301 549, which incorporates WCAG. It generally expects you to be able to show what you tested, when, what you found, and what you decided about anything you did not fix. That evidence trail is what the ignore log and the audit export exist to produce. ### Does the plugin send my content anywhere? No. axe-core is bundled with the plugin and runs in your browser, against your own site, on your own machine. Your pages, your scan results and your ignore reasons never leave your server. The only component that could is the Freemius SDK, which handles licensing, and it starts switched off. It contacts nothing until you choose to opt in, and if you never do, it never does. Opting in is offered rather than required, it tells you exactly what it would share first (your WordPress user’s name and email address, your site address and title, your WordPress and PHP versions, and the list of plugins and themes installed), and every feature works the same either way. ### Why does the scan open my page in a hidden frame? Contrast ratios, computed styles and focus order only exist once a page has actually been laid out by a browser. There is no way to evaluate them by parsing HTML on the server, and any tool that claims to will give you wrong answers. So the scanner loads your page in an offscreen frame and measures the real rendered result. The frame is only ever created for a logged-in user with editing permission, and the scanning script is never loaded for ordinary visitors. ### Can I scan drafts? Yes. Unpublished posts are scanned through their preview link, and the result is recorded against the post itself, so its history carries over when you publish. ### Can I translate it? Yes, and it will always be free to do so. Every string is translatable and a POT file ships with the plugin. ## Ressenyes No hi ha ressenyes per a aquesta extensió. ## Col·laboradors i desenvolupadors «Lodestone Accessibility Audit – Accessibility Checker» és programari de codi obert. La següent gent ha col·laborat en aquesta extensió. Col·laboradors * [ Lodestone ](https://profiles.wordpress.org/loureiro70/) [Traduïu «Lodestone Accessibility Audit – Accessibility Checker» a la vostra llengua.](https://translate.wordpress.org/projects/wp-plugins/lodestone-accessibility-audit) ### Interessats en el desenvolupament? [Navegueu pel codi](https://plugins.trac.wordpress.org/browser/lodestone-accessibility-audit/), baixeu-vos el [repositori SVN](https://plugins.svn.wordpress.org/lodestone-accessibility-audit/), o subscriviu-vos al [registre de desenvolupament](https://plugins.trac.wordpress.org/log/lodestone-accessibility-audit/) per [fisl de subscripció RSS](https://plugins.trac.wordpress.org/log/lodestone-accessibility-audit/?limit=100&mode=stop_on_copy&format=rss). ## Registre de canvis #### 1.0.12 * New: a live preview on the WordPress.org listing. Try the plugin in your browser, with a sample page to scan, without installing anything. * The FAQ now links a guide to what automated testing cannot catch, and how to check it by hand. #### 1.0.11 * Fixed: when «Show on page» moved its panel to the top of the window to keep it off the element, it covered the WordPress toolbar. It now sits below it. * Changed: the dashboard’s one panel about Pro no longer appears on your first visit, before the plugin has done anything for you. It appears once you have ruled out an issue with a reason or published an accessibility statement, and says what Pro does with the record you are keeping. * The plugin now links its own page, madebylodestone.com/accessibility-audit, from the Plugins screen. #### 1.0.10 * New: «Show on page» beside every issue opens the page with the element outlined and the problem named in a panel beside it. Only a signed-in user who can edit that post can open it; nothing is loaded for visitors, and the page is never cached or indexed while it is shown. #### 1.0.9 * New: the checks axe-core could not decide automatically are listed by name under each scan, with how many elements each covers and a link to how to check it by hand. Until now the scan said only how many there were. Scans made before this update keep the count alone. * New: every screen of the plugin ends with a link to its support forum. * Fixed: the description of Pro promised more than Pro does. Its scan queue covers every published post, page and public content type — not taxonomy archives or any URL you name, which it never did. Its WP-CLI commands check status, export the ignore log and start a run; they do not scan, because the checks need a browser. And scheduled re-scans are worked through on the Scan queue screen, not anywhere in the dashboard. The Pro tab, the free dashboard panel and this listing now say exactly what Pro does. * Fixed: the statement this plugin builds was described as following «the EN 301 549 model form». There is no such form. EN 301 549 is the standard a site is assessed against; the statement follows the EU model accessibility statement, Commission Implementing Decision (EU) 2018/1523, and is now named as such. * Housekeeping: the Freemius SDK can no longer add a trial or affiliate-programme notice to the admin, whatever is switched on in its dashboard. The plugin’s one-notice limit now holds against settings as well as against code. #### 1.0.8 * New: once the scanner has a few scans behind it, the scan screen asks whether you would rate the plugin on WordPress.org. It is asked once per site, only of editors and administrators, and answering it either way retires it permanently. It is not an admin notice and does not appear on any screen but this plugin’s own. * Fixed: the Pro tab listed the statement’s feedback mechanism as a Pro feature. It is in the free statement and always has been. The tab now names only what Pro actually adds. * Housekeeping: the internal version constant had fallen a release behind the plugin header, which meant an updated site could keep serving the previous release’s stylesheet from cache. #### 1.0.7 * Fixed: the published accessibility statement repeated its own title. The page showed «Accessibility statement» twice, once as the page heading and once again at the top of the content. * Fixed: a statement published before the first scan said «0 pages were tested». It now says plainly that no pages have been tested yet. * The statement’s section headings are now one level up, so they sit correctly under the page title rather than skipping a level. * The listing now says which standards the plugin reports against and how they relate to the ADA, Section 508 and the European Accessibility Act, and describes the accessibility statement it generates. * Corrected the description of what the free statement contains: the feedback route for visitors is free, not a Pro feature. #### 1.0.6 * The directory name now says what the plugin is: an accessibility checker. Nothing about how it works has changed. * The Pro tab now states the 14-day money-back guarantee next to the prices, and a founding-customer code for the first 20 buyers. * Pro’s scheduled re-scans now bring the database up to date themselves after an automatic update, instead of waiting for someone to open the dashboard. #### 1.0.5 * Pro is now €149 / €399 / €999 a year for 1 / 5 / 25 sites, down from €199 / € 499 / €1,299. * The plugin now names Lodestone as its author. #### 1.0.4 * The published accessibility statement now reads «3 pages were tested» rather than «3 page(s) were tested». It is a document you put your own name to, and it should not look like nobody read it. * The same fix in the Pro full-site scan queue and its WP-CLI commands, which counted pages the same way. #### 1.0.3 * Fixed: scanning did not work on sites using WordPress’ default «plain» permalinks. The scanner built a REST URL that put its argument inside the route name, so every scan failed with a routing error. It now works whichever permalink structure you use. * The plugin’s own dashboard is now the first thing you see. Opting in to email updates is offered rather than required, and nothing is transmitted unless you choose it. * The dashboard now keeps a «Scan another page» button once you have scanned something, instead of removing every control after the first scan. * Prices are shown in euros per year on the upgrade page, matching the Pro tab, instead of being converted to a monthly figure in dollars. * Authors and contributors are no longer shown the accessibility statement tab, which needs a capability they do not have, or the Pro pitch, which they cannot act on. They keep the dashboard and can scan their own drafts. * Issues are now titled in plain English — «Images must have alternative text» rather than «image-alt». The axe rule id is still shown, and still linked to its documentation. * Fixed: the dashboard’s «nothing scanned yet» button sent Authors and Contributors to the Pages list, which they cannot open. It now points at the list their role can actually use. * Fixed: the block editor sidebar reported «1 open issues». * Fixed: «0 further checks could not be decided automatically» was printed after every clean scan. * The ignore log, CSV export and printable report now name WCAG success criteria in full («1.1.1 Non-text Content (A)») instead of printing axe’s internal tags. * The Pro description no longer lists a safe fix that the Safe fixes screen does not offer. * Clearer wording throughout on what the optional Freemius opt-in prompt is and what it shares. #### 1.0.2 * Ignoring or reopening an accessibility issue now refuses by default. Rulings on issues whose scan is missing, or on a scanned URL that is not a post, previously fell through the per-post check; they now require the Editor capability, and an issue with no scan behind it can be ruled on by nobody. #### 1.0.1 * Site-wide figures, the ignore log, the history chart and the printable report now require the Editor capability. Authors and Contributors see the dashboard scoped to their own content instead of the whole site. * The full-site scan REST endpoints now require the same administrator capability as the screen that drives them. * Class and view loading is restricted to files inside the plugin directory. #### 1.0.0 * Initial release. ## Meta * Versió **1.0.12** * Darrera actualització **fa 2 dies** * Instal·lacions actives **Menys de 10** * Versió del WordPress ** 6.4 o posterior ** * Provada fins a **7.1.2** * Versió del PHP ** 7.4 o posterior ** * Idioma * [English (US)](https://wordpress.org/plugins/lodestone-accessibility-audit/) * Etiquetes * [accessibility](https://ca.wordpress.org/plugins/tags/accessibility/)[accessibility checker](https://ca.wordpress.org/plugins/tags/accessibility-checker/) [ada](https://ca.wordpress.org/plugins/tags/ada/)[EAA](https://ca.wordpress.org/plugins/tags/eaa/) [wcag](https://ca.wordpress.org/plugins/tags/wcag/) * [Vista avançada](https://ca.wordpress.org/plugins/lodestone-accessibility-audit/advanced/) ## Valoracions Encara no s'ha enviat cap ressenya. [La vostra ressenya](https://wordpress.org/support/plugin/lodestone-accessibility-audit/reviews/#new-post) [Visualitza totes les ressenyes](https://wordpress.org/support/plugin/lodestone-accessibility-audit/reviews/) ## Col·laboradors * [ Lodestone ](https://profiles.wordpress.org/loureiro70/) ## Suport Teniu quelcom a dir? Necessiteu ajuda? [Visualitza els fòrums de suport](https://wordpress.org/support/plugin/lodestone-accessibility-audit/)