Level
A
Since
WCAG 2.0
Entries
2 / 193
/ WCAG criterion

1.3.2 Meaningful Sequence

When the order of content matters to its meaning, the code has to carry that order, not only the layout on screen.

/ What it requires

Where the order of content matters to its meaning, that order has to be the one in the code. A screen reader, a braille display and a text-only browser all follow the document, not the screen. CSS can show the third block first, and a sighted visitor never notices; a blind visitor hears the price before the product, step three before step one, or an error message long after the field it belongs to.

The criterion applies only when sequence affects meaning. A navigation bar and an article can come in either order, and a page may have more than one correct reading order, of which one has to be programmatically determinable. What fails is content whose sense changes when it is read in document order: reordered steps, columns built from spaces, a layout table that linearises into nonsense. Keyboard focus order is a separate matter, covered by 2.4.3.

/ How pages fail it

  • Flex or grid items are reordered with order, row-reverse or column-reverse, so the visual sequence differs from the document.
  • Absolute positioning or a float places a block above content that precedes it in the markup.
  • Columns or tables are faked with spaces and line breaks in plain text, which is then read across the columns line by line.
  • A layout table makes sense on screen and gives the wrong order when its cells are read row by row.
  • The letters of a word are separated by spaces for visual effect, so it is read out letter by letter.

/ How to check it yourself

  1. Turn styles off (Firefox: View, Page Style, No Style) and read from top to bottom. The content should still make sense.
  2. Let a screen reader read the whole page without stopping and follow along on screen. Note every place where the voice jumps.
  3. Select all, copy, and paste as plain text into an editor. That is the document order.
  4. In the browser's developer tools search the styles for order, row-reverse, column-reverse and position: absolute, and compare each hit with the markup.
  5. Repeat the check in a narrow window, because responsive layouts often reorder content at one breakpoint only.

/ How to fix it

  • Write the markup in the order the content should be read and lay it out with CSS afterwards, not the other way round.
  • Remove the order property and flex-direction: row-reverse where they change meaning, and move the elements in the source instead.
  • Replace text aligned with spaces by a real table element or by CSS columns.
  • Space out a word with the letter-spacing property, never with spaces between its letters.
  • If a layout table has to stay, make sure its cells make sense read row by row, and give it role="presentation".

/ What our scanner checks

The rendered pass takes up to 120 visible blocks inside main, article and section elements, skips anything fixed or sticky, and compares each with the block before it in the markup. A block that sits clearly higher on screen in the same column is reported, at most six per page. It measures one desktop viewport and cannot tell whether the order matters, so a person has to read every finding.

/ Who fails it, in our own measurements

Measured bodies failing this criterion, most instances first
BodySectorInstancesScore
Bundesagentur für Arbeitgovernment · DE116
Bundeszentrale für politische Bildunggovernment · DE110

One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.

/ Questions about this criterion

Is the CSS order property an accessibility problem?

It can be. The order property, row-reverse and column-reverse change what is seen without changing the document, and assistive technology follows the document. If both sequences tell the same story, nothing fails. If the meaning depends on the sequence, as with numbered steps or a label and its value, the reordering fails 1.3.2 and usually confuses keyboard users as well.

What is the difference between 1.3.2 Meaningful Sequence and 2.4.3 Focus Order?

1.3.2 is about the order in which content is read: text, images, headings, everything. 2.4.3 is about the order in which interactive elements receive keyboard focus. A page can fail one and pass the other. Both usually have the same cause, markup written in one order and moved by CSS into another, and the same cure: put the source in reading order.

Does the DOM order have to match the visual order exactly?

No. The criterion requires a correct reading sequence only where the sequence affects meaning. A sidebar may come before or after the main text in the code, and two independent columns can be read in either order. Trouble starts when blocks that depend on each other, such as a heading and its paragraph or the steps of an instruction, are separated or swapped.