Every check we run

An ARIA attribute is not allowed on this role, so it is ignored or misreported.

The page body is hidden from assistive technology, so screen reader users get an empty page.

This role needs attributes that are missing, so its state is not announced.

This role must contain particular child roles, and they are missing.

This role must sit inside a particular parent role, and it does not.

An element uses a role that is not valid, so assistive technology falls back to whatever the element was originally.

An aria- attribute is misspelled, so it does nothing.

An ARIA attribute has a value it does not accept, or points at an element that does not exist.

An element is marked as presentational but is still focusable or has a global ARIA attribute, so the roles conflict.

The audio has no transcript or captions.

Audio plays automatically, which covers a screen reader's own speech and leaves the user unable to hear it.

The video has no captions, so anyone who is deaf or hard of hearing gets no access to the audio.

The text does not stand out enough from its background. People with low vision, and anyone in bright light, will struggle to read it.

The text sits on a gradient and drops below the required contrast at the pale end.

The text sits on a background image, so contrast changes with the image and cannot be measured automatically.

Links are separated from text by colour alone.

A custom input built from ARIA has no accessible name.

A custom checkbox, radio, or switch has no accessible name.

This button has no text, so a screen reader announces "button" with no indication of what it does.

The field has more than one label. Different screen readers announce different ones, so users get inconsistent instructions.

This button has no name, so it is announced only as "button".

This field has no label, so a screen reader announces it as an unnamed edit box. The user has to guess what to type.

This dropdown has no accessible name, so its purpose is not announced.

An overlay widget is installed. Overlays are marketed as a fix, but they cannot repair the underlying HTML, and they do not remove legal exposure.

The page refreshes or redirects on a timer, which can move people away mid-task.

Zoom is disabled, so anyone who needs to enlarge the text cannot.

An image map region has no name, so its link is announced with no destination.

A screen reader announces this image by its file name, or skips it. Someone who cannot see the image gets nothing from it.

This image is a button. Without a name, a screen reader announces it as "button" with no indication of what it does.

Embedded content has no text alternative, so anyone who cannot see it gets nothing.

An element marked as an image has no accessible name.

An element is hidden from screen readers but can still be reached by keyboard, so focus disappears into content that is not announced.

This element responds to a mouse click but cannot be reached with a keyboard, so keyboard and screen reader users cannot use it at all.

One control is nested inside another. Screen readers announce this inconsistently and the inner control is often unreachable.

No focus styling was found. A keyboard user cannot see where they are on the page.

There is no way to skip repeated navigation, so keyboard users tab through it on every page.

A positive tabindex pulls this element out of the natural reading order, so the tab sequence no longer matches what is on screen.

A scrollable area cannot be reached or scrolled by keyboard.

The page does not say what language it is in, so a screen reader may read it with the wrong pronunciation rules.

The language code is not valid, so it is ignored.

The lang and xml:lang attributes disagree, so the language announced depends on the tool.

A lang attribute inside the page uses an invalid code.

A keyboard user has to tab through the whole navigation on every page before reaching the content.

This link is distinguished from surrounding text by colour alone. Anyone who cannot separate those colours cannot tell it is a link.

This link has no text. Screen reader users often navigate by pulling up a list of links; this one appears blank in that list.

The skip link's target does not exist, so activating it does nothing.

A definition list has content that breaks its structure, so term and definition pairings are announced incorrectly.

A definition term or description sits outside a definition list.

The page has no title. Browser tabs, bookmarks, and screen reader page lists all show nothing useful.

Two elements share an id that ARIA references, so the reference resolves to the wrong element.

An iframe has no name, so it is announced only as "frame" when a user moves into it.

Heading levels skip a step. Screen reader users navigate by heading level, so a gap makes the page structure read as though content is missing.

The page has no main landmark, so screen reader users cannot jump straight to the content.

A list contains elements that are not list items, so the count announced to screen reader users is wrong.

A list item is not inside a list, so it is not announced as part of one.

The page has no top-level heading, so there is no clear starting point when navigating by headings.

Some content sits outside any landmark, so it is missed when navigating by region.

The table's caption and summary say the same thing, which is announced twice.

A table cell points at headers that do not exist, so the relationship announced is wrong.

A table header describes no cells, which usually means the table is used for layout.