How to fix common accessibility problems
Plain-language fixes for the problems automated scans find most often, with before and after code and a note for your platform.
- ARIA attributes not allowed on the element
- ARIA attributes with invalid values
- Buttons without a name
- Click and tap targets are too small
- Content outside landmark regions
- Declared language does not match the content
- Dropdowns without a label
- Duplicate IDs referenced by ARIA or labels
- Elements with role="img" missing a text alternative
- Empty headings
- Form fields with invalid autocomplete values
- Form fields without a label
- Frames without a title
- Heading levels skipped
- Hidden content that can still be focused
- Image buttons missing alternative text
- Images missing alternative text
- Interactive controls nested inside other controls
- Keyboard focus is not visible
- Landmarks that cannot be told apart
- Links distinguished only by color
- Links with vague text
- Links without a name
- List items outside a list
- Lists with invalid structure
- Long PDF documents have no bookmarks
- Media plays automatically
- More than one H1 heading
- No main landmark
- No way to skip repeated navigation
- Page has no main heading (H1)
- Page has no title
- Page language code is invalid
- Page language not declared
- PDF documents are not tagged
- PDF documents contain only images of text
- PDF documents have no language set
- PDF documents have no usable title
- PDF security settings block assistive technology
- Pinch-zoom is disabled
- Required ARIA attributes missing
- SVG images missing a text alternative
- Text with low color contrast
Colour contrast checker · Alt text checklist
Automated testing detects only a portion of WCAG issues. Manual testing is required to assess full conformance.