Accessibility checks explained, with code fixes
The 53 most common automated accessibility failures, explained in plain language with the fix for HTML, React, Shopify and WordPress. Each page says who the problem hurts first, then how to fix it. Ordered from most to least severe.
- CriticalWCAG 1.1.1Image has no alt textBlind and low-vision people using screen readers or braille displays, and anyone whose images fail to load.
- CriticalWCAG 4.1.2Button has no accessible nameScreen reader users and voice control users, who need a name to say (“click Cart”).
- CriticalWCAG 1.3.1, 4.1.2Form field has no labelScreen reader users, voice control users, people with memory or attention difficulties, and anyone who forgets what a field was for.
- CriticalWCAG 1.4.4Zoom is disabledPeople with low vision who zoom to read, and anyone reading small print on a phone.
- CriticalWCAG 1.1.1, 4.1.2Image button has no alt textScreen reader and voice control users.
- CriticalWCAG 1.3.1, 4.1.2Dropdown has no labelScreen reader users and voice control users.
- CriticalWCAG 4.1.2ARIA role is missing a required attributeScreen reader users, who hear a control with no state (“checkbox” but not whether it is ticked).
- CriticalWCAG 1.2.2Video has no captionsDeaf and hard-of-hearing people, people in noisy places, and anyone watching with the sound off.
- CriticalWCAG 4.1.2ARIA attribute not allowed on this elementScreen reader users, who hear a state that doesn’t match the control, or miss the state altogether.
- CriticalWCAG 4.1.2ARIA attribute name is misspeltScreen reader users, who miss the label, description or state the attribute was meant to provide.
- CriticalWCAG 4.1.2ARIA attribute has an invalid valueScreen reader users, who hear the wrong state (or none) for menus, accordions and tabs.
- CriticalWCAG 4.1.2Element has an invalid ARIA roleScreen reader users and voice control users, who get no role, so a control isn’t announced as a button, dialog or menu.
- CriticalWCAG 1.3.1ARIA role is missing the children it needsScreen reader users, who can’t tell how many tabs or options there are, or which one is selected.
- CriticalWCAG 1.3.1ARIA role is outside the parent it needsScreen reader users, who hear a tab or option with no group, count or position.
- CriticalWCAG 4.1.2ID used by a label or ARIA is not uniqueScreen reader users and voice control users, who get the wrong label for a field or control.
- CriticalWCAG 2.2.1Page refreshes or redirects on a timerPeople who read slowly, screen reader users who lose their place on reload, and people with cognitive disabilities.
- CriticalWCAG 2.4.4, 4.1.2Image map area has no alt textScreen reader users and voice control users, who need a name to choose or say each link.
- SeriousWCAG 2.4.4, 4.1.2Link has no accessible nameScreen reader users, who often browse a list of links, and voice control users.
- SeriousWCAG 1.4.3Text has too little contrastPeople with low vision or colour-vision differences, older readers, and anyone on a phone in sunlight.
- SeriousWCAG 3.1.1Page has no language setScreen reader users, and people using translation or reading tools.
- SeriousWCAG 2.4.2Page has no titleScreen reader users (the title is the first thing they hear), people with many tabs open, and everyone in search results.
- SeriousWCAG 1.3.1List contains things that aren’t list itemsScreen reader users, who hear “list, 5 items” and use it to judge the length of menus and product grids.
- SeriousWCAG 1.3.1List item outside a listScreen reader users, who lose the count and grouping of items.
- SeriousWCAG 4.1.2Embedded frame has no titleScreen reader users moving between frames on a page.
- SeriousWCAG 4.1.2Hidden content can still be focusedScreen reader users, who land on a silent, invisible stop, and keyboard users.
- SeriousWCAG 1.4.1Links are only shown by colourPeople with colour-vision differences and low vision.
- SeriousWCAG 1.1.1Image made with SVG has no text alternativeScreen reader users.
- SeriousWCAG 2.5.8Touch target is too smallPeople with tremors or limited dexterity, and everyone using a phone one-handed.
- SeriousBest practicePositive tabindex changes the tab orderKeyboard users and screen reader users.
- SeriousWCAG 1.3.5Form field has an invalid autocomplete valuePeople with memory, motor or cognitive disabilities, who rely on autofill, and everyone on a phone.
- SeriousWCAG 4.1.2aria-label used where it isn’t allowedScreen reader users, who hear the raw content (“★★★★½”, “−20%”) instead of the label you wrote.
- SeriousWCAG 4.1.2Custom button or menu item has no nameScreen reader users, and voice control users who need a name to say.
- SeriousWCAG 4.1.2Custom input has no accessible nameScreen reader users, and voice control users who need a name to move to the field.
- SeriousWCAG 4.1.2Custom checkbox or switch has no nameScreen reader users, and voice control users who need a name to tick or untick it.
- SeriousBest practiceDialog has no accessible nameScreen reader users, who hear the dialog open but not what it is about.
- SeriousWCAG 2.4.1No way to skip repeated contentKeyboard users, switch users and screen reader users, who would otherwise go through every menu link on every page.
- SeriousWCAG 1.1.1Embedded object has no text alternativeScreen reader users, and anyone whose browser can’t show the embedded file, such as many phone browsers with PDFs.
- SeriousWCAG 1.1.1Element with role="img" has no text alternativeBlind and low-vision people using screen readers or braille displays.
- SeriousWCAG 2.1.1Scrolling area can’t be reached by keyboardKeyboard users, including people who can’t use a mouse or trackpad.
- SeriousWCAG 4.1.2Control is nested inside another controlScreen reader users, who never hear the inner control, and keyboard users, who get confusing focus.
- SeriousWCAG 3.1.1Page language code is not validScreen reader users, especially people who read in more than one language, and anyone using browser translation.
- SeriousWCAG 3.1.2Language code on part of the page is not validScreen reader users, who hear foreign words read in the wrong accent, often unrecognisably.
- SeriousWCAG 1.3.1Table header has no data cellsScreen reader users, who rely on headers being read out as they move between cells.
- SeriousWCAG 1.3.1Table cell points to headers that don’t existScreen reader users, who hear the wrong context for numbers and prices in complex tables.
- ModerateBest practiceHeading levels skipScreen reader users, who navigate by headings to skim a page, much as sighted people scan bold text.
- ModerateBest practicePage has no main landmarkScreen reader users and keyboard users who use “skip to content”.
- ModerateBest practicePage has no level-one headingScreen reader users, who often press “1” to jump straight to the main heading.
- ModerateBest practiceContent is outside every landmarkScreen reader users, who jump between landmarks to find their way around a page.
- ModerateBest practiceLandmarks can’t be told apartScreen reader users, who pick from a list of landmarks to move around the page.
- ModerateWCAG 3.3.2Form field has more than one labelScreen reader users and voice control users, who may hear or need a different name from the one you expect.
- MinorBest practiceRole not allowed on this elementScreen reader users, who lose the original meaning (a heading stops being a heading), and keyboard users if the new role promises behaviour that isn’t there.
- MinorBest practiceHeading is emptyScreen reader users, who navigate by headings to skim a page.
- MinorBest practiceAlt text repeats the text beside itScreen reader users, who hear every product name twice on collection pages and search results.
Rule ids match axe-core and Lighthouse, so you can look up any id from those tools here. Automated checks find a large share of issues, not all; some WCAG criteria need a person to judge. To see which of these a page fails, run the free scan.