element-html-removed
This fails the run. Where it is wrong about your code, // ramonda-check-ignore <reason> on the line says so, and the reason is printed on every run.
Reported when a tag HTML has removed is written, so nothing defines what it means.
These still parse and most still paint something, which is why they survive: nothing breaks, so nothing draws attention to them. What they no longer have is a specification saying what they MEAN — so the accessibility tree has nothing to map them to, and a future browser owes them nothing.
<marquee> and <blink> are worse than obsolete. Moving content that cannot be paused is a
failure of WCAG 2.2.2 on its own: a reader who needs time on a line cannot get it, and for
some people motion is a vestibular trigger. If something must move, it belongs in CSS, where
it can be stopped and where prefers-reduced-motion is honoured:
@media (prefers-reduced-motion: reduce) {
.ticker { animation: none; }
}
A name nobody has ever heard of is a different report. This one is for names that WERE right, so each has a replacement rather than a correction.
Next
- All rules — the other checks this one runs beside.
- Checking your app — how to run it, and what it proves.