Accessibility Overlay vs Accessibility Checker: Which One Does Your WordPress Site Need?

The short answer

An accessibility overlay adds a toolbar that changes your site inside each visitor’s browser. An accessibility checker finds the problems in your content and theme so you can fix them at the source. If you want a site that people with disabilities can use, and one you can defend if a complaint arrives, start with a checker. An overlay can sit on top as an extra, but it can’t stand in for the fixes.

Why this question comes up

Many WordPress site owners first hear about accessibility through an ad promising compliance with one line of code, or through a news story about a lawsuit against a business like theirs. Both push you toward a quick fix, and the quick fix on offer is usually an overlay.

A quick note on where this article comes from: it’s published by MantraBrain, the team behind Lumtera, a free accessibility checker for WordPress. The comparison below sticks to what each type of tool does, with sources you can check yourself, because picking the wrong tool here can cost far more than a plugin license.

What is an accessibility overlay?

An accessibility overlay, often called an accessibility widget, is a script you add to your site that loads a toolbar for visitors. People can use it to make text bigger, raise contrast, switch to a dyslexia-friendly font or pause animations. Some overlays also try to repair problems automatically, for example by guessing alt text for images.

The key detail is where the changes happen. They run in the visitor’s browser after the page has loaded, and your own content stays exactly as it was.

Picture a product page where the Add to cart button is only a shopping bag icon, with no text label in the code. A screen reader user hears “button” and nothing more. An overlay can let them enlarge the icon or switch to high contrast, but the button still has no name in your HTML, so they still can’t tell what it does.

What is an accessibility checker?

An accessibility checker scans your pages against the Web Content Accessibility Guidelines (WCAG), the standard most accessibility laws point to, and lists what’s wrong. Typical findings include images without alt text, links that only say “click here”, headings that skip levels, text with too little contrast, form fields with no label and menus you can’t leave with a keyboard.

Take the same shopping bag button. A checker flags it as a button with no accessible name and tells you which WCAG rule it breaks (4.1.2, Name, Role, Value). You add a label once, and from then on every visitor, every screen reader and every search engine gets the fixed version.

Checkers have limits, and a good one admits them. Software can tell that an image has no alt text, but not whether the alt text you wrote describes the image well. Some WCAG criteria will always need a person to judge them.

Accessibility overlay vs checker at a glance

The table below summarizes the main differences.

	Accessibility overlay	Accessibility checker
What it is	A script that adds a toolbar for visitors	A tool that scans your pages for WCAG issues
Where changes happen	In each visitor’s browser, after the page loads	In your content and theme, at the source
Fixes missing labels and alt text in your code	No	Yes, with your review
Screen reader users	May clash with tools they already use	Get the fixed page, with nothing extra loading
Effort required	Little after setup	Fix issues, then re-check as you publish
Stops ADA lawsuits	No	No tool can promise that, but it removes the barriers lawsuits describe

 

Do accessibility overlays prevent ADA lawsuits?

No, and the 2025 numbers make that clear. EcomBack’s annual report counted 3,948 ADA website lawsuits in 2025, and 983 of them (24.9%) were filed against websites that already had an accessibility widget installed. That’s roughly one lawsuit in four.

The reason is simple. A complaint describes a specific barrier, such as a checkout that can’t be finished with a keyboard or a button a screen reader can’t name. A toolbar on top of the page doesn’t remove that barrier from the code.

Lawsuits overall are rising too. Plaintiffs filed 3,117 website accessibility lawsuits in US federal court in 2025, 27% more than in 2024, according to Seyfarth Shaw. UsableNet also found that 1,427 lawsuits in 2025 targeted companies that had been sued before, which shows that a one-time fix isn’t enough when you keep publishing new content. Trackers count cases differently, so the totals vary between reports, but they agree that filings rose in 2025.

What the law asks for in 2026

The rules differ by country, but they keep pointing to WCAG.

• European Union: the European Accessibility Act has applied since 28 June 2025 to many products and services sold in the EU, online shops included. Its web requirements point to EN 301 549, which uses WCAG 2.1 AA. Businesses are also expected to publish an accessibility statement. Microenterprises providing services, meaning fewer than 10 employees and annual turnover or balance sheet total under 2 million euros, are exempt from the service requirements.
• US state and local government: the ADA Title II rule requires WCAG 2.1 AA by 26 April 2027 for entities serving 50,000 people or more, and by 26 April 2028 for smaller entities and special districts. The Department of Justice set these dates in April 2026, when it extended the original deadlines by one year.
• US private businesses: ADA Title III has no technical standard written into its regulations. In practice, many accessibility audits, demand letters and settlements use WCAG 2.1 AA as the reference point.

