Changelog

Lumtera Pro 1.2.0 needs Lumtera 1.2.1 or newer, and 1.3.0 is recommended. See Requirements.

Lumtera 1.3.0

• New: the block editor checks the rendered page, with your theme's real colors, after each save. Saving is not held up. To turn it off, switch off Check after each save in the Lumtera sidebar, or use the lumtera_editor_page_check_after_save filter for a whole site.
• New: 19 new content checks and 5 new whole-page checks, for 88 and 38: required ARIA states and values, custom controls and click handlers the keyboard can't reach, nested controls, locked text spacing, table headers, passages in another language, scroll boxes, clipped text and locked orientation. See All checks.
• Changed: the coverage meter counts only what ran. Content checks count once content is checked; whole-page checks count once a review mode result is saved with nothing open; focus checks that need the keyboard walk don't count. Its number may go down.
• Changed: a Cover block's default empty alt text is now a tip; footnote links and Image block lightboxes are no longer flagged.
• Changed: you will see more items to review after you check your content again, because of the new checks and the rendered page. The score covers a post's content only, and the sidebar now names each count on its own line.
• Changed: an Image block with empty alt text is an error again, unless something suggests it is decorative (a theme or pattern image, a template, icon size, an ornament file name or a caption).
• Changed: site fixes step aside when WP Accessibility really has the same fix on, and the Settings screen says so. That covers its skip links (when they have a target), focus outline, zoom and form labels.
• New: theme text that fails contrast can be fixed with one approved CSS rule in the nearest passing color, with Undo. Nothing in the theme or content changes.
• New: color fixes keep the hue where they can, grouped findings can be fixed together, and each rendered finding links to its check's documentation.
• New: 12 more optional site fixes, for 19, including read-more links, document links, menus that open a new tab, form labels, empty searches and a PDF warning.
• New: export and import settings with a preview and undo; network defaults for multisite; Site Health tests; Check a page at desktop or phone size; an images list, a color tester and optional AAA tips.
• New: a first-run flow with one step at a time, and an Upgrade to Pro screen. Pro tips now use what your site really has, at most one per screen, and can be dismissed.
• Faster: a logged-out visitor's page loads 3 Lumtera files instead of 132.
• Fixed: on PHP 8.1, a failed page-feature query could stop with a type error.
• Fixed: Elementor images are reported as missing alt text, not empty; links to documents accept "(PDF, 200 KB)" inside the link or just after it.

Lumtera Pro 1.2.0

• New: rendered checks without a cloud. Scheduled pages wait for a browser you control: an administrator's admin session in the background, a button, wp lumtera-pro rendered run or the tools folder. Each page says what it has had, and whoever paused the background pass can see that and resume.
• New: conformance report editions for Revised Section 508 and EN 301 549, from the same evidence. What a person must answer stays Not Evaluated until they do.
• New: Asana, ClickUp and Trello trackers. Linked issues close when a re-scan confirms a fix, with a comment, and reopen if the problem returns.
• New: Send a test issue for each tracker creates one real issue and closes it, showing that a token can write as well as read.
• New: AI rules with your own AI provider (Growth and up), off by default, one page at a time. Each answer is a Needs review note, never a failure.
• New: network settings sync (Agency and up) with preview, copy and undo. Secrets never travel.
• New: score history per page with a sparkline and a table, linking to what changed. PDFs are ordered by how many pages link to them.
• New: recurring test sessions with reminders, report presets, an executive summary and a spreadsheet CSV for Excel, and a statement limitations suggestion you use and edit yourself, with drafts in another installed language.
• New: an HTTP password for scheduled checks on a staging site, stored encrypted and tried when you save it.
• Faster: a visitor's page loads 5 Lumtera Pro files instead of 84, with Lumtera 1.3.0 or newer. With 1.2.1 or 1.2.2, Pro works as before.
• Security: the one-time pass for wp lumtera-pro rendered run no longer appears in the process list or server logs. A browser that can't reach the site stops within a minute with a plain error.
• Fixed: a queue run finished at its limit no longer looks unfinished, Approve all shows a live count, and cron through WP-CLI reads as a scheduled task.
• Fixed: the statement screen no longer contacts WordPress.org for language names; "server check only" no longer counts pages not checked yet; Compare's wording and plurals.
• Needs Lumtera 1.2.1 or newer. Lumtera 1.3.0 is recommended.

