Text Truncation Issues

Text content in iOS apps must not be truncated in ways that hide meaningful information from users, especially when Dynamic Type increases font sizes.

WCAG Reference

Maps to: WCAG 1.4.4 Resize Text | Applies to: WCAG 2.0, WCAG 2.1, WCAG 2.2 Introduced in: WCAG 2.0 | Level: AA | Read the official specification →

What this rule checks

The scanner identifies text elements that are clipped or truncated (ending with "...") when the content contains meaningful information that is lost, particularly when the user has increased the text size through Dynamic Type settings.

Why it matters

Users with low vision rely on Dynamic Type to increase text size. If the app truncates text instead of expanding or wrapping, these users lose access to important information like button labels, instructions, or data values.

Common failure patterns

• labels with a fixed numberOfLines = 1 that truncate long content
• table cells with fixed heights that clip multi-line text at larger Dynamic Type sizes
• navigation bar titles that truncate when text size increases
• buttons with fixed widths that clip label text

Remediation guidance

• use numberOfLines = 0 with Auto Layout constraints to allow text to wrap
• set minimum cell heights using Auto Layout rather than fixed values
• use adjustsFontForContentSizeCategory = true on text elements
• test with the largest Dynamic Type size (Accessibility sizes enabled) to confirm no meaningful content is lost

Related docs

• iOS Rule Repository
• Accessibility Issue Remediation Guide