Redundant Role Keyword in Accessibility Label

Accessible labels shouldn't repeat a control's role — words like "button" or "switch" — since TalkBack already announces the role separately.

WCAG Reference

Maps to: WCAG 4.1.2 Name, Role, Value | 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 flags accessible names that embed the control's role — words like "button", "switch", "checkbox", "slider", "dropdown" — on controls whose role TalkBack already announces. Common informal variants are also flagged ("btn", "toggle", "text field", "picker"), since they encode the same role intent. Only role words matching the actual control type are considered: "Play button" on a text label that is not a button is not flagged.

Why it matters

TalkBack appends the role to every announcement. A Button labeled "Submit button" is announced as "Submit button, Button" — the user hears the role twice on every focus. Across a whole screen this doubles the verbosity of navigation and slows down screen reader users without adding any information.

Common failure patterns

• labels that describe the widget instead of the action: "Settings icon", "Search button", "Volume slider"
• abbreviated role words in labels: "Submit btn", "WiFi toggle"

Remediation guidance

• identify role keywords — find words like "button", "link", or "icon" in the label that describe the control's type
• remove them — "Settings Icon" becomes "Settings"
• assign the role programmatically instead — use the Button class, or role = Role.Button in Compose, so TalkBack announces it once, correctly

Related docs

• Android Rule Repository
• Accessibility Issue Remediation Guide