Press the button. The findings stay on the page.
This is LiveAudit inspecting the page you are reading — not a recording of it. The fragment below carries defects on purpose; the rest of the page is this site, unchanged and included in the scan.
Nothing runs until you say so, and nothing is repaired afterwards. The inspector reads the DOM and draws its own layer beside it; the fragment keeps every attribute it has now, including the broken ones.
The page under inspection
A fragment with known defects, rendered on its own white surface so the contrast cases hold in both themes.
JavaScript is off, so the inspector cannot run. Everything else on this page works without it.
Reservations
The same id, a second time.
Which of the two describes this?
An element with an invented role.
A heading that skips a level
| Monday | 9:00 |
| Tuesday | 11:00 |
Grey on white, 2.85:1 — this has to be caught.
White on a gradient — not decidable, so UNTESTED.
What the four states mean here
FAIL was proven — the image has no alt text, the id exists twice.REVIEW is a suspicion a person has to settle: "here" may well be a fine link name in its sentence. UNTESTED is the one that separates this from a score: text on a gradient has no single background colour to measure, so the rule says so instead of guessing white and passing it.
Turn the contrast pass off and the two contrast rules do not run — the sidebar lists them under “Rules that did not run”, with the reason, rather than staying silent.
It inspects. It does not repair.
No attribute, style or node inside the fragment changes while the layer is up: the inspector keeps its own host element as the last child of <body>, fixed and click-through, and every marker is positioned from measurements it read. Hide it and nothing of it remains. That is the whole difference to an accessibility overlay, which edits the page and leaves the defects in the source.