Lumtera 1.2.2

• New: when you add alt text to the posts that show an image, you choose which posts get it, so decorative copies (such as Cover backgrounds) can be left out.
• Fewer false alarms in colour contrast: modern CSS colours (color-mix(), oklch(), lab()) are read correctly, and text beside an icon, in a collapsed panel or under an image or video overlay is no longer flagged.
• Fewer false alarms in the keyboard check: focus shown on a checkbox's label, a switch's track, or a button's inner text or icon is recognised.
• Content checks no longer report markup that is never shown (<noscript>, <template>, inert). Hidden slides, drawers and menus are Needs review instead of errors.
• Links in menus, trees and tabs, menu links to "#…", and theme search buttons are no longer reported.
• Changed: more than one H1 is a tip. A dialog without a name, symbol icons, an autoplaying video that isn't muted, and an Image block with empty alt text are Needs review instead of errors.
• The dialog and pop-up check defaults to Needs review on Settings → Checks, as its findings are reported.
• Security: the feedback form refuses messages sent from another website's page.
• Saved code snippets no longer keep security tokens from the page address, so they never reach reports or share links.
• Keyboard focus stays in place after "Show all findings" in the editor, while the fix dialog applies or undoes a fix, in review mode (Check again, Dismiss, Restore, the Manual tab) and when hiding a tip.
• The editor toolbar counts match the sidebar when possible issues are hidden, and the dismiss form's help text meets AA contrast.
• The Dismissed view says why Restore is missing, and review mode says when a page has no menus or pop-ups to test.
• WP-CLI: wp lumtera issues exits with 2 for an unknown --rule or --post_type, and its help explains JUnit failures, --fail-on and exit codes.
• The lumtera/site-summary ability returns the coverage summary its description promises.

Lumtera 1.2.1

• After Check all content, your results appear first, with a summary of what was found and a link to what to fix. See Site report.
• Review mode works on the blog home page, archives, search and the shop page, and the weekly home page check opens it.
• New: a Dismissed view in the Content report shows who dismissed each issue, when and why, with Restore.
• New: choose what happens to your data when Lumtera is deleted (keep it by default, or delete everything), with a feedback export.
• Feedback replies use your statement's contact email as Reply-To, and include the reference number and the original message.
• Contrast is checked for text on a Cover block whose overlay is set to 0%.
• Issues anywhere in a synced pattern link back to their block.
• Fix at the source counts only the pages that use that part.
• WP-CLI: wp lumtera issues --fail-on sets the exit status in every format, with or without --baseline. See WP-CLI.
• Editor: the toolbar button names its counts, Escape closes the dismiss form, dismissing can be undone, and the summary block starts in its text. See Block editor sidebar.
• Clearer wording throughout.

Lumtera 1.2.0

• Faster, lighter Overview, coverage, weekly email and abilities on sites with many saved whole-page results: each saved result now keeps a small summary, so site-wide numbers no longer load every finding into memory. Results saved before this version get their summary in the background, a few at a time; the numbers are the same.
• The Fixed this week count in the weekly email no longer counts a fix that was undone.
• For add-on developers: new filters lumtera_page_result_summaries and lumtera_page_result_load, and PageResults::index(), summaries(), walk() and with_issues(). lumtera_page_result_sources still works. See Whole-page results for add-ons.

Lumtera 1.1.1

• Output buffers used while checking content always close back to where they started, even when a block, widget or shortcode leaves its own buffer open.
• No longer loads WordPress admin files it doesn't use.
• The readme lists the chat widgets Lumtera recognizes in your page's HTML, and confirms it never contacts them.

