Find and fix while you write Free
Guided checklists
One guided item for each WCAG 2.2 A and AA criterion that needs a person, with steps anyone can follow, recorded per page with who checked it and when.
Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.
Overview
Guided checklists sit in two places: the Manual accessibility checks panel in the block editor's post settings sidebar, and the Manual tab in review mode on the published page. Both show the same checklist for the page: one item for each WCAG 2.2 A or AA criterion that software cannot fully decide, 54 in all, grouped under headings such as Keyboard only, Zoom to 200% and a narrow window, Screen reader, Forms and error messages, and Touch, mouse and motion. A progress line such as "12 of 54 checks recorded, 1 failed" sits on top, and a filter shows All checks, Not recorded yet or Failed.
Open an item to see about how many minutes it takes, Why it matters, Tools to use, numbered Steps and What to record for a pass, a fail and not applicable. In the editor, Open the page goes to the live page, or asks you to save the draft first. The text spacing item adds Open with test spacing, which shows the page with WCAG's test spacing applied, to you only.
Choose a Result, add an optional Note and click Save result, or Save and go to the next check. The result is saved straight away, without updating the post. Lumtera also reads which features the page has, such as a form, a video or a carousel; when items do not seem to apply, it suggests marking them Not applicable, and you untick anything the page does have before saving. Reopening an item shows who recorded the result and on what date, and Clear result removes it.
Why does it matter?
Automated checks decide only part of WCAG. Whether a page works with the keyboard alone, at 200% zoom or with a screen reader, or whether captions match the audio, needs a person to try it — and most people do not know where to start.
What do you get?
- 54 items, one per criterion that software cannot fully decide, grouped under headings such as Keyboard only, Screen reader, and Forms and error messages.
- Each item says why it matters, which free tools to use, the steps, and what Pass, Fail and Not applicable mean.
- When a page has no form, video or other feature an item is about, Lumtera suggests Not applicable. You decide.
- Results are saved per page and per criterion, with who recorded them, when, and an optional note.
- A pass or Not applicable counts as evidence in the coverage meter for 12 months, and in Lumtera Pro's conformance report.
How does it work?
-
Open the checklist
In the block editor, find the Manual accessibility checks panel in the post settings sidebar. On the published page, open the Manual tab in review mode.
-
Follow the steps
Each item says what to try and what a pass looks like.
-
Record the result
Choose Pass, Fail or Not applicable, add a note if you like, and save.
Who is it for?
-
Teams without an accessibility specialist
Each step says which keys to press or which setting to change, so an editor can test a page properly the first time, without training.
-
Key pages before a launch
Work through the checklist on the home page, a typical post, the contact form and the checkout. Pages built from the same template usually pass or fail together.
-
Agencies preparing a conformance report
Results recorded on published pages feed the VPAT 2.5 Accessibility Conformance Report in Lumtera Pro, on every plan, where only a passed manual check can mark a criterion Supports.
Good to know
How it behaves, what it needs, and where its limits are.
- What the checklist covers
- Every WCAG 2.2 A and AA criterion that automated checks cannot fully decide, each with free tools such as your keyboard, browser zoom, NVDA or VoiceOver. Results are recorded per criterion, so each one stands on its own.
- Who can record results
- Anyone who can edit the post can see its checklist and record or clear results. The test spacing preview works only for logged-in users who can edit that post; visitors never see it.
- Evidence for 12 months
- In the coverage meter, a pass or Not applicable on published content counts as evidence for that criterion for 12 months, unless a newer result failed. Manual results never change the automated score.
- Where results show
- In the panel and the Manual tab, in the Content report, where a line such as "Manual checks: 4 of 54 done, 1 failed" appears under the title, in the coverage meter, and to AI assistants through the get-manual-review-status ability.
- Privacy
- Each result stores the user who recorded it, the date and the optional note, up to 2,000 characters. WordPress's personal data export includes them. Erasing a user's data keeps the result but removes who recorded it and the note.
Questions
Something else on your mind? Contact support
Where do the results go?
They stay with the post and show in the Content report and the coverage meter. In Lumtera Pro, on every plan, results on published content also feed the VPAT 2.5 conformance report.
If a page passes every item, does it meet WCAG?
Not on its own. The results are your own evaluation record, kept with the post, not an official assessment of the page. They are a structured way to test what automated checks cannot.
Do I need special software?
Most items need only a browser and a keyboard. Screen reader items use NVDA, free for Windows, or VoiceOver, built into every Mac and iPhone. A few need a phone or tablet, or your browser's device mode.
Can I use it on Elementor or classic editor pages?
Yes, through review mode. The editor panel is in the block editor only, but the Manual tab in review mode records the same results on any page you can edit.
More in “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.
-
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.
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.