All WCAG criteria
WCAG 1.3.2 · PerceivableLevel A

1.3.2Meaningful Sequence

When the order of content matters, the order must be programmatically determined — so screen readers and other assistive tech read it in the right order.

Common failures

Patterns that fail this criterion.

  • 01CSS `position: absolute` reordering elements visually but not in DOM
  • 02CSS flexbox `order` property visually reordering without DOM matching
  • 03Floats/grids that look one way visually but read another for screen readers
How to test

Testing approach: manual.

Manual — disable CSS or use a screen reader; confirm reading order matches visual order.

How to fix

Remediation steps.

  1. 1

    Order DOM correctly first

    Put elements in the meaningful logical order in the HTML. Then style.

  2. 2

    Avoid layout-only DOM tricks

    CSS `order` and absolute positioning that swap order break assistive tech. If you must, fix the DOM.

Scan for WCAG 1.3.2 on your site

Find every violation in 42 seconds.

AccessProof runs axe-core 4.9.1 against your site and flags every WCAG criterion with the offending element selector. WCAG 1.3.2 is one of 49 criteria we check on every scan.

Start free auditTry free scanner — no signup
Related criteria

Often appears with…

WCAG 2.4.3 · Level A

Focus Order

WCAG 1.3.1 · Level A

Info and Relationships

All 50 WCAG 2.1 Level A + AA success criteria explained.

View the full checklist