Text Truncation

The text truncation rule checks whether visible text content remains fully readable when users increase the font size. Truncated text can hide critical information, especially for users with low vision or those who rely on larger text for comfortable reading. Visible and resizable text improves accessibility and provides a consistent experience for all users.

Success criteria

The specific criteria for success are:

• Scalable fonts: Text must use relative units to allow dynamic resizing.
• Flexible layouts: Text containers must use dynamic sizing.
• No fixed sizes: Avoid fixed height or width values that prevent text containers from resizing to fit larger text.
• Scrollable containers (if needed): If the layout cannot expand, use a scrollable container (ScrollView on Android, UIScrollView on iOS) so users can access all text content.

How to fix

To prevent text truncation:

Example

The following screenshot highlights a text truncation violation in an Android app:

Errors

• The TextView uses the correct font unit (sp) for scalable text, but its parent view has a fixed height of 273dp.
• The fixed height restricts the TextView from expanding as text size increases, causing truncation.

Fix

To fix this violation:

• Change the parent view’s height from 273dp to wrap_content to allow it to expand with the text.
• Set the TextView layout_height to wrap_content.
• If the text is long, place the TextView inside a ScrollView so users can access the entire content.

References

WCAG

• 1.4.4 Resize Text (Level AA): WCAG 2.1 · WCAG 2.2

RAAM 1.1

• 8.2: RAAM 1.1