Lumtera 1.1.0

• New: a weekly home page check, off by default and one click to turn on. Your home page is checked every week on your own server; new errors show on the Overview and in the weekly email.
• Weekly email: a Fixed this week count, the home page check result and an accessible HTML layout with a plain-text copy, plus an optional one-line note about Lumtera Pro that you can switch off.
• Getting started checklist: two new steps, trying review mode on your home page and turning on the weekly email with one click. It updates as soon as a check finishes.
• A clearer Free vs Pro page (the weekly summary is free; support is in the WordPress.org forums), and 4 Pro preview screens in the menu instead of 10.
• Short Pro tips at relevant moments, which you can dismiss and which are hidden when Pro is installed. A one-time request for a review once you've made progress, which you can snooze or turn off.
• The admin menu is now called Lumtera, and the editor sidebar, Elementor panel, classic editor box and Dashboard widget Lumtera Accessibility. The Content report's Compliance view is now All findings.
• The alt text screen lists images without alt text that aren't in the Media Library. The admin bar item has a small menu with this content's counts and quick links.
• Works on SQLite, including WordPress Playground.
• Nothing moved from free to Pro: every check and tool stays free.

Lumtera 1.0.0.3

Tested feature by feature in Chrome, Firefox and Safari's engine, with fixes for what that found:

• Review mode's keyboard check can be stopped with Escape, and continues after a reload with Continue the check. See Keyboard.
• Skip link fixes on block themes: when WordPress's own skip link is switched off, the link now has a target, and there is never a second link.
• Document-link labels on sites with a port in the address.
• Keyboard focus stays in place in the guided checklist and the Elementor panel.
• Contrast over SVG images in Firefox, text spacing in Safari, and system focus rings. See In other browsers.
• The Elementor panel asks for an optional reason when dismissing, like the block editor.
• Feedback: a confirmation before deleting a message, and a warning for recipient addresses that are not valid. See Feedback form and inbox.
• The Content report's CSV export follows Show possible issues. Widget areas no longer produce "list item outside a list" false positives.

Lumtera 1.0.0.2

• More accurate checks, measured against the W3C ACT test cases. Images and SVGs named only by ARIA, form fields built with ARIA roles, invalid language codes, blocked zoom and autocomplete values are now found. Disabled controls, text shadows, short or controllable audio and menu toggle links no longer raise false errors. See How accurate is Lumtera?.
• New check: Autocomplete value is not valid (WCAG 1.3.5).
• Check all content can continue where it stopped, and lists any item that could not be checked. See Continue a check that stopped.
• A dismissed issue that comes back says why (Showing again). See Showing again.
• The weekly email summary shows when sending failed, and can be tested with Send a test summary now. See Weekly email summary.
• Faster reports on large sites, and tighter permission and privacy checks.

Lumtera 1.0.0.1

• Every inline script and style is added with WordPress's enqueue functions; nothing is printed as a raw <style> or <script> tag.
• Database queries use fixed SQL with placeholders only.
• Plugin name shortened to "Lumtera – Accessibility Checker".

Lumtera 1.0.0

First public release.

