Success Criteria

WCAG 1.3.2 Meaningful Sequence

Success Criterion 1.3.2 requires that when the reading order of content is important to understanding it, the correct order can be programmatically determined. It's a Level A criterion under Guideline 1.3 (Adaptable).

Where this actually breaks

CSS gives visual layout complete freedom to differ from DOM order — order in flexbox/grid, absolute positioning, floats, can all make content appear in a different visual sequence than the sequence it exists in the underlying HTML. A sighted user sees the CSS-arranged version; a screen reader reads the actual DOM order. When these diverge significantly for content where sequence carries meaning (a numbered set of instructions, a form flowing logically from one field to the next), a screen reader user gets a scrambled, confusing version of the same content.

A common concrete example

A two-column layout built with CSS floats or grid, where the visual left column is actually the second element in the DOM (reordered visually via CSS) — a sighted user reads left-to-right, top-to-bottom as expected, but a screen reader announces the DOM's actual order, which might read column two before column one.

How to check for this

The classic test: disable CSS entirely (or use your browser's reader-mode view) and read the page in its raw, unstyled order. If the content still makes logical sense — instructions still flow step by step, a form's fields still progress sensibly — the DOM order is fine regardless of how CSS visually repositions things. If it reads as scrambled or confusing, the DOM order (not just the CSS) needs to change to match the intended reading sequence.

The distinction from focus order (2.4.3)

This criterion is about the sequence content is read in; Focus Order (2.4.3) is specifically about the sequence interactive elements receive keyboard focus in when tabbing. They often break together (since focus generally follows DOM order too), but they're testing two related, distinct experiences.

Common questions

What is WCAG 1.3.2?

A Level A criterion requiring the DOM and reading order to be meaningful when sequence matters, so assistive technology reads content in the intended order.

What causes 1.3.2 violations?

Using CSS (like flexbox order or absolute positioning) to visually rearrange content so the visual order no longer matches the underlying DOM order screen readers follow.

How is 1.3.2 different from 2.4.3?

1.3.2 is about the reading order of content; 2.4.3 Focus Order is specifically about the order keyboard focus moves through interactive elements.