Find and fix while you write Free
Live checks in the block editor
A Lumtera Accessibility sidebar that re-checks your post a moment after you stop typing, and shows each problem next to the block that caused it.
Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.
Starts at 0:10: “Meet Lumtera”. Captions are on. Nothing loads from YouTube until you press play.
Overview
Lumtera adds a Lumtera Accessibility sidebar to the block editor for every content type you choose under Lumtera → Settings → General. Posts and pages are on by default, and products when WooCommerce is active. Open it from the Lumtera icon in the editor's top bar, or from the Options menu under "Accessibility checker". The sidebar shows an automated score out of 100, a headline such as "2 errors to fix", a Review coverage meter and every issue, errors first.
The checks run on your own server. About a second and a half after you stop typing, the editor sends the current blocks to Lumtera, and the sidebar refreshes with "Up to date" and the number of checks that ran. If a block keeps changing its settings on its own, a check still runs within three seconds. Changes in the result are announced to screen reader users, so the sidebar is useful without looking at it.
Each issue card has a title and a short message. Expand it to see How to fix, the markup that caused the problem, a link to the WCAG success criterion and "Why is this flagged?": why the check exists, every criterion it counts against and how sure it can be. "Report a false positive…" prepares a report you edit and post yourself; nothing is sent from your site. Select block moves to the block, Go to next issue steps through errors and review items, filter buttons for All, Errors, Review and Tips narrow the list, and dismissed items sit in their own list with a Restore button.
Why does it matter?
Most accessibility problems are added one post at a time, by people who never open an audit report. When the check runs weeks later, the author has moved on and fixing it means reopening old work. Checking while the post is still being written is the cheapest moment to fix anything.
What do you get?
- Issues appear in a sidebar while you write, grouped by severity: Error, Needs review and Tip.
- Select block and Go to next issue take you straight to the problem.
- Every issue says how to fix it in WordPress terms, with a link to the WCAG success criterion.
- "Why is this flagged?" explains each finding: why the check exists, the criteria it counts against and how sure it can be.
- A "Decorative image" switch on the Image block, so empty alt text is a decision, not an accident.
How does it work?
-
Write as usual
Open any post, page or product. Lumtera checks the content in the background — nothing changes about how you write.
-
Open the Lumtera Accessibility sidebar
Click the Lumtera icon in the editor's top bar. The sidebar shows the score, the counts, a review coverage meter and each issue with its explanation.
-
Fix and watch it clear
Jump to the block and fix it, often in one click, and the issue disappears on the next check.
Who is it for?
-
Content editors
Writers see problems in the post they are working on, while fixing them is still a small edit, without leaving the editor or learning a separate tool.
-
Teams with mixed experience
Each fix is explained in WordPress terms, such as which panel or setting to use, so an author who has never read WCAG can still act on it.
-
Authors who use assistive technology
Check results are announced after each run, and Select block announces the block it moved to, so screen reader users get the same feedback as everyone else.
Good to know
How it behaves, what it needs, and where its limits are.
- Content, not the theme
- The sidebar checks the post's own content: blocks rendered the way the front end renders them, plus shortcodes. Your header, menus and footer are checked as site parts and in review mode. When whole-page results have been saved for the post, a "Theme and page" line shows their counts, with a link to review the whole page.
- Tips and possible issues stay quiet
- Tips get no outline, and Go to next issue skips them. Findings from checks that often flag things that are fine are hidden until you tick Show possible issues.
- Outlines are each author's choice
- An administrator sets the default with "Outline blocks and widgets with issues" under Lumtera → Settings → General. Each author can switch outlines off with the toggle at the foot of the sidebar, and that choice is saved to their own WordPress preferences.
- No outside requests while checking
- While content is rendered for a check, outgoing HTTP requests are blocked, so embeds and RSS blocks are not fetched on every pause in typing. Each user can run up to 120 checks a minute; normal writing stays far below that.
- Limits
- Content over 512 KB of markup is not checked live; developers can raise the limit with the lumtera_max_check_bytes filter. A clean result means no automated issues were found, and the sidebar says so, with a suggestion to try the post with a keyboard.
Checks you will see here
-
WCAG 1.1.1 · AError
Image has no alternative text
-
WCAG 1.3.1 · ANeeds review
Heading level is skipped
-
WCAG 2.4.4 · ANeeds review
Link text is vague
Questions
Something else on your mind? Contact support
Does it slow down the editor?
No. Checks run a moment after you stop typing, on your own server, and only while the editor is open. Nothing runs for site visitors.
Does my content leave my site?
No. Lumtera has no account, no API key and no external service, and every check runs inside your WordPress installation. The only exception is optional AI suggestions, which send the image or text in question to the AI provider you connected when someone clicks for a suggestion.
Does it work in the classic editor?
Yes, in a simpler form. The classic editor gets an "Accessibility check" box below the content with a Check saved version button. It checks the last saved version, so save first, and you can dismiss an item there with a reason. Live re-checking and quick fixes are block editor features.
Which content types get the sidebar?
The ones ticked under Lumtera → Settings → General → Content to check. Any public content type can be added there, including custom post types.
Which page builders work?
Elementor, Beaver Builder, SiteOrigin Page Builder, Brizy, Visual Composer Website Builder, Live Composer, Zion Builder, Divi 4, Bricks, Oxygen 2–4 and WPBakery, plus the block libraries Spectra, Kadence Blocks, GenerateBlocks, Stackable, Otter, Essential Blocks, Greenshift and Kubio, and values in Advanced Custom Fields. Oxygen 6 and Breakdance are not supported yet. For a builder page, the sidebar says its results are for the saved layout and links to the builder.
More in “Find and fix while you write”
-
Free
One-click quick fixes
Skipped heading levels, fake lists, bold "headings", new-tab links, table headers, spacing and low-contrast text colors, fixed in one click. Every fix can be undone.
-
Free
Fixes you approve, with undo
Fix saved content from the Content report or the editor: see the change before and after, edit it, approve it, and undo it later.
-
Free
Live checks in Elementor
A Lumtera panel inside the Elementor editor that checks unsaved changes and selects each widget with a problem.
Start with the free plugin today
All 69 content checks and 33 whole-page checks, fixes you approve with undo, and the site report — free, with no account and no page limits.