1.3 Adaptable · SC 1.3.2

A2 min read

Meaningful Sequence

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

In plain language

If the order content is read in matters for understanding it, that reading order needs to be correct in the code as well as on screen.

Why it matters

Screen readers read content in the order it appears in the code, which may differ from how it looks on screen. If CSS visually rearranges things without changing the code order, screen reader users hear the content in a confusing sequence.

In practice

Fails this criterion

A page uses CSS to visually reorder a multi-column layout, but the underlying HTML order doesn't match. A screen reader reads the paragraphs in a jumbled sequence that doesn't make sense.

Meets this criterion

The HTML follows the same logical order as the visual reading order (top to bottom, column by column), so a screen reader reads the content in the intended sequence.

Test it yourself

Use a screen reader (or disable CSS on the page) and go through the content. Does it still make sense in the order it's read out?

Read SC 1.3.2 on the official WCAG 2.2 specification ↗