1.3.2 Meaningful Sequence (Level A) — WCAG 2.1
WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence (Level A): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Perceivable → 1.3.2 Meaningful Sequence
1.3.2 Meaningful Sequence (Level A)
What it requires: When the order content is presented in affects its meaning, that order has to be correct in the underlying code, not just visually — because a screen reader reads DOM order, and CSS can visually reposition content away from its source order.
Common failure: A two-column product page uses CSS to visually place the price above the description, but the underlying HTML has the price defined after unrelated sidebar content — a screen-reader user hears things in a confusing, disconnected order.
Fix it: Keep the DOM order matching the logical reading order. If CSS (flexbox/grid order, absolute positioning) is used to achieve a different visual layout, verify the reading order still makes sense with CSS disabled or via a screen reader.
In 1.3 Adaptable: ← 1.3.1 Info and Relationships · 1.3.3 Sensory Characteristics →
↑ Back to Perceivable overview
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.