Rules · list
Failure reference
Broken list markup.
Screen readers announce "list, 12 items" — unless divs interrupt the structure and the count, and the shortcuts, disappear.
What fails — and who it fails
The failure, in plain language.
ul/ol containing non-li children (wrapper divs from frameworks), or li outside a list. Structure users rely on for orientation quietly breaks.
Detection — what the machine can and cannot judge
How the scanner finds it.
- List elements are checked for valid parent-child structure in the rendered DOM.
The legal reading — factual, not fearful
Where this sits in enforcement.
A low-drama Level A structure criterion — rarely the headline in a letter, routinely present in the annex. Clears in bulk with one template correction.
The fix — by pattern
The pattern that clears it.
- <ul><div class="row"><li>…</li></div></ul>
+ <ul><li class="row">…</li></ul>Fix the template, not the page — one change typically clears every instance at once. The triage engine groups findings by template pattern for exactly that reason.
Verification — resolution is evidence, not a checkbox
Fixed means a scan said so.
On monitored domains, mark the finding fixed and the next scan verifies it: zero remaining instances converts the finding to Resolved, and both the claim and the confirmation land in the append-only ledger. Criteria that need human judgement close through sign-off in the coverage matrix — covered by the right method, never by assumption.
See where your templates stand.
A complimentary assessment renders up to 25 public pages in an EU-hosted browser and shows every instance of this failure — grouped, ranked, and honest about what still needs a human.