Skip to main content

Back to Guidelines

Perceivable
WCAG 1.3.2
Level A

What is Meaningful Sequence?

The reading order in the DOM must match the visual order so meaning stays clear for assistive technologies.

Avoid reordering content in ways that change how users understand the page.

Screen reader users following the DOM.
Keyboard users tabbing through content.
Users who depend on a logical, predictable flow.

Improves Accessibility
Better Structure
Better User Experience
Supports Compliance

Good vs Bad Examples

Use the tabs to compare logical order with confusing order.

Logical reading sequence

html

<h2>Plan Summary</h2>
<p>Choose the option that matches your needs.</p>
<button>Get Started</button>

Why this is correct:

DOM order matches the visual order.
Screen readers announce content logically.
Keyboard focus follows the same flow.

Implementation Checklist

Progress0 / 6 completed (0%)

DOM order matches visual order.
CSS does not reorder content in a way that changes meaning.
Screen readers encounter content in a logical sequence.
Keyboard focus follows the visible flow.
Responsive layouts keep reading order predictable.
Meaningful sequence is verified during QA.

Knowledge Check

Answer Yes or No to test your understanding of meaningful sequence.

Score: 0 / 5 · Answered: 0 / 5

Should DOM order match visual order when meaning matters?

Can CSS reposition content if the meaning changes?

Should screen readers follow a logical sequence?

Does keyboard focus need to remain predictable?

Is WCAG 1.3.2 about meaningful sequence?