• 69 checks mapped to WCAG 2.2, built to avoid false alarms: checks a machine cannot decide are marked "Needs review", and Why is this flagged? explains each finding. See All checks.
• Block editor sidebar with live checks, one-click quick fixes, jump to block, dismiss with a reason, and a pre-publish check. Also in Elementor and the classic editor.
• Review mode on the live page, with 33 whole-page checks of the rendered page: title, language, landmarks, skip link, headings, contrast, target size, zoom, reflow, text spacing and reading order.
• Contrast everywhere: gradients, text over images, non-text and focus-indicator contrast, and suggested passing colors from your theme palette.
• Keyboard walk: every Tab stop numbered, with checks for visible focus, focus hidden under sticky headers, focus order and possible keyboard traps.
• Widget tests: menus, disclosures, dialogs, tabs and accordions operated from the keyboard, with the page restored afterwards.
• Screen reader preview of headings, landmarks, links and form fields.
• Fixes you approve: a before-and-after review, a revision for every change, a re-check after saving, and undo.
• Fix at the source: fix an issue once in a template part, synced pattern, navigation or classic menu, and re-check the pages that use it.
• Site parts: menus, widget areas, template parts, synced patterns and navigation are checked, and each issue shows where it comes from.
• Honest coverage meter: how many WCAG 2.2 A/AA criteria the enabled checks cover, shown next to the score, never merged into it. See Review coverage.
• Guided checklists for the criteria that need a person, with results saved per page and per criterion.
• Accessibility feedback form block and shortcode, with an inbox, reference numbers, statuses, replies, retention and optional Akismet.
• Accessibility statement with WCAG 2.1, WCAG 2.2 and EN 301 549 options and EAA, PSBAR, ADA Title II and AODA templates.
• ADA Title II exception tags that never hide an item from totals or reports.
• Content report with My content, Site parts and Compliance views, grouping of the same issue across pages, CSV export and a column in your post lists.
• Whole-page results saved to reports when you choose.
• Page builders and custom fields: Beaver Builder, SiteOrigin, Brizy, Visual Composer, Live Composer, Zion Builder, Divi, Bricks, Oxygen, WPBakery and Advanced Custom Fields, plus a fallback for builders that use the content filter.
• Block libraries: Spectra, Kadence Blocks, GenerateBlocks, Stackable, Otter, Essential Blocks, Greenshift and Kubio; WooCommerce product descriptions.
• Alt text manager for the Media Library.
• Optional AI drafts through the WordPress AI Client: alt text (also for many images at once), link text, headings and a plain-language summary, always approved by a person.
• Optional server-side site fixes for common theme problems (skip link, focus ring, zoom, link underlines, form labels, new-tab and document-link text), off by default.
• Blocks: Accessibility statement link, Accessibility feedback form and Plain-language summary; [lumtera_statement_link] and [lumtera_feedback] shortcodes.
• WP-CLI with exit codes, baselines that fail only on new issues, SARIF and JUnit output, and site part scans.
• REST API, hooks, and WordPress Abilities for AI assistants: read-only, plus a fix proposal that waits for a person.
• Reading level in six languages, and vague-link checks in English, German, French, Spanish, Italian, Dutch and Portuguese.
• Permissions, a "Lumtera Reporter" role for agency hubs, an optional weekly email summary and a dashboard widget.
• Personal data export and erase for dismissals and feedback; fix history is exported and anonymised.
• Multisite support, including clean uninstall across a network.

Lumtera Pro 1.1.1

• Security: client reports can be read, changed or deleted only by people with "Manage client reports", including through XML-RPC.
• Security: a page check's results can be removed only by people who may see that page, and signed-in results only by administrators who run signed-in checks.
• Security: updates are downloaded only from https addresses, and "View details" never shows markup from the store.
• Security: scheduled signed-in checks never send their one-time pass over plain http.
• Deleting Lumtera Pro also removes the daily licence check from WP-Cron.
• Client portfolio: a report link is offered only when the client site would accept the request ("Manage client reports"). Lists show the port and path, so two sites on one host can be told apart, and the limit message is right on plans without the portfolio.
• Webhooks: "Regenerate secret" asks first, and only appears for signed JSON webhooks.
• Fix approval permissions can be given only to roles that can edit content.
• The carousel motion check shows "Needs review" on Settings → Checks, as its findings are stored.
• Saving signed-in check addresses says how many were not added, and burden records name the post IDs that were not added.
• Test sessions: "1 difference to review" uses the right plural.
• With Lumtera 1.2.2, page checks share its fewer false alarms in colour contrast and the keyboard check.
• Needs Lumtera 1.2.1 or newer.

Lumtera Pro 1.1.0

