Meaningful Sequence
The order in which content is announced must match the order in which it visually makes sense to read.
Maps to: WCAG 1.3.2 Meaningful Sequence | Applies to: WCAG 2.0, WCAG 2.1, WCAG 2.2 Introduced in: WCAG 2.0 | Level: A | Read the official specification →
What this rule checks
The scanner examines whether the programmatic reading order of the screen matches the meaningful visual sequence of its content. Detection is AI-based, comparing the announced order against the visual layout. (AI rule) Where Traversal Order Does Not Match Visual Layout targets misused traversal overrides on focusable controls, this rule concerns the sequence of the content itself.
Why it matters
Content whose meaning depends on order — steps in a process, a heading followed by its body, a price next to its product — loses that meaning when announced out of sequence. The user hears all the pieces but cannot reconstruct the whole.
Common failure patterns
- multi-column layouts read column-by-column when the meaning flows row-by-row
- captions announced before the content they describe
- visual ordering achieved purely through positioning while the hierarchy retains insertion order
Remediation guidance
- reorder views in the layout to match the visual reading order
- use
android:accessibilityTraversalBefore/android:accessibilityTraversalAfterto set the correct TalkBack traversal sequence when reordering in code isn't possible
Chat with Us