Insights:Accessibility and Usability Troubleshooting: From Symptoms to Root Causes
Four Root Causes
| Root Cause | Typical Symptoms | Troubleshooting Entry |
|---|---|---|
| Structure | Disordered reading order, skipping readings | Heading hierarchy and tags |
| Visual | Poor visibility, insufficient contrast | Color picker and zoom |
| Interaction | Keyboard cannot reach, buttons unclickable | Tab walkthrough and sizing |
| Content | Unclear what to fill, incomprehensible error messages | Labels and prompt copy |
Structure Checks
- Is the tag order consistent with visual order?
- Do headings progress sequentially without skipping levels?
- Are lists and tables using proper structural elements?
- Do images have descriptive text or are they clearly marked as decorative?
Visual Checks
- Is there sufficient contrast between body text and background?
- Does the design rely solely on color to convey information?
- Does content remain readable when zoomed to 200%?
- Do small font sizes maintain adequate line spacing?
Interaction Checks
- Can Tab key reach all interactive elements?
- Is focus indicator visible?
- Are mobile touch targets appropriately sized and spaced?
- Do modals trap keyboard focus? Can they be closed?
Content Checks
- Does each input field have persistent labels?
- Do error messages clearly explain where the mistake occurred and how to fix it?
- Are link texts understandable out of context?
Recommended Check Sequence
- Start with interaction (most impacts usability).
- Then address content (affects form completion capability).
Situations Prone to Misjudgment
- Automated tools report errors but they're false positives: requires manual review.
- Only reproducible in one browser: first verify how focus styles are implemented.
- Keyboard accessible but screen reader reads garbled output: usually a structure issue, not an interaction issue.
Boundaries
Cause categorization is a scoping tool, not a final diagnosis. For complex components, it's faster to reproduce directly in a real browser than to cross-reference a checklist.
Related reading: