Insights:What Is Web Accessibility: A Visual Guide
Four-Layer Model
| Layer | Problem Solved | Key Practices |
|---|---|---|
| Perception | Can users see/hear the content? | Contrast, alt text, captions |
| Comprehension | Can users understand the content? | Clear headings, consistent terminology, error messages |
| Operation | Can users interact with elements? | Keyboard access, adequate tap targets, visible focus |
| Compatibility | Can assistive tools read the page? | Semantic markup, ARIA attributes, correct tab order |
If any layer is missing, the experience breaks.
Perception Layer: Contrast & Alt Text
- Body text contrast ratio of at least 4.5:1, large text 3:1.
- Images should have
altdescribing the content, not the filename. - Use empty
altfor purely decorative images to avoid screen reader duplication. - Do not rely solely on color to convey status (add icons or text alongside red/green).
Comprehension Layer: Structure & Language
- Use proper heading hierarchy (h1 → h2 → h3) without skipping levels.
- Associate form labels with their input fields.
- Error messages must clearly state what went wrong and how to fix it.
- Keep terminology consistent; do not mix synonyms.
Operation Layer: Keyboard & Focus
- All interactive elements must be reachable via Tab.
- Focus style must be clearly visible; never remove outline without providing an alternative.
- When a dialog opens, move focus into it; on close, return focus to the triggering element.
- Tap/click targets should be no smaller than 44×44 pixels.
Compatibility Layer: Semantics & ARIA
- Use semantic tags (header, nav, main, footer).
- Add ARIA roles and states to custom components.
- Avoid abusing
tabindexto mess up the order. - Respect "Reduce Motion" settings for animations.
Why It Matters for Search
- Semantic structure helps search engines understand pages.
- Fast loading and clear structure benefit both accessibility and SEO.
- Mobile usability directly affects experience metrics.
When accessibility is done well, search performance tends to be strong too.
Common Mistakes
- Adding
altbut writing "Image 1". - Designing only for mouse users; keyboard users can't interact.
- Using
divto simulate buttons that screen readers can't recognize. - Removing focus styles so keyboard users don't know where they are.
Where to Start
- Check contrast (scan with a tool).
- Add missing image
alttext. - Verify form labels.
- Navigate core flows using the keyboard only.
- Fix heading hierarchy.
Completing these five steps addresses most issues.
Boundaries
Accessibility improves "reachability and comprehensibility," not whether content has value. It's a baseline for experience, not a source of competitive advantage.
Related Reading: