Success criterion 1.3.1
Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
- Level A
- Principle 1: Perceivable
- Guideline 1.3: Adaptable
In a user’s words
“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.”
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!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 1.3.1 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.