Accessibility
Problems that stop people using assistive technology, and AI agents that rely on the same labels, from using the page.
- Buttons without an accessible name: One or more buttons lack a name, so screen readers, voice control and AI agents cannot tell what clicking them will do.
- Embedded frames without a title: One or more iframes on the page have no title, so screen reader users cannot tell what an embedded video, map or form contains.
- Form fields without a label: One or more form fields have no label, so screen reader users, voice control and AI agents cannot tell what to enter in them.
- Heading levels skipped: A heading on the page skips one or more levels, such as an H2 followed by an H4, which breaks the outline screen reader users navigate by.
- Links without an accessible name: One or more links have no name, so screen readers cannot say where they lead and AI agents cannot tell what following them will do.
- Page language code not valid: The page declares a language, but the value is not a valid language code, so screen readers cannot use it to choose the right voice.
- Page language not declared: The page does not declare its language, so screen readers may read it aloud with the wrong voice and pronunciation rules.
- Page refreshes or redirects on a timer: The page uses a timed meta refresh to reload itself or send visitors to another URL after a delay, often before they have finished reading.
- Positive tabindex changes the keyboard order: Elements on the page have a tabindex above zero, which makes keyboard focus jump in an order that no longer follows the page.
- Whole page hidden from screen readers: The page’s body or html element is marked aria-hidden, so screen readers and other assistive tools are given none of its content to read.
- Zoom blocked by the viewport tag: The page’s viewport tag stops visitors from zooming in on mobile, so people with low vision cannot enlarge the text to read it.
Last updated on