Images with Text

Meaningful text baked into an image's pixels is invisible to screen readers and must be provided as real text or an accessible description instead.

WCAG Reference

Maps to: WCAG 1.1.1 Non-text Content | 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 images on the screen for meaningful text rendered inside the image itself — text that exists only as pixels, with no real text element carrying it. Detection is AI-based, analyzing the rendered screen rather than the view hierarchy alone. (AI rule)

Why it matters

A screen reader can only speak what the accessibility tree contains. Text baked into a banner, promotion image, or screenshot is invisible to TalkBack, and it does not scale with the user's font-size setting, does not reflow, and cannot be selected or translated. The information exists solely for sighted users.

Common failure patterns

• marketing banners exported from design tools with headline text flattened into the bitmap
• screenshots or diagrams containing instructions
• stylized text rendered as an image to preserve a custom font

Remediation guidance

• avoid embedding meaningful text inside images — use real text views (TextView) so TalkBack can read the content, or provide the text through android:contentDescription
• if the image is decorative, mark it as such (android:importantForAccessibility="no") so screen readers skip it

Related docs

• Android Rule Repository
• Accessibility Issue Remediation Guide