• License and updates rebuilt: a new license screen (save, activate, check status, deactivate), plan and site counts, a daily license check, and updates with a changelog in View details. Existing licenses move over automatically.
• New permission: Manage client reports is needed to create, delete and share reports and to edit the conformance report. Administrators have it; give it to editors under Lumtera → Settings → Permissions. See Who can manage reports.
• Deactivating or uninstalling Lumtera Pro no longer fails when Lumtera is inactive.
• Scheduled checks: Save works while the usage tip is showing.
• Form tests can test hand-made forms that post to the same page.
• Client portfolio: sites that haven't been checked are left out of the average.
• Expanded snippets can be scrolled with the keyboard; the portfolio table fits at 1280px; clearer messages.
• Check again on the Updates screen shows a new version on the first click.
• Deleting Lumtera Pro with LUMTERA_PRO_DELETE_LICENSE frees this site's activation on the store. See Data & uninstall.
• Needs Lumtera 1.2.1.

Lumtera Pro 1.0.1

• Faster, lighter conformance report and Overview on sites with many page check results: each result now keeps a small summary, so site-wide numbers no longer load every finding into memory. Results from 1.0.0 get their summary in the background, a few at a time; the numbers are the same.
• Needs Lumtera 1.2.0 or newer. With an older Lumtera, Pro asks you to update it and stays off until you do.
• The readme says what deleting Lumtera Pro keeps, and how to remove it too. See Data & uninstall.

Lumtera Pro 1.0.0

First release. 1.0.0 also included:

• The plans are Personal, Growth, Agency and Unlimited. Personal, Growth and Agency can be a yearly or a lifetime license; Unlimited is yearly.
• Signed-in checks on every plan: 1 role on Personal and Growth, any number on Agency and Unlimited.
• A first-run checklist after a license is activated, tailored to the plan, with steps that tick themselves off.
• Plan limits that link to the plan with more, and a quiet tip at 80% of a limit. See When you reach a limit.
• A renewal reminder 30 and 7 days before a yearly license expires, on Lumtera screens only. Pro keeps working after a license expires.
• Compare scans lists the WordPress, theme and plugin updates made between two scans, as a possible cause.
• Scheduled checks keep every finding only a browser can measure from the last browser check of a page. See What scheduled checks can't do.
• The Accessibility client role can read the finished conformance report.
• Personal data exporters and erasers for fix tracking and disproportionate burden records. See Privacy.
• The fixes queue's run routes accept POST only. See REST API.

Features in 1.0.0:

• Page checks in the browser for many pages, at desktop and phone width, on the free plugin's audit engine.
• Scheduled page checks as a logged-out visitor, with key templates found automatically and a per-plan page limit.
• Signed-in checks with one-time passes and view-only test users: one role on Personal and Growth, any number on Agency and Unlimited.
• Form tests with dry-run safeguards for Contact Form 7, WPForms, Gravity Forms, WooCommerce classic checkout and plain HTML forms.
• Hover, focus and pressed-state contrast, and a runtime carousel check.
• Consistency checks across pages (Growth plan and up).
• PDF checks for the Media Library.
• Tamper-evident evidence log with verification, monthly summaries and an evidence pack.
• Scan comparison with new, fixed and persisting issues, the site parts edited in between, and the WordPress, theme and plugin updates in between.
• Test sessions with sign-off, feeding the conformance report and statement.
• Fixes queue with bulk propose, review, apply and undo, built-in fixes or your own text (AI drafts only with a connected AI provider), fix at the source, and an optional approval rule (Agency plan and up).
• Feedback response targets and disproportionate burden records.
• Email and Slack alerts, weekly digest and score history.
• Fix tracking with GitHub, GitLab, Jira and Linear.
• Ignore-everywhere rules, activity log and webhooks.
• Branded client reports and a VPAT 2.5 style conformance report on every plan.
• White-label reports, client portfolio with trends, client emails and share links (Growth plan and up).
• Multisite network overview and network license (Agency plan and up).
• Abilities for AI assistants that apply only changes a person approved, unless you allow built-in rule fixes.
• Licensing and automatic updates.