Level AWCAG 2.0

1.3.2 Meaningful Sequence

If the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

Last reviewed: September 9, 2026

Understanding 1.3.2

Sighted users can visually scan a page in any order and rely on layout to understand context, but screen readers and other assistive technology typically read content in DOM order. If the visual (CSS) layout order diverges from the underlying DOM order, assistive technology users, or users of custom style sheets, may hear or read content in an order that changes or destroys its meaning.

How to Meet It

Ensure the source order of your HTML matches the logical reading order of the content. Avoid relying purely on CSS positioning (e.g., position: absolute, or unconstrained flexbox/grid order) to visually reorder content in ways that reverse or scramble the underlying DOM sequence, especially for content read sequentially like forms, articles, or step-by-step instructions.

Code Examples

INCORRECT

/* HTML has Subtotal before Total in the DOM, but CSS visually reverses them */
.subtotal { order: 2; }
.total { order: 1; } /* Total appears first visually but reads last to AT, confusing meaning */

CORRECT

/* DOM order matches the intended reading and visual order */
.subtotal { order: 1; }
.total { order: 2; }

Frequently Asked Questions

Is using CSS order or Grid placement always a violation?

Not automatically. It's only a problem when the reordering changes the meaning of the content for someone reading it in DOM order (e.g., a screen reader user). Purely decorative reflows that don't affect comprehension are fine.

Related Success Criteria

1.3.1 Info and Relationships 1.3.3 Sensory Characteristics 1.3.4 Orientation 1.3.5 Identify Input Purpose

Quick Facts

Criterion1.3.2
LevelA
IntroducedWCAG 2.0

Automate Compliance

AccessiSight automatically scans and identifies 1.3.2 issues in your codebase.

Try Scanner Free