Info and Relationships
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
In plain language
Headings, lists, tables, and form labels must be marked up properly in the code, so assistive technology can understand the page's structure. Making them look right visually isn't enough.
Why it matters
Screen reader users don't see visual structure like bold text or indentation. They rely on the underlying code to know what's a heading, what's a list, or which label belongs to which field. If the structure only exists visually, they lose that information.
In practice
Fails this criterion
A form marks required fields only with red text, with no indication in the code. A screen reader user has no way to know which fields are required.
Meets this criterion
The required fields have red text and an asterisk, and each label is properly linked to its input in the code, so the screen reader announces "required."
Test it yourself
Read through the page's content from top to bottom, ignoring how it looks. Do the headings, lists, and paragraphs still make sense in the order they appear? Can you still tell which label belongs to which field, or that a field is required, without relying on color or layout?