- Level
- A
- Since
- WCAG 2.0
- Entries
- 182 / 193
1.3.1 Info and Relationships
Structure that is visible on screen (headings, lists, tables, labels) has to exist in the markup, not only in the styling.
/ What it requires
What a sighted visitor understands from layout has to be available to software too. Bold large text reads as a heading, an indented column reads as a list, a grid reads as a table, and a word beside a box reads as its label. Unless the markup says the same thing, a screen reader announces a flat stream of text, and its user cannot jump between headings, hear which column a cell belongs to, or learn what a form field is asking for.
The criterion is met when each such relationship can be determined from the code or is stated in text. A required field marked with the word required passes; one marked only with a red border does not. WCAG does not prescribe one h1 per page or forbid a skipped heading level, and it names no exceptions here. The failure is the mismatch: structure that exists for the eye and not in the markup, or markup that claims a structure the content does not have.
/ How pages fail it
- Headings are paragraphs or div elements styled large and bold, so the page has no outline to navigate.
- A form field has no label element or accessible name, or relies on a placeholder that vanishes on typing.
- A data table has no th cells, so each value is announced without its column or row.
- A list is built from line breaks and dashes, or a ul contains children that are not li elements.
- A group of radio buttons or checkboxes has no fieldset and legend, so each option is announced without the question.
/ How to check it yourself
- List the headings in a screen reader (NVDA: Insert+F7) or with a browser extension that shows the page outline. Compare the list with what looks like a heading on screen.
- Click the visible label of each form field. If the cursor does not land in the field, the label is not associated with it.
- Inspect each data table for th elements and the scope attribute, and each visual list for ul, ol and li.
- Turn styles off (Firefox: View, Page Style, No Style) and check that headings, lists and tables are still recognisable.
- With a screen reader, jump from landmark to landmark and confirm that the main content, the navigation and the footer can each be reached.
/ How to fix it
- Mark headings with h1 to h6 in an order that follows the content, and do not use heading elements only to make text bigger.
- Give every input, select and textarea a label element tied to it with for and id, and wrap related options in a fieldset with a legend.
- Write header cells as th with scope="col" or scope="row", and add a caption that names the table.
- Build lists with ul, ol and li, with li as the only direct children.
- Wrap the regions of the page in main, nav, header and footer, and connect each tab to its panel with aria-controls.
/ What our scanner checks
The static pass flags a missing or repeated h1, jumps in heading level, a missing main element and tables without th. The rendered pass adds content outside every landmark, lists with stray children, fields with no label or only a placeholder, option groups without a legend and tabs not linked to a panel. HTML_CodeSniffer adds empty headings. Text that only looks like a heading is invisible to all of them.
/ Who fails it, in our own measurements
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Is skipping a heading level a WCAG failure?
Not by itself. 1.3.1 asks that the heading structure in the markup reflects the structure of the content; it does not say that h2 must be followed by h3. It is still worth fixing, because screen reader users skim a page by its outline and a gap reads like a missing section. That is why our scanner reports it as a moderate finding.
Can a page have more than one h1?
WCAG does not forbid it. It is enough that headings are marked up as headings and their levels match how the content is organised. One h1 naming the page is the convention most screen reader users expect, so several make the outline harder to read. Our scanner lists more than one h1 as a moderate finding under 1.3.1: a sign of weak structure, not proof of a failure.
Is a placeholder enough to label a form field?
No. A placeholder disappears as soon as somebody types, is often too pale to read, and is not treated as a label by every assistive technology. Use a visible label element connected to the field with for and id. Where a visible label is not possible, such as a single search box with a button, aria-label gives the field a name.
Is WCAG 1.3.1 level A or AA?
Level A, the lowest level, so every claim of AA conformance includes it. It has been part of WCAG since version 2.0 and is in 2.1 and 2.2 under the same number.
Does WCAG 1.3.1 apply under the European Accessibility Act?
Yes, through EN 301 549, the standard used to show conformity with the EAA's requirements for websites and apps. Clause 9.1.3.1 requires a web page to satisfy WCAG 2.1 success criterion 1.3.1, clause 10.1.3.1 applies it to documents such as PDFs, and clause 11.1.3.1 to software.
