Lumadro Accessibility Ledger finds specific WCAG 2.1 AA failures, helps you fix\nthem in your actual content, and writes every step into an append-only ledger\nyou can export: each finding with the success criterion it fails, each change\nwith its before and after, the date, who approved it, and where the text came from.<\/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. Its technical\nreference is WCAG 2.1 level AA. When someone asks what you have done about\naccessibility, the answer should be a document, not a feeling.<\/p>\n\n
It does not make your site legally compliant, and no plugin can.<\/strong> It is\nnot an overlay<\/strong>: it adds nothing to the front end and changes the underlying\ncontent, not what visitors see at runtime.<\/p>\n\n Site scan.<\/strong> Reads every published post, page and library image in the\nbackground, and loads each published page once to check what the theme adds:<\/p>\n\n Browser check.<\/strong> Loads your pages in your own browser tab and runs the open\nsource axe-core engine: computed colour contrast, and content JavaScript builds\nafter loading, such as a block checkout. It then probes sideways scrolling at\n320 pixels wide, elements with no visible change on focus, clickable elements a\nkeyboard cannot reach, and content opened on focus that Escape does not close.\nThese are listed for review, never as proven failures. Each run starts with the\nhome and shop pages, then pages never checked, so repeated runs cover the site.<\/p>\n\n AI drafts alt text using your own provider key through WordPress core's AI\nClient: no credits and no per-fix charges; you pay your provider directly.\nScanning, the browser check and the reports need no AI at all.<\/p>\n\n A library image's alt text is used wherever it is placed from then on. An image\nalready placed in a post is fixed in that post, with a normal post revision.<\/p>\n\n The free plugin is complete for fixing and recording work one item at a time.\nPro, a separate paid plugin, adds bulk accept and reject (still never replacing\ntext a person wrote), scheduled re-scans with a dated history, JSON and CSV\nexports, a drafted accessibility statement, a multisite network overview and a\nportfolio of your separate sites.<\/p>\n\n The site scan checks 10 of the 50 WCAG 2.1 level A and AA success criteria; the\nbrowser check partly checks a few more on the pages it loads. The rest need a\nperson, and the plugin names every one on its \"Coverage and limits\" screen and\nin every report. Passing the automated checks does not mean your site conforms.<\/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\ntext of the published page it appears on. Nothing from password-protected or\nprivate content is sent, nor files in WooCommerce's or Easy Digital Downloads'\nprotected download folders (the lumadro_ledger_private_upload_folders filter\nadds others). Nothing is sent while\nscanning, running the browser check or building reports, or if no provider is\nconnected. The provider's own terms and privacy policy apply (for example\nhttps:\/\/openai.com\/policies\/, https:\/\/www.anthropic.com\/legal or\nhttps:\/\/policies.google.com\/).<\/p>\n\n If WordPress's AI Client has no provider and the separate AI Services plugin\nhas one, drafting uses that instead, sending the same text but not the image,\nonly when you ask for drafts, 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 site scan only fetches your own site's pages, and axe-core runs in your own\nbrowser; neither contacts an outside service.<\/p>\n\n No, and be suspicious of anything that says it does. Compliance is a legal\njudgement about your whole service. This plugin documents specific technical\nfixes; that may be useful evidence of effort. It is not a certificate and it is\nnot legal advice.<\/p><\/dd>\n Partly, through the browser check, on the pages it loads, in one desktop-width\nview. Text over images is listed for you to check by eye. It does not press the\nTab key, so keyboard traps and focus order still need a person.<\/p><\/dd>\n Not unless you explicitly choose to, one item at a time. Pro's bulk accept\ncannot touch text a person wrote either.<\/p><\/dd>\n No. axe-core is bundled and runs in your browser, on your own site's pages.<\/p><\/dd>\n Editors and administrators can read the change log and download the report,\nwhich cover the whole site, and review drafts for content they can edit.\nScanning, drafting, the browser check and settings are for administrators.<\/p><\/dd>\n By default the change log and scan history stay, because they are your\nevidence. An administrator can choose to delete them on deletion. Alt text\nalready written is never removed.<\/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
How much of WCAG this covers<\/h4>\n\n
External services<\/h3>\n\n
Third-party libraries<\/h3>\n\n
\n
\n
\n
Does it make my site EAA or ADA compliant?<\/h3><\/dt>\n
Does it check colour contrast, keyboard access and focus?<\/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
0.1.2<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n