Non-Responsive Container Clips Text

Layout containers that hold text should size flexibly so they can grow alongside text scaled up by the user's font setting.

WCAG Reference

Maps to: WCAG 1.4.10 Reflow | Applies to: WCAG 2.1, WCAG 2.2 Introduced in: WCAG 2.1 | Level: AA | Read the official specification →

What this rule checks

The scanner examines whether layout containers that hold text use flexible sizing (match_parent, wrap_content, or 0dp with layout_weight) rather than fixed pixel dimensions. Containers without any text content are not checked — fixed dimensions are legitimate for icons and decorative elements.

note

The required device data is available on Android 11+ only; on older devices the rule reports Incomplete.

Why it matters

This rule is the counterpart to Dynamic Type Support: even when text is correctly sized in sp, a hard-sized parent container cannot grow with it. When the user enlarges their font scale, the text expands but the container does not — the result is clipped, truncated, or overlapping text, and content can become unreadable or actions unreachable. WCAG 1.4.10 requires content to reflow without loss of information or functionality.

Common failure patterns

• cards, chips, or banners with hard-coded layout_width/layout_height in dp wrapping text
• fixed-height rows in lists whose text truncates at larger font scales

Remediation guidance

• identify the container that wraps the clipped text
• replace fixed dimensions with flexible sizing so the container grows with its content — use match_parent, wrap_content, or 0dp with layout_weight instead of a fixed dp/px dimension. In ConstraintLayout, use 0dp with constraint chains rather than fixed sizes.

Related docs

• Dynamic Type Support
• Android Rule Repository
• Accessibility Issue Remediation Guide