Rule

Reading order vs visual order

CSS reordering should not make reading order diverge from the visual order.

Rule
reading-order-divergence
WCAG 2.2
1.3.2 Meaningful Sequence (opens in a new tab) (Level A)
Severity
Moderate

What it checks

Screen readers read a page in source order. When a flex or grid container uses the CSS order property or a reversed flex-direction, the blocks can appear on screen in a different order from the source. The rule compares the two for sibling blocks in the same container, where at least two of them hold text.

When a person decides

A difference is only ever sent for review. The criterion asks whether the change of order changes the meaning, and only a person can judge that. A container whose reordered children are all links, buttons or fields is left to the focus order rule, which asks the same question from the keyboard side.

Example

Sent to review

<div style="display: flex">
  <p style="order: 2">Step 1: Unplug the kettle.</p>
  <p style="order: 1">Step 2: Empty the water.</p>
</div>

Passes

<div style="display: flex">
  <p>Step 1: Unplug the kettle.</p>
  <p>Step 2: Empty the water.</p>
</div>

The engine is tested against both examples.

How to fix it

Change the source order to match what is shown, rather than reordering with CSS. If the difference does not change the meaning, the finding can be dismissed.

Check your own pages

This rule runs in every pour audit: the browser extension, the bookmarklet, the command line and the editor. Get pour, free.