Images
1 lessonColor
1 lessonForms
2 lessonsForm Fields Without Labels
Every form input must have a programmatic label — either a <label> element, aria-label, or aria-labelledby.
Inaccessible Button Patterns
Buttons must use the <button> element or role="button" with full keyboard support. Using <div> or <span> for buttons is a common accessibility failure.
Structure
2 lessonsBroken Heading Structure
Headings (h1–h6) must form a logical, nested hierarchy. Skipping levels and using headings for visual styling breaks navigation for screen reader users.
Missing or Wrong Language Attribute
The <html> element must have a lang attribute so screen readers use the correct language, pronunciation rules, and voice.
Navigation
2 lessonsUninformative Link Text
Link text must describe the destination or purpose of the link. "Click here" and "Read more" are meaningless when read out of context.
Missing Skip Navigation Links
Pages with repeated navigation must provide a way to skip directly to the main content, so keyboard users don't have to tab through the same nav links on every page.
Keyboard
2 lessonsElements Not Keyboard-Accessible
All interactive functionality must be operable with a keyboard alone. Users who can't use a mouse depend entirely on keyboard navigation.
Missing or Hidden Focus Indicators
Keyboard users must be able to see which element is focused. Removing the browser's default outline without a replacement is a common and serious barrier.
ARIA
1 lessonMultimedia
1 lessonSee these issues on your own site
ADAGuard automatically detects all 12 of these patterns and dozens more — in seconds.