Skip to content
A11ySignal
Level AWCAG 2.0WCAG 2.1WCAG 2.2EN 301 549 § 9.1.3.1

1.3.1
Info and Relationships

Structure you show with layout — headings, lists, tables, groups — has to exist in the markup too.

What the standard says

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Why it matters

Screen reader users navigate by heading and landmark. If your headings are styled `div`s, that navigation does not exist and the page becomes one long paragraph.

What a failure looks like

  • fails`<div class="h2">` instead of `<h2>`.
  • failsA layout table with no `<th>`, or a data table with no header cells.
  • failsRelated radio buttons not wrapped in a `<fieldset>` with a `<legend>`.
  • failsA visual list built from `<br>` tags.

How to fix it

  • doUse the element that means what you mean, then style it. Semantics first, CSS second.
  • doGive data tables `<th scope="col">` or `scope="row"`.
  • doGroup related form controls in `<fieldset>` and name the group in `<legend>`.
  • doAdd landmarks: `<main>`, `<nav>`, `<header>`, `<footer>`.

How A11ySignal checks it

12 automated checks run against this criterion on every scan.

What a tool cannot tell you

Automation catches missing table headers and empty headings. Whether your heading levels describe the actual outline still needs reading.

Also under 1.3 Adaptable