WCAG 2.0 · Level A · Perceivable
WCAG 1.3.1 — Info and Relationships
Structure conveyed visually — headings, lists, tables, form labels — must also be present in the markup so assistive tech can perceive it.
WCAG 1.3.1 at a glance
Level A · Principle: Perceivable · Added in WCAG 2.0. Level A is the minimum — failing it blocks some users entirely.
What it means
Structure conveyed visually — headings, lists, tables, form labels — must also be present in the markup so assistive tech can perceive it.
Who it helps
Screen-reader users who navigate by structure.
Common failures
- Headings styled with bold text instead of <h> tags
- Layout built so reading order or relationships are visual-only
- Form fields not programmatically associated with labels
- Data tables without proper headers
How to meet WCAG 1.3.1
- Use real semantic elements (headings, lists, <th>, <label>)
- Associate labels with inputs via for/id
- Use ARIA only where native semantics fall short
How to test it
Partly automatable (e.g. missing labels, heading order); reading order and relationships need manual review.