None of this is legal advice. If you’ve received a demand letter, talk to a lawyer who handles accessibility cases.

When does an overlay make sense?

A display toolbar isn’t always a problem on its own. Some visitors like having controls on the page. The trouble starts when the toolbar is treated as the accessibility work itself, or when its automatic repairs change the page in ways that get in the way of a visitor’s own assistive technology.

The European Disability Forum and the International Association of Accessibility Professionals made the same point in a joint statement: most overlay features copy settings that browsers and operating systems already offer, and overlays don’t make a website accessible or compliant with European accessibility law. Hundreds of accessibility professionals have also signed the Overlay Fact Sheet, which advises against relying on overlays. Fix the content first, then decide whether a toolbar adds anything for your audience.

How to check and fix a WordPress site with Lumtera

Lumtera is a free accessibility checker for WordPress from MantraBrain. It adds nothing for visitors unless you choose to add one of its blocks, so there’s no overlay and no extra script on your pages. Here’s a simple workflow for a first pass.

1. Install Lumtera from WordPress.org. It’s free and needs no account.
2. On the Lumtera Overview screen, click Check all content. The Content report then lists your posts and pages with the worst ones first, so you know where to start.
3. Open your home page while logged in and choose Accessibility in the admin bar. Review mode checks the page as visitors see it, with your theme. It numbers every keyboard Tab stop, opens your menus and pop-ups from the keyboard and shows what a screen reader would list.
4. Fix issues one at a time. Lumtera shows each change before it’s saved, keeps it as a revision and lets you undo it. If a problem comes from your header, footer or menu, you can fix it once there instead of on every page.
5. Work through the guided checklists for the things software can’t judge, then publish an accessibility statement with the built-in generator. It has templates for the EAA, ADA Title II, UK public sector rules and AODA.
6. Turn on the weekly email summary so new problems don’t pile up as you publish.

To be clear about what software can cover: with review mode, Lumtera’s automated checks cover 37 of the 55 WCAG 2.2 A and AA success criteria, fully or in part. The rest need a person, which is why the checklists exist. A score of 100 in Lumtera means no automated issues were found. It doesn’t mean your site is compliant.

The Lumtera team tested it against the W3C’s ACT rules test cases, where the right answers are known. On the 21 rules its checks cover, it found 98% of known failures, with 4 false alarms in 222 clean examples. Those are the team’s own tests, not an independent audit, and the full method and the rules Lumtera doesn’t check are published on the Lumtera accuracy page.

If you run an agency or an online shop, Lumtera Pro adds scheduled checks across many pages, checkout form tests, an evidence log, a VPAT 2.5 conformance report and white-label client reports. For a limited time, the code WPDEALHUNT takes 50% off Pro.

Frequently asked questions

What is the difference between an accessibility overlay and an accessibility checker?

An overlay changes how your site looks in each visitor’s browser and leaves your content as it is. A checker finds accessibility problems in your content and theme so you can fix them permanently, for every visitor.

Are accessibility overlays bad?

They aren’t a fix. Overlays are often sold as a way to become compliant, but they can’t deliver that because they don’t change your content, and some interfere with the screen readers and settings disabled people already use. If you keep a toolbar, treat it as an optional extra on a site you’ve already fixed.

Does an accessibility widget make my site ADA compliant?

No. About one in four ADA website lawsuits in 2025 named a site that already had a widget installed. No tool, overlay or checker, makes a site compliant by itself.

What is the best free accessibility checker for WordPress?

It depends on how you work. Lumtera checks content as you write, tests the live page from the keyboard and lets you fix issues with a preview and undo, all for free. Equalize Digital Accessibility Checker is another well-known option, and WP Accessibility by Joe Dolson fixes common theme issues. Try one on a staging copy of your site and see which fits.

Can I use an overlay and a checker together?

Yes. Use the checker to find and fix the real issues, and keep a toolbar only if your visitors find it useful.

Will Lumtera slow down my site?

No. Checks run in the WordPress admin, and visitors load no Lumtera script or stylesheet unless you add one of its blocks, shortcodes or optional site fixes.

The bottom line

An overlay changes how your site looks to some visitors. A checker helps you change what your site is. If you’re starting today, install a checker, fix the pages people use most, like your home page, contact form and checkout, and build from there.

You can install Lumtera free from WordPress.org and run your first full scan in a few minutes.