Perceivable · Level A · Introduced in WCAG 2.0
WCAG 1.3.1: Info and Relationships
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
Structure and relationships conveyed visually must also be available programmatically or in text. Headings, labels, lists and table headers should describe the relationships a reader sees.
A practical example
A pricing table uses bold cells as column names but ordinary data cells in the markup. Replace those cells with headers and connect more complex header relationships so each price can be understood with its plan and billing period.
How to check it
- Identify visual headings, grouped controls, lists, tables and emphasized relationships.
- Inspect the markup and accessibility tree for the corresponding semantics and associations.
- Navigate by headings and read selected form controls and table cells with a screen reader, checking the announced context.
What can be missed
Making text bold does not create a heading. Conversely, adding ARIA to every container can make the structure harder to use. Prefer the native element that expresses the actual relationship.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.