Free WordPress pluginv1.0.0

Fix the page,
not the symptom.

Accessibility Remediation scans your WordPress pages against WCAG 2.2, shows every issue on a live preview of the real page, and proposes changes to your own markup that you review before anything is applied. Nothing is added to your front end for your visitors.

WordPress
6.8 or newer
PHP
8.1 or newer
Licence
GPL‑2.0‑or‑later
Outbound requests
None
The plugin's report screen. A score of 54 out of 100 sits beside a note explaining that it counts only what automated checks can settle. Below it, four figures — 386 barriers found, 169 needing a person to look, 3 fixed, 41 checks available — then charts of findings by severity, what comes up most, and which pages have the most to do.
The report. Every bar opens the findings behind it.

01The difference

An overlay hides the problem.
This one fixes it.

There is a whole category of plugin that drops a script onto your site and layers a widget over the top. It changes nothing underneath. We do not build those.

A widget on a broken page

  • Injects a script into your front end for every visitor.
  • Leaves the underlying markup exactly as it was.
  • Widely criticised by the disabled people it claims to serve.
  • Has drawn regulatory action.
  • Stops working the moment you remove it.

Real fixes in your own code

  • Nothing is added to your front end. Ever.
  • Changes go into your markup and your own Additional CSS.
  • Every change is previewed, diffed and reviewed by you first.
  • Alt text is written to WordPress’s own field.
  • Remove the plugin and your fixes stay behind.

02How it works

From “what’s wrong” to “fixed, and written down”

  1. 01

    Scan, twice

    A server-side pass reads the rendered HTML against a registry of WCAG rules. A second pass runs in your browser, on the page as it was actually painted, for the things no parser can know: real contrast, real target sizes, real layout.

  2. 02

    See it on the page it came from

    The inspector puts findings beside a live preview. Choosing one highlights the element it is about, so you are never guessing which paragraph or which button.

  3. 03

    Understand what you are looking at

    Every issue carries its WCAG success criterion and severity, and is labelled either auto-detected or needs manual review. Findings name themselves in readable terms rather than a long DOM path.

  4. 04

    Fix it, reversibly

    Markup fixes are shown as a preview and a diff, then stored in an override layer that never overwrites your content. Styling problems get a rule written into your own Additional CSS, where you can read, edit or delete it without this plugin.

  5. 05

    Check the fix actually worked

    After a style rule is applied the page is loaded and measured again. If your theme outranked the rule you are told that, rather than being told it is fixed.

  6. 06

    Write it down

    Generate an accessibility statement you review, edit and attest to, including the feedback contact mechanism European rules expect. The plugin never asserts conformance on your behalf.

The inspector. A list of findings on the left, each naming the element and the words on it, beside a live preview of the page on the right with the selected element outlined.
Findings beside the real page. Choosing one highlights the element it is about.

03What is in it

A complete toolkit — every part of it free

There is no locked tier. Everything below is in the plugin you install.

  • 41 checks

    36 run on the server, 5 need the rendered page. Every one is documented, including what it cannot catch.

  • Live inspector

    Findings beside a real preview, one open at a time, arrow keys to move between them.

  • Reversible fixes

    Stored in an override layer with a preview, a diff and an undo. Your content is never overwritten.

  • CSS fixes in your CSS

    Style corrections go into Additional CSS, weighted to outrank what is already there — and they say so when nothing can.

  • Bulk alt-text editor

    Every undescribed image in one list with a field beside each. It writes to WordPress’s own alt text field, so it stays behind if you remove the plugin.

  • Site-wide fixes

    Switches that supply what a theme leaves out: a skip link, a visible focus outline, a page title. Each says what it might disturb before you turn it on.

  • Whole-site runs

    Check every post and page in one background job. No page limit, because nothing is metered.

  • Repeated faults, judged once

    A fault your theme repeats on every page is grouped by the markup behind it and settled once, with a reason on the record.

  • Reading-level check

    Pages measured against Flesch–Kincaid, with somewhere to add a plain-language summary where the text is heavy going.

The images screen. A list of media items that have never been described, each row showing a thumbnail and an alt text field ready to type into.
Describe forty images without opening forty screens.
The site-wide fixes screen. A list of switches that supply what a theme leaves out, each with a note saying what turning it on might disturb.
Site-wide switches, each honest about its side effects.

04Limits

We tell you what a machine cannot check

Automated testing can only ever settle part of WCAG. Meaningful sequence, focus order, whether your alt text is actually accurate — those need a person.

It separates barriers a check settled from findings that need someone to look, and documents the coverage of all 41 checks in a panel you can read at any time. It will never report your site as compliant, because no plugin can.

It does not determine or certify compliance with the ADA, the European Accessibility Act, Section 508, AODA, the UK Equality Act, or any other law. It is a tool for doing the work and keeping a record of it. It is not legal advice, and it is not a substitute for testing with disabled users.

The accessibility statement screen. A generated draft with editable sections and a feedback contact field, awaiting the site owner's review and attestation.
A statement you attest to. Never one we assert for you.

05Privacy and price

Nothing leaves your site. Nothing is metered.

No outbound requests, ever

  • No API, no account, no telemetry, no phone-home.
  • The scanner, the fixes, the alt-text screen, the statement and the reports all run on your own server.
  • It works the same whether or not your server can reach the internet.
  • No AI. Nothing is generated and nothing is sent.

One plan. All of it. Free.

£0GPL‑2.0‑or‑later

  • No page limits, because nothing is being paid for per page.
  • No locked buttons and no upgrade prompts.
  • Bundles Action Scheduler by Automattic for background work.
Install free

06Questions

The things people ask first

Will this make my site compliant?

No, and be careful of any tool that says it will. Conformance is a property of your site and your organisation’s practices, not something a plugin can confer. This plugin helps you find issues, fix them properly, document what you did, and notice when something regresses. The rest — manual testing, testing with disabled users, editorial judgement — is yours.

Is this an accessibility overlay?

No. Overlays layer a script over your site at run time. They are widely criticised by disabled users and have drawn regulatory action. This plugin changes the underlying markup instead and adds nothing to your front end for visitors.

Can I undo a fix?

Yes. Fixes live in a reversible override layer rather than being written over your content, and each one can be reverted.

Does it use AI?

No. Nothing here is generated and nothing is sent anywhere. Where an answer depends on what your content means — what an image is for, what a link promises — the plugin says so and gives you the fastest way to write it yourself, rather than producing a plausible sentence and leaving you to notice it is wrong.

Is any of it paid?

No. Everything is free, including checking your whole site at once. There are no locked buttons and no upgrade prompts.

Where is the alt text saved?

In WordPress’s own alt text field on the media item. It applies everywhere that image is used, works with every theme, and stays behind if you remove this plugin.

Find what is actually broken.
Then fix it for real.

Building something that needs this level of care? That is what we do for clients too.