🟢 Level A

WCAG 1.3.1: Info and Relationships

Success Criterion 1.3.1 — Level A

Quick Answer

Structure conveyed visually must also be conveyed programmatically (via HTML or ARIA).

Why It Matters

Screen readers rely on semantic HTML to understand page structure. Visual-only structure is invisible to them.

How to Audit

Run an automated accessibility scan to detect common Info and Relationships failures. Then manually verify with: keyboard-only navigation, a screen reader (VoiceOver on Mac, NVDA on Windows), and browser developer tools. Automated tools catch approximately 40% of Info and Relationships issues — manual testing is essential.

How to Fix

Use proper heading hierarchy (h1-h6), lists (<ul>/<ol>), and ARIA roles. Never use tables for layout.

Frequently Asked Questions

What is WCAG 1.3.1 Info and Relationships?

Structure conveyed visually must also be conveyed programmatically (via HTML or ARIA).

Is WCAG 1.3.1 required for ADA compliance?

WCAG 2.1 Level A is the minimum baseline for ADA website compliance. Courts have upheld WCAG 2.1 AA as the standard for ADA Title III lawsuits.

How do I fix WCAG 1.3.1 violations?

Use proper heading hierarchy (h1-h6), lists (<ul>/<ol>), and ARIA roles. Never use tables for layout.

Disclaimer: This guide is for informational purposes only and does not constitute legal advice. Consult a qualified ADA/accessibility attorney for your specific compliance situation.

Scan Your Site for WCAG 1.3.1 Issues

Get a free automated accessibility report including all WCAG 2.1 AA violations.

Run Free Accessibility Scan