Marcelo Paiva

All criteriaPresent as slides

A man wearing headphones, glasses, and a hooded sweatshirt holds a spoon over a bowl of soup near a window.Meant to show: A blind man who uses a screen reader

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.”

Who this helps: Blindness, Low Vision

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!”

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.

A success criterion

This is one page of a phrase book. It takes one success criterion and tells it from the side of the person it helps.

From top to bottom

  1. At the top, the site header: my name, which goes home, then links to Writing, Work, Signal, Tools and Resume, then Settings, where you choose the drawings, light or dark, and movement.
  2. Links back to all the criteria, and to present this one as slides.
  3. A drawing, the criterion’s number and name, what it requires in one sentence, and its level.
  4. In a user’s words: a quote from the person who meets the barrier.
  5. What each role can do: one task each for the product manager, the designer, the developer and the tester.
  6. Once it is fixed: the same person again.
  7. Share this with your team: post to LinkedIn, download the slides as a PDF, or copy a link.
  8. Some criteria then have a t-shirt to order.
  9. Links to the previous and next criterion. The left and right arrow keys go there too.
  10. At the bottom, the footer: a note on how this site is built, links to Illustrations, Pens, Concepts and Accessibility, this Describe this page button, then GitHub, LinkedIn and email.

What you can do here

Learn what this criterion asks, and what your part of the fix is.

Also here

The quotes are written to illustrate the criterion. They are not from real people.