LynBro Plugins
/ Accessibility
LynBro Plugins
/ Accessibility
In April 2025 the American Federal Trade Commission ordered accessiBe to pay one million dollars for claiming its overlay made sites WCAG-compliant. This is the other kind of tool: it reads your markup, tells you what is wrong and where, corrects the handful of things that can be corrected without guessing what you meant — and is straight with you about the rest.
Free forever. Full-site scanning, the site-wide report and the export are in the free plugin — they are what the best paid tool in this category charges $74.50 a year for.
rules, each tied to a WCAG 2.2 success criterion, with why it matters and how to fix it in plain words.
There is no percentage anywhere in this plugin, because no automated scan can produce one honestly. What you get is three counts: failures we can prove from your markup, likely failures worth your eyes, and the things that need a person. A number that says “87% accessible” is the exact claim regulators have started fining people for.
The best tool in this category puts bulk scanning, the site-wide report and form-field labelling behind a paid tier. A scan that stops at twenty pages is a scan that hides the other four hundred, and for a compliance question that is worse than useless. Here it is the free plugin, for every page, for as long as you have it.
Ten fixes, every one off until you ask, every one explained on screen — what it changes and what to be careful of. None of them edits a post, a template or your database, so switching one off puts your markup back exactly as it was. Nothing here quietly rewrites your headings or invents alt text you never wrote.
No "Pro" tier, no nag screens. The features other plugins paywall are here from day one.
Missing alt attributes, of course — but also alt text that reads “image”, “billede” or “DSC_0042.jpg”, which passes every automated check and tells a blind visitor nothing. Logo links whose only content is an image with an empty alt. Image maps and bare inline SVGs.
Fields with no label, fields where the placeholder is doing the label’s job and vanishes the moment someone types, labels pointing at an id that is not on the page, and name and e-mail fields with no autocomplete — which for someone with a tremor is the difference between a form they can finish and one they cannot.
Contrast is not in your HTML; it is what your stylesheet, your fonts and the visitor’s screen produce together. So for that one we do what an auditor does and open the page. The measuring script runs only for a signed-in administrator who asked for it, on that one view. Your visitors are never sent anything.
A focus ring the theme removed and never replaced. Links and buttons inside aria-hidden that can still be tabbed to. aria-labelledby pointing at an id that does not exist. tabindex=“3” dragging the whole page out of order. Controls under 24 by 24 pixels — a criterion added at AA in WCAG 2.2, which most sites have never been measured against.
Are the captions on that video actually right? Does the page still work at 400% zoom? Can the keyboard get back out of the cookie banner? Does your checkout make people type the same address twice? Each one with an answer, a note and a date — which is what an assessment looks like, and what a scan alone never is.
Every finding, every page, as CSV or JSON, with the manual answers alongside. No row limit and no export cap. It is your site’s data; the only reason to meter it would be to sell you the rest of it back.
The four accessibility plugins WordPress sites actually run, and what they hold back.
| Feature | Lynbro Accessibility | Ally | WP Accessibility | Accessibility Checker |
|---|---|---|---|---|
| Scans every page of the site | ✓ | — | — | — |
| Site-wide report across all pages | ✓ | — | — | — |
| Labels unlabelled form fields | ✓ | ✓ | ✓ | — |
| Names the element behind each finding | ✓ | — | — | ✓ |
| Contrast measured in the browser | ✓ | — | — | ✓ |
| WCAG 2.2 target size and the other 2.2 additions | ✓ | — | — | — |
| Says plainly what a scanner cannot check | ✓ | — | — | — |
| No compliance percentage claimed | ✓ | — | ✓ | ✓ |
| Not an overlay | ✓ | — | ✓ | ✓ |
| No account required | ✓ | — | ✓ | ✓ |
| Nothing sent to the vendor | ✓ | — | — | — |
| Full export of the report | ✓ | — | — | — |
No, and nothing you can install does. It finds what can be found automatically, tells you how to fix it, fixes a few things for you if you ask, and is honest about the rest. Automated testing reaches roughly a third of WCAG; the other two thirds are the checklist inside the plugin, and the work is still yours.
Possibly not, and we would rather say so. The European Accessibility Act has applied since 28 June 2025, and in Denmark Erhvervsstyrelsen supervises it — but microenterprises, under 10 people with turnover at or below 2 million euro, are exempt for services. Plenty of small sites are simply not obliged. If you are over that line the report and the manual checks are what an assessment looks like; if you are under it, everything here still makes your site work for more people.
No, and it is built as the opposite. There is no widget, no toolbar, and no script sent to your visitors claiming to make the site compliant. The overlay industry is where the FTC’s million-dollar order against accessiBe came from, and where the class actions keep landing. What this does instead is show you the problems in your own markup.
Because contrast is not in your HTML. It is the result of your stylesheet, your fonts and the screen, and the only honest way to know it is to look at the page as a browser has drawn it. Pressing “check in browser” opens the page with a measuring script that runs once, reports back and is gone on the next load. It is only ever loaded for a signed-in administrator.
It runs in short bursts with a time budget and a memory ceiling, both checked between every page, and it stops by itself if it gets near either. Nothing about it ever runs on a visitor’s request. On a small shared host, lower the pages-per-burst setting.
Because changing an h4 to an h3 means deciding what you meant by it. A plugin that quietly renumbers your headings has made a judgement it cannot explain to you afterwards, and the same goes for writing alt text nobody wrote. Those appear in the report with the element and the reason; the call is yours.
Not for anything in this plugin. Everything here runs on your own server, which costs us nothing per site, so there is nothing honest to charge for. Nothing is capped, metered or held back for later.