Lumtera – Accessibility Checker – WCAG, ADA, EAA and Section 508 Compliance
by MantraBrain 1 (0 reviews)

Lumtera – Accessibility Checker – WCAG, ADA, EAA and Section 508 Compliance

Accessibility checker for WCAG 2.2, ADA and EAA. Find issues as you write and on the live page, then fix them with a preview and undo. No overlay.

Lumtera ranks #62,854 among WordPress.org plugins with 1+ active installations, is #329 of 765 in the Accessibility category, a 1/5 rating from 0 reviews, and was last updated Oct 2, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1
v1.2.2 Current Version v1.2.2
Updated 4 weeks ago Last Update on 02 Oct, 2026
Refreshed 2 days ago Last Refreshed on
#329 of 765 in Accessibility Actively maintained
View on WordPress.org
Rank
#62,854
— No change
Active Installs
1+
— No change
KW Avg Position
93.3
0.6 worse
Downloads
380
+1 today
Support Resolved
0%
— No change
Rating
20%
Review 1 out of 5
1 (0 reviews)

Next Milestone 10

Total Progress 20%
0+ 10+
49,917
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

  • Exact install estimates within tiers
  • Track install growth over time
  • Milestone progress predictions
Upgrade to Pro
Need 8 more installs to reach 10+

Rank Changes

61,760 64,131 66,502 68,872 71,243 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
53,451 58,170 62,889 67,608 72,327 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Current #62,854
Change
Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Active Installs 0,000,000+
Growth +0.0%
Peak 0,000,000

Downloads Growth

0 10 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
0 10 17-10-2026 18-10-2026 19-10-2026 20-10-2026 21-10-2026 22-10-2026 23-10-2026 24-10-2026 25-10-2026 26-10-2026 27-10-2026 28-10-2026 29-10-2026 30-10-2026 31-10-2026 01-11-2026
Downloads
Growth
Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

1.0
0 reviews
Overall 20%
5
0 (0%)
4
0 (0%)
3
0 (0%)
2
0 (0%)
1
0 (0%)

Frequently Asked Questions

Common questions about Lumtera – Accessibility Checker – WCAG, ADA, EAA and Section 508 Compliance

No tool can do that on its own, and you should be wary of any that claims to. Lumtera finds the problems automation can reliably detect, explains them and helps you fix them. Meeting WCAG also needs manual testing (Lumtera's guided checklists help), an accessible theme and ongoing care. A score of 100 means "no automated issues found", nothing more.
No. An overlay adds a toolbar or script that changes your pages in each visitor's browser. It doesn't fix the underlying content, and it can get in the way of the assistive technology people already use. Lumtera adds nothing for visitors: it finds problems in your content and theme, explains them, and helps you fix them at the source. The optional site fixes change the HTML your server sends, the same for everyone, and each one is explained.
Yes. Lumtera checks against WCAG 2.2 at levels A and AA, which builds on WCAG 2.1 and 2.0. Its checks include criteria that are new in WCAG 2.2: focus not obscured (2.4.11), dragging movements (2.5.7), target size (2.5.8), redundant entry (3.3.7) and accessible authentication (3.3.8). Each finding names the success criterion it relates to, and the check reference lists them all.
WCAG 2.2 has 55 success criteria at levels A and AA. With review mode's whole-page checks, Lumtera's automated checks cover 37 of 55 of these criteria, fully or in part. The checks of saved content alone cover 25 of 55 criteria. "Covers" means a check looks at that criterion; it does not mean your site meets it. The rest need a person: for example, whether alt text is accurate or captions match the audio. Lumtera's guided checklists walk you through these, and record who checked what and when.
Yes. The EAA has applied since 28 June 2025 to many products and services sold in the EU, online shops included, and it points to EN 301 549, whose web requirements are WCAG 2.1 AA. Lumtera checks against WCAG 2.2 A/AA, which builds on 2.1, and adds the two things the EAA asks you to publish: Accessibility statement: WCAG 2.1, WCAG 2.2 or EN 301 549 as the standard, with templates for the EAA, UK public sector (PSBAR), ADA Title II and AODA. Known problems are pre-filled from your results. You choose the conformance status; it never says "fully conformant" on its own. Accessibility feedback form: a block and the [lumtera_feedback] shortcode. It works without JavaScript, has spam protection, and stores messages on your site in a Feedback inbox with reference numbers, statuses, replies and a retention period you choose. These tools support your conformance work. They are not legal advice.
The US Department of Justice's Title II rule asks state and local governments to meet WCAG 2.1 AA on their websites. The dates were moved in 2026: 26 April 2027 for entities serving 50,000 people or more, and 26 April 2028 for smaller ones and special districts. Lumtera checks against WCAG 2.2 A/AA, which builds on 2.1. It also has an ADA Title II statement template and exception tags: record which exception you believe applies to a post or file, with a note. Tagged items stay in every total and report, marked "Exception claimed".
The web requirements of both point to WCAG: WCAG 2.0 AA for the US Section 508 standards, and WCAG 2.1 AA for EN 301 549. Lumtera checks against WCAG 2.2 A/AA, which builds on both versions, and the statement generator can name EN 301 549 as the standard. Lumtera Pro's VPAT 2.5 conformance report is the WCAG edition; it doesn't include separate Section 508 or EN 301 549 tables.
We tested it ourselves against the W3C's ACT rules test cases, whose right answers are known. On the 21 W3C ACT rules its checks cover, Lumtera found 98% of known failures at any severity (130 of 132: 95 as errors and 35 for review), with 4 false alarms in 222 clean examples. Rules outside Lumtera's checks were tested too and are listed as gaps. False alarms waste your time, so we also ran Lumtera on 529 pages that meet WCAG 2.2 AA or nearly so: WAI-ARIA and GOV.UK examples, WordPress default themes and WooCommerce. After our own triage, review mode raised no false errors there; the editor's check of raw content still raised 8, on markup a script changes after the page loads. Where a check isn't sure, it says "Needs review" rather than raising an error. See the method and full results.
No. A visitor's page view runs no Lumtera database query and loads no Lumtera script or stylesheet, unless you add one of its blocks or shortcodes, the optional statement link in the footer, or an optional site fix. Review mode's scripts load only for logged-in users who can edit the page, and only when they open it. Checks run in the admin: when a post is saved, and in batches when you click Check all content. The weekly jobs run through WP-Cron.
Yes. In the block editor, Lumtera has a sidebar that checks as you type, jumps to each block and offers one-click fixes. Elementor gets its own panel in the editor, which checks unsaved changes. Tested on real installs: Elementor, Beaver Builder, SiteOrigin Page Builder, Brizy, Visual Composer Website Builder, Live Composer, Zion Builder, and the block libraries Spectra, Kadence Blocks, GenerateBlocks, Stackable, Otter, Essential Blocks, Greenshift and Kubio. Divi 4 (Divi 5 layouts are blocks), Bricks, Oxygen 2–4 and WPBakery are supported through their documented APIs. Other builders that output their layout through WordPress's content filter are checked too. Oxygen 6 and Breakdance aren't supported yet; review mode still checks their pages as rendered. Advanced Custom Fields values are checked with the post. Lumtera doesn't change content a page builder manages; it tells you what to fix in the builder.

Sign In / Register

You need to sign in or register to use this feature.