Info and Relationships: Structure in the Code
Also called: Semantic HTML, Programmatic structure, Content structure
Definition
Info and Relationships is WCAG success criterion 1.3.1: information, structure and relationships conveyed through presentation can be programmatically determined or are available in text.
Info and Relationships is the WCAG rule that the structure people see on a page must also be in the code. A bold line that looks like a heading, dots that look like a list, a grid that looks like a table – if they are only styled that way, a screen reader announces plain text and the structure is lost. Semantic HTML keeps it available, whatever way the content is presented.
What it means
WCAG 1.3.1 Info and Relationships is a Level A criterion in WCAG 2.2. Information, structure and relationships conveyed through presentation must be programmatically determinable or available in text. W3C names the typical structures:
| Shown visually as … | Needs in the code |
|---|---|
| Large or bold heading text | <h1>–<h6>, see heading structure |
| Bullets or numbers with indentation | <ul>, <ol>, <dl> |
| Rows and columns with headers | <table>, <th> with scope or headers |
| Text next to a form field | <label>, groups in <fieldset> with <legend> |
| Page regions (header, menu, main content) | Landmarks, see ARIA landmarks |
| Emphasized words | <strong>, <em> or a text cue |
| Required fields marked in red | A text or programmatic cue such as "Required" |
The goal: when the presentation changes – a screen reader reads the page aloud, a braille display shows it, or someone applies their own style sheet – the meaning stays intact. Where a technology cannot express a relationship in code, a text description is acceptable. Information given by color alone is covered by use of color (1.4.1).
Who benefits: screen reader users can jump between headings, hear "list, 5 items" or which column a table cell belongs to. Deaf-blind people using braille get the same structure. People who change fonts, colors or spacing keep the logic of the page.
Examples
<!-- Fails: looks like a heading and a list, but is plain text -->
<p class="big-bold">Opening hours</p>
<p>• Monday–Friday: 9–18</p>
<p>• Saturday: 10–14</p>
<!-- Passes: the structure is in the markup -->
<h2>Opening hours</h2>
<ul>
<li>Monday–Friday: 9–18</li>
<li>Saturday: 10–14</li>
</ul>Both versions look the same. Only the second tells a screen reader that this is a heading followed by a list of two items. W3C lists the opposite problem as a failure too: using structural markup, such as a <blockquote> for indentation or <th> in a layout table, where it does not represent the content.
Use headings, lists and data tables for what they are, connect every field to its label, group radio buttons with fieldset and legend, mark page regions with landmarks, and write "Required" next to required fields.
Fake headings with bold text, build lists with typed bullet characters, lay out tables with spaces or <pre>, use role="presentation" on content that carries meaning, or mark required fields with color only.
How to check info and relationships
Questions
What does info and relationships mean in WCAG?
It is success criterion 1.3.1: structure and relationships that people see – headings, lists, tables, labels, groups – must also be expressed in the code or in text. Then screen readers and other tools can present the same structure.
Which errors fail 1.3.1 most often?
Fake headings made of bold text, form fields without connected labels, data tables without header cells, lists built from typed characters, and required fields marked only by color. Several of them appear in W3C's failures for 1.3.1, for example F2 (changes in text presentation used to convey information) and F91 (table headers not marked up correctly).
Is semantic HTML required for WCAG?
WCAG does not require a specific technology, but on websites semantic HTML is the most direct way to meet 1.3.1. W3C's sufficient techniques include h1–h6 for headings, ul, ol and dl for lists, table markup for data and label for form fields.
Does every page need landmarks to meet 1.3.1?
W3C lists ARIA landmarks as one sufficient technique for identifying page regions. Landmarks such as header, nav, main and footer are the usual way to make the visible layout of a page available in code.
How is 1.3.1 related to the European Accessibility Act?
1.3.1 is Level A, so it is part of every WCAG level referenced by EN 301 549 and the European Accessibility Act. Structure problems are among the first things to fix.
Related terms
Heading Structure: Build a Clear Page Outline
Heading structure is the outline a page forms through its h1 to h6 elements. Each heading marks the start of a section, and its level shows where that section sits in the hierarchy.
Read definition: Heading Structure: Build a Clear Page OutlineARIA Landmarks: Page Regions for Screen Readers
ARIA landmarks are roles such as banner, navigation, main and contentinfo that identify the large regions of a page. Screen readers list them and let users jump directly to each region.
Read definition: ARIA Landmarks: Page Regions for Screen ReadersForm Labels: Clear Labels and Instructions
Form labels are the visible texts that name what a form field expects, such as “Email address”. WCAG 3.3.2 requires labels or instructions wherever content asks for user input, including formats and required fields.
Read definition: Form Labels: Clear Labels and InstructionsUse of Color: Never Rely on Color Alone
Use of Color is WCAG success criterion 1.4.1. Color must not be the only visual means of conveying information, indicating an action, prompting a response or distinguishing a visual element.
Read definition: Use of Color: Never Rely on Color Alone