Marcelo Paiva

1.3.1 Info and Relationships, as slides

A man wearing headphones, glasses, and a hooded sweatshirt holds a spoon over a bowl of soup near a window.

Success criterion 1.3.1 · Level A

Info and Relationships

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

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

A success criterion, as slides

This is a slide show on a projector. One slide fills the screen, and the site’s header and footer are out of the way.

From top to bottom

  1. The slide: there are five, for the cover, the quote, the criterion, the tasks for each role, and a thank-you.
  2. Under the slide: Exit slides, Previous, which slide you are on, Next, and Full screen.
  3. A line on the keys. The left and right arrows change slide, and Home and End go to the first and last.

What you can do here

Present the criterion to a room, a slide at a time.