Whether people using a screen reader, a keyboard or with poor eyesight can use the page: names for links and buttons, labels, contrast and focus.
SmooxSEO runs 13 accessibility checks on every page of your site:
A page can't be found, indexed or trusted, or search engines can't read part of the site. Fix it soon: it costs traffic.
Icon-only buttons with no label: screen reader users hear "button" and can't tell what it does.
Fields without a label are read as "edit text", so people can't know what to type.
Pressing Tab gets stuck, or you can't see which element is selected, so the site can't be used without a mouse.
Screen readers announce these links as just "link", with no idea where they go (often icon or image links).
The page still ranks, but less well, or a real opportunity is lost. Fix it when you can.
Elements hidden with aria-hidden still receive keyboard focus, so Tab lands on something invisible and silent.
Text colour too close to its background (below WCAG AA 4.5:1, or 3:1 for large text) is hard to read, especially on phones outside.
Without a valid <html lang>, screen readers use the wrong voice and pronunciation, and translators guess.
Data tables with no <th> are read as a stream of cells with no column names.
Good practice with a small effect, or something that is often intentional. Nice to have.
The page reloads itself after a delay, which loses people's place and interrupts screen readers.
Two elements share an ID that a label or ARIA attribute points to, so the label can attach to the wrong field.
Embedded frames (videos, maps, forms) without a title are announced as "frame" with no name.
Wrong ARIA tells assistive technology something false, which is worse than no ARIA.
Positive tabindex changes the natural keyboard order and usually makes it confusing.