Keyboard Navigation Broken on Website
Keyboard navigation broken? Learn why users can't tab through your site, which WCAG criteria you're failing, and step-by-step fixes for broken keyboard access.
Images Missing Alt Text — How to Fix
Images missing alt text fail WCAG 1.1.1 and block screen reader users. Learn how to write proper alt text, handle decorative images, and audit your site in minutes.
Missing Form Labels — Screen Reader Issue
Form inputs without labels fail WCAG 1.3.1 and 4.1.2. Screen reader users cannot identify form fields. Learn how to add proper labels and test your forms for accessibility.
Screen Reader Not Reading Website Content
Screen reader skipping or misreading content? Learn the common WCAG failures that break screen reader compatibility and how to fix them systematically.
Modal and Dialog Keyboard Trap Problems
Modal dialogs that trap keyboard focus or let it escape break WCAG 2.1.2. Learn how to implement proper focus management for accessible modal dialogs and overlays.
Video Missing Captions — WCAG Failure
Videos without captions fail WCAG 1.2.2 (prerecorded) and 1.2.4 (live). Deaf and hard-of-hearing users cannot access audio content. Learn how to add captions that meet WCAG requirements.
Low Color Contrast — WCAG AA Failure
Color contrast failing WCAG 1.4.3? Learn the exact contrast ratios required, how to measure them, and how to fix low contrast text without redesigning your site.
Keyboard Focus Indicator Not Visible
Invisible focus indicators fail WCAG 2.4.7 and 2.4.11. Keyboard users cannot see where they are on the page. Learn how to add visible focus styles that meet WCAG requirements.
WAVE Tool Showing Errors on Your Site
WAVE accessibility checker flagging errors and alerts on your website? Learn what each WAVE error means, which to fix first, and how to resolve the most common violations.
Lighthouse Accessibility Score Low
Lighthouse accessibility score below 90? Learn what the score measures, which violations to fix first, and how to systematically improve your score to 95+.
axe DevTools Violations on Your Site
axe DevTools flagging violations on your website? Learn how to interpret axe results, prioritize fixes by impact, and resolve the most common WCAG violations axe detects.
Missing ARIA Landmarks and Semantic HTML
Missing landmark regions prevent screen reader users from navigating your page efficiently. Learn how to add ARIA landmarks and semantic HTML to meet WCAG 1.3.6 and 2.4.1.
"Click Here" and Unclear Link Text
Vague link text like "click here" or "read more" fails WCAG 2.4.4. Screen reader users cannot understand where links go. Learn how to write descriptive link text that passes WCAG.
Broken Heading Hierarchy (Skipping Levels)
Skipping heading levels (H1 to H3, H2 to H5) breaks WCAG 1.3.1 and disorients screen reader users. Learn how to fix heading structure and audit your page hierarchy.
HTML lang Attribute Missing
Missing lang attribute on <html> fails WCAG 3.1.1 and causes screen readers to use the wrong language/accent. Learn how to declare language and handle multi-language content.
How to use these guides
Each guide covers one specific accessibility problem — the kind of issue you would discover through an automated audit tool like Lighthouse, axe DevTools, or WAVE.
We describe the exact WCAG criteria that applies, show you what symptoms look like in practice, explain the common causes, and walk through a code-level fix with before/after examples.
Start with Critical issues — they completely block users with disabilities from accessing content and carry the highest lawsuit risk. Then work through Serious, Moderate, and Minor violations.
Automated tools catch roughly 30–40% of all WCAG violations. For comprehensive coverage, combine automated scanning with manual keyboard testing and screen reader testing, or request a professional audit.