1.3.2 Meaningful Sequence

What this criterion requires

When the order of content matters, the correct reading order must be programmatically determinable - the DOM order must make sense, not just the visual arrangement.

Who it helps

Screen reader users and anyone linearizing the page, who receive content in DOM order.

Example: fails vs passes

.steps { display: flex; flex-direction: row-reverse; }
    <!-- DOM order: step 3, step 2, step 1 -->

<!-- DOM order matches reading order: step 1, step 2, step 3 -->
    .steps { display: flex; }

Screen readers follow DOM order. CSS that reorders visually while the source stays scrambled fails this criterion.

How to meet and fix it

• Keep DOM order aligned with visual order; be careful with CSS ordering (flex order, grid placement, floats)
• Test by tabbing and by reading the page with a screen reader

Common failures auditors find

• CSS reordering that makes a screen reader announce steps 3-1-2
• Multi-column layouts whose source order interleaves unrelated content

Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.

In PDF documents

PDF reading order lives in the tag tree order, which can differ from the visual layout. Multi-column layouts, sidebars and forms are the classic places where a screen reader reads a PDF in the wrong sequence.

Check any document against this and 80+ more automated checks with the free PDF accessibility checker.

Last updated 12 August 2026. Reviewed by the EqualWeb accessibility team.