Lumadro Accessibility Ledger keeps the record that accessibility work usually leaves scattered\nacross emails and memory. It finds specific WCAG 2.1 AA failures, helps you fix them\nin your actual content, and writes every step into an append-only ledger you\ncan export: each finding with the success criterion it fails, each change with\nits before and after, the date, who approved it, and whether AI drafted it.<\/p>\n\n
The European Accessibility Act has applied since 28 June 2025 to many products\nand services sold to consumers in the EU, online shops among them, wherever the\nseller is based. Its technical reference is WCAG 2.1 level AA, through EN 301 549.\nWhen someone asks what you have done about accessibility, the answer should be\na document, not a feeling.<\/p>\n\n
It does not make your site legally compliant, and no plugin can.<\/strong> It finds\nspecific problems, helps you fix them properly, and documents the effort in a\nform you can show someone, with the tool's own limits written into it.<\/p>\n\n This is not an accessibility overlay.<\/strong> It adds nothing to the front end and\ndoes not change what visitors see at runtime. It changes the underlying content.<\/p>\n\n Site scan.<\/strong> Reads every published post and page and every library image, in\nthe background, and fetches each published page once to check what the theme\nadds. It finds:<\/p>\n\n Browser check.<\/strong> Loads your pages in your own browser tab and runs the open\nsource axe-core engine on them. It sees what visitors see: computed colour\ncontrast, and forms and content that JavaScript builds after the page loads,\nsuch as a block checkout. It then probes what axe-core cannot: whether the page\nscrolls sideways at 320 pixels wide (reflow), whether elements show a visible\nchange when they take focus, whether clickable elements can be reached from the\nkeyboard, and whether content that opens on focus closes with Escape. These are\nlisted for review, never as proven failures. Each run starts with the home page\nand shop pages, then pages never checked, then those checked longest ago, so\nrepeated runs work through the whole site; the browser check screen lists pages\nby when they were last checked, and the report says how many never were.\nNothing is sent to any other service.<\/p>\n\n AI drafts the part that is slow to write by hand: alt text. It uses your own\nprovider key through WordPress core's AI Client, so there are no credits and no\nper-fix charges; you pay your provider directly, at cost, for any volume.\nScanning, the browser check and the reports work with no AI configured at all.<\/p>\n\n Fixes go where the problem is. A library image's alt text is used wherever it is\nplaced from then on. An image already placed in a post is fixed in that post,\nwith a normal post revision, and if the library already describes that image\nwell, its description is offered without an AI call.<\/p>\n\n The free plugin is complete for fixing and recording work one item at a time.\nPro, a separate paid plugin, adds:<\/p>\n\n Pro uses the same bring-your-own-key AI, with no credits or per-fix charges.<\/p>\n\n The site scan checks 10 of the 50 WCAG 2.1 level A and AA success criteria. The\nbrowser check adds partial checks of a few more on the pages it loads, and the\nreport says exactly which and how far. The rest need a person, and the plugin\nlists every one of them by name on its \"Coverage and limits\" screen and inside\nevery report. Passing the automated checks does not mean your site conforms.<\/p>\n\n We would rather tell you that than let you believe otherwise.<\/p>\n\n Your AI provider (optional).<\/strong> Drafting alt text uses the provider you connect\nyourself under Settings > Connectors, through WordPress core's AI Client. Only\nwhen you ask for drafts, the plugin sends the provider the image (the file from\nyour media library, or its public URL on your own site), the image's file name,\ncaption, description and current alt text, and the title, language and nearby text of the published page it\nappears on. Nothing from password-protected or private content is sent. No data\nis sent to the provider while scanning, running the browser check or building\nreports, and nothing is sent at all if no provider is connected. The provider's\nown terms of service and privacy policy apply; see your provider's website (for\nexample https:\/\/openai.com\/policies\/, https:\/\/www.anthropic.com\/legal or\nhttps:\/\/policies.google.com\/).<\/p>\n\n When WordPress's AI Client is missing or has no provider set up, and the\nseparate AI Services plugin is installed with a provider, drafting uses that\ninstead. It sends\nthe same text (the image's file name, caption, description, current alt text\nand the page context above) but not the image itself, only when you ask for\ndrafts, to the provider configured in AI Services, under that provider's terms.<\/p>\n\n No licensing or update service.<\/strong> This plugin contains no licensing code and\ncontacts no licensing or update service; it updates from WordPress.org like any\nother plugin.<\/p>\n\n The browser check and the site scan contact no outside service: the scan only\nfetches your own site's pages, and axe-core runs in your own browser.<\/p>\n\n No. Overlays modify the page for visitors at runtime and are widely criticised by\naccessibility practitioners for not achieving conformance. This plugin changes\nthe content itself and adds nothing to the front end.<\/p><\/dd>\n No, and be suspicious of anything that says it does. Compliance is a legal\njudgement about your whole service. This plugin finds and helps fix specific\ntechnical failures and documents the work. That documentation may be useful\nevidence of effort. It is not a certificate and it is not legal advice.<\/p><\/dd>\n The date and scope of the last scan and browser check, open findings grouped by\nsuccess criterion and page, the complete change log, and the criteria that were\nnot checked, with the reason. You can download it as Markdown; Pro adds JSON\nand a CSV of the change log.<\/p><\/dd>\n Partly, through the browser check. It only covers the pages it loads, in one\ndesktop-width view, and text over images or gradients is listed for you to check\nby eye.<\/p><\/dd>\n Partly. The browser check focuses up to 60 elements on each page it loads and\nlists those that show no visible change, and lists elements that look clickable\nbut cannot take keyboard focus. It does not press the Tab key, so keyboard\ntraps and focus order still need a person using a keyboard, and it cannot tell\nwhether a focus style is easy to see.<\/p><\/dd>\n The site scan does not: it reads your stored content. The browser check does,\nonce the page has finished loading. It does not fill forms in or step through a\ncheckout, and a WooCommerce checkout only shows its form when the cart has\nsomething in it, so add a product to your cart first.<\/p><\/dd>\n Not unless you explicitly choose to, one item at a time, in the media library\nor in a post. (Pro's bulk accept cannot touch text a person wrote either.)<\/p><\/dd>\n No. axe-core is bundled with the plugin and runs in your browser, on your own\nsite's pages. Results go only to your own site.<\/p><\/dd>\n Editors and administrators. Accepting, rejecting or undoing a change also needs\npermission to edit that particular post or image, so a draft for content you\ncannot edit is not shown to you. Settings are for administrators only.<\/p><\/dd>\n By default the change log and scan history stay in your database, because they\nare your evidence of the work. An administrator can tick \"Delete all Lumadro\nAccessibility Ledger data when the plugin is deleted\" on the dashboard to\nremove them on deletion. Alt text already\nwritten is never removed: it is part of your content. On multisite each\nsite decides for itself.<\/p><\/dd>\n You pay your AI provider directly for the drafting you use, and nothing to us for\nit. There is no credit system.<\/p><\/dd>\n\n<\/dl>\n\n\nThe ledger<\/h4>\n\n
\n
How it finds problems<\/h4>\n\n
\n
How it fixes them<\/h4>\n\n
Nothing changes without you<\/h4>\n\n
\n
Lumadro Accessibility Ledger Pro<\/h4>\n\n
\n
How much of WCAG this covers<\/h4>\n\n
External services<\/h3>\n\n
Third-party libraries<\/h3>\n\n
\n
\n
\n
Is this an accessibility overlay?<\/h3><\/dt>\n
Does it make my site EAA or ADA compliant?<\/h3><\/dt>\n
What is in the report?<\/h3><\/dt>\n
Does it check colour contrast?<\/h3><\/dt>\n
Does it check keyboard access and visible focus?<\/h3><\/dt>\n
Does it check forms built by JavaScript?<\/h3><\/dt>\n
Will it overwrite alt text I wrote myself?<\/h3><\/dt>\n
Does the browser check send my pages anywhere?<\/h3><\/dt>\n
Who can use it?<\/h3><\/dt>\n
What happens to my data if I delete the plugin?<\/h3><\/dt>\n
What does it cost to run?<\/h3><\/dt>\n
0.1.1<\/h4>\n\n
\n