
Success criterion 1.3.1 · Level A
Info and Relationships

“Your page looks neatly organized. To my screen reader it's one long sentence: no headings, no lists, and a table that reads like soup.”
Success criterion 1.3.1 · Level A
Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
Principle 1: Perceivable · Guideline 1.3: Adaptable
What each role can do
- Product manager
- Require that visual structure, such as headings, lists, tables and form groups, is also present in the code.
- Designer
- Annotate designs with heading levels, list structure, table headers and field groupings.
- Developer
- Use semantic HTML and ARIA landmarks to help define the structure and purpose of elements.
- Tester
- Navigate by headings, lists and tables with a screen reader and confirm the structure matches what is shown.
Once it is fixed

“Headings, lists, proper tables! Now I can skim your page as fast as anyone. Thanks for the structure!”
Next criterion: 1.3.2 Meaningful Sequence