Skip to content

Scores & severities ​

Severities ​

Every issue Lumtera finds has one of three severities:

SeverityMeaningAffects the score?
ErrorLumtera is confident this is a barrier.Yes, strongly
Needs reviewA machine can't decide this on its own, such as whether alt text is accurate or a video has captions. A person should confirm or dismiss it.A little
TipA best practice, including the four WCAG AAA checks.No

Lumtera is built not to cry wolf. When it can't be sure, it says Needs review, not Error. Each check has a default severity, listed in All checks. You can change it, or switch the check off, in Settings.

How the score is worked out ​

Each post, page or product gets a score from 1 to 100:

score = 100 × 0.85^errors × 0.96^items to review

Rounded, and never lower than 1. Tips don't count, and neither do dismissed items or findings ignored everywhere with Lumtera Pro. Results of guided manual checks don't change the score either.

FoundScore
Nothing100
1 item to review96
1 error85
2 errors72
5 errors44

The score is colored good from 90, warning from 60 to 89, and critical below 60.

Because the penalty multiplies, the score never reaches zero. A page with 20 errors still scores lower than one with 10, and fixing any error always raises the score.

A score of 100 isn't "compliant"

100 means "no automated issues found". Automated checks find only part of what WCAG covers. See What automated testing can't do.

Site-wide numbers ​

On the Overview:

  • Average automated score is the average of the stored scores of every checked item. Published posts count, and so do drafts, pending, private and scheduled ones. Only the content types you chose in Settings are included.
  • Errors is the total number of errors. "On N items" is how many items have at least one.
  • Needs review is the total number of items to review.
  • Coverage is how many items have been checked, out of all items of those types. Trash and auto-drafts aren't counted.

When scores update ​

A post's stored score updates whenever it's checked:

  • when it's saved (if Check content on save is on, which is the default)
  • when you run Check all content from the Overview, or Check or Check again on an item in the Content report
  • when an issue on it is dismissed or restored
  • when the Alt text manager adds alt text to it (this saves the post, so it's re-checked if Check content on save is on)
  • when you run wp lumtera scan

Changing settings doesn't re-check anything. After you change a check's severity or switch a check off, run Check all content again from the Overview to update existing results.

Live checks in the editor sidebar are never stored. They update as you type, and the stored result updates when you save.