Practical Guides

The 10 Most Common Accessibility Errors (and How to Avoid Them)

Accessibility Team
2 min read
Share:

Reading time: 8 minutes

As a developer, you know this: Accessibility sounds complex and overwhelming. But the truth is: 80% of problems arise from 10 recurring mistakes. Let’s go through them together – with practical examples and immediate solutions.

1. Missing Alt Text for Images

The Problem:

<!-- ❌ Bad -->
<img src="team-meeting.jpg">

<!-- ❌ Also bad -->
<img src="team-meeting.jpg" alt="IMG_1234">

The Solution:

<!-- ✅ Good -->
<img src="team-meeting.jpg" alt="Team discusses project planning at whiteboard">

<!-- ✅ For decorative images -->
<img src="decorative-line.png" alt="" role="presentation">

2. Insufficient Color Contrast

The Problem: Light gray text on white background is hard to read.

The Solution:

  • Normal text: minimum contrast ratio 4.5:1
  • Large text (18pt+): minimum 3:1
  • Use tools like our Contrast Checker

3. Missing Form Labels

The Problem:

<!-- ❌ Bad -->
<input type="email" placeholder="Email">

The Solution:

<!-- ✅ Good -->
<label for="email">Email Address</label>
<input type="email" id="email" name="email">

4. No Keyboard Navigation

The Problem: Custom UI components can’t be operated with the keyboard.

The Solution:

  • Use semantic HTML elements (<button>, <a>, <input>)
  • Add tabindex=”0″ for custom elements
  • Implement keyboard event handlers

5. Missing Skip Links

The Problem: Screen reader users must navigate through the entire menu on every page.

The Solution:

<a href="#main-content" class="skip-link">
  Skip to main content
</a>

6. Auto-Playing Media

The Problem: Videos or audio that play automatically can be disturbing and disorienting.

The Solution:

  • Never autoplay media with sound
  • Provide clear play/pause controls
  • Add volume controls

7. Missing Page Titles

The Problem: Generic or missing page titles make navigation difficult.

The Solution:

<!-- ✅ Good -->
<title>Contact Us | Company Name</title>

8. Inaccessible Error Messages

The Problem: Error messages shown only through color or position.

The Solution:

  • Use aria-describedby to link errors to inputs
  • Include icon + text, not just color
  • Use aria-live for dynamic messages

9. Missing Language Declaration

The Problem: Screen readers don’t know what language to use.

The Solution:

<html lang="en">

10. Touch Targets Too Small

The Problem: Buttons and links that are too small to tap accurately.

The Solution:

  • Minimum size: 44×44 pixels
  • Adequate spacing between targets

Conclusion

These 10 errors account for the majority of accessibility problems. Fix them, and you’re already 80% of the way there!

Test Your Website's Accessibility

Use our free accessibility checker to identify and fix issues on your website.

Start Free Scan

Related Articles

© 2025 Accessibility Checker. Built for WCAG compliance.