WCAG 1.3.1
Level A
Perceivable
1.3.1 Info and Relationships
Structure and relationships conveyed visually are also available programmatically (headings, lists, tables, labels).
What 1.3.1 Info and Relationships means
Assistive tech can announce headings, table rows/columns, and form labels correctly because the markup is semantic.
How to test
Inspect markup: real <h1>-<h6>, <ul>/<ol>, <table> with <th>, and <label> tied to inputs — not visual styling alone.
How to meet it
Use semantic HTML; associate labels with for/id; mark up data tables with headers and scope; avoid faking structure with CSS.
Need help meeting 1.3.1?
Our IAAP-certified team audits your website and apps against every WCAG 2.2 criterion and delivers code-level remediation.
Official reference: Understanding 1.3.1 Info and Relationships (W3C)
More Perceivable criteria
1.1.1 Non-text Content
1.2.1 Audio-only and Video-only (Prerecorded)
1.2.2 Captions (Prerecorded)
1.2.3 Audio Description or Media Alternative (Prerecorded)
1.2.4 Captions (Live)
1.2.5 Audio Description (Prerecorded)
1.3.2 Meaningful Sequence
1.3.3 Sensory Characteristics
1.3.4 Orientation
1.3.5 Identify Input Purpose
1.4.1 Use of Color
1.4.2 Audio Control
1.4.3 Contrast (Minimum)
1.4.4 Resize Text
1.4.5 Images of Text
1.4.10 Reflow
1.4.11 Non-text Contrast
1.4.12 Text Spacing
1.4.13 Content on Hover or Focus