Skip to main content

See the whole site Free

Honest coverage meter

Next to every automated score, a meter shows how many WCAG 2.2 A/AA criteria the checks cover, how many have evidence and how many need a person.

Watch the free tour from 0:41: Lumtera: Free WordPress Accessibility Checker for WCAG 2.2, ADA & EAA (1:12) (opens YouTube)

Lumtera: Free WordPress Accessibility Checker for WCAG 2.2, ADA & EAA

Starts at 0:41: “The overview and WCAG coverage”. Captions are on. Watch on YouTube: Lumtera: Free WordPress Accessibility Checker for WCAG 2.2, ADA & EAA

Updated for Lumtera 1.2.2 and Lumtera Pro 1.1.1.

Overview

The "Review coverage" meter sits next to the automated score on the Overview, in a compact form on the Dashboard widget, and in the block editor sidebar. It is never merged into the score. Its label counts how many of the 55 WCAG 2.2 A/AA criteria have evidence, and a sentence below says how many criteria content scans and whole-page checks cover automatically, how many of those fully and how many in part, and how many need a person.

Every number is computed from the checks your site has switched on, including the whole-page checks review mode runs. With every free check on, that is 37 of 55 criteria covered fully or in part; the checks of saved content alone cover 25 of 55. Turn a check off under Lumtera → Settings → Checks and the meter changes with it.

A criterion counts as having evidence when a manual check passed or was marked "not applicable" in the last 12 months, or when the checks that cover it found no errors or items to review on published content. A recent manual failure cancels that. The bar reaches full only when every criterion has a manual record, and then reads "Evidence recorded for all 55 WCAG 2.2 A/AA criteria", never that the site conforms.

Why does it matter?

A score of 100 sounds like a finished job. It only means the automated checks found nothing, and automated checks look at part of WCAG. Without saying what was not checked, a clean score can give site owners and clients false confidence.

What do you get?

  • With review mode, automated checks cover 37 of 55 WCAG 2.2 A/AA criteria (fully or in part); checks of saved content alone cover 25 of 55.
  • Every number is worked out from the checks your site has switched on, never typed in, so it stays true when you change settings.
  • Shown next to the score, never merged into it, on the Overview, the Dashboard widget and the editor sidebar.
  • Counts criteria with evidence: a manual pass or "not applicable" from the last 12 months, or clean results from the checks that cover them.
  • The bar is only full when every criterion has a recorded result, and even then it says "evidence recorded", not that the site conforms.

How does it work?

  1. Check your content

    Run Check all content from the Overview. The meter appears beside the score as "Review coverage".

  2. Read what it covers

    One sentence says how many criteria the automated checks cover, how many of those fully or in part, and how many need a person.

  3. Add evidence by hand

    Work through the guided checklists for the criteria a machine cannot judge. Each result you record adds to the evidence count.

Who is it for?

  • Explaining a score to a client

    Show what a clean score does and does not mean, in one sentence, next to the number itself.

  • Planning manual testing

    The criteria that need a person are the ones to work through with the guided checklists.

  • Keeping evidence current

    Manual results older than 12 months stop counting, which is a reminder to test again.

Good to know

How it behaves, what it needs, and where its limits are.

Covered is not met
Covering a criterion means a check looks at it. It does not mean your site meets it.
Your site's own number
The figures depend on which checks are switched on, so two sites can show different coverage.
How to add evidence
The meter links to the documentation on testing by hand. Results from the guided checklists are recorded with who checked what and when.
Available to assistants
The same figures are available to AI assistants through the get-coverage ability, including how many criteria have saved whole-page results behind them.
With Lumtera Pro
Pro's form tests add criteria that need a submitted form (40 of 55, on every plan), and its consistency checks on Growth and up add those that need several pages (44 of 55).

Questions

Something else on your mind? Contact support

Does covering a criterion mean my site meets it?

No. Covering a criterion means a check looks at it. Whether your site meets it depends on what the check found and on the parts only a person can judge.

Why not just show a percentage score?

A single number mixes what was checked with what was found. Keeping coverage separate shows how much of WCAG the score is based on.

Why is my bar never full?

It fills completely only when every one of the 55 criteria has a manual result on record. Automated checks alone never fill it.

More in “See the whole site”

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.