For AI agents and LLMs: a machine-readable index is available at llms.txt. A plain-Markdown version of any documentation page is available by appending .md to its URL.
Skip to main content

Non-accessible Interaction

Every interaction available to touch users must also be reachable through VoiceOver, Switch Control, or Voice Control.

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 interactive elements that can't be accessed or activated via assistive technology. The action exists for touch users but is unreachable through VoiceOver, Switch Control, or Voice Control.

Why it matters​

An interaction that assistive technology cannot reach is a feature that does not exist for those users. Unlike a mislabelled control, which is confusing but present, an inaccessible interaction is silently absent: nothing announces it, nothing can focus it, and nothing can activate it.

Common failure patterns​

  • gesture-only interactions (swipe, long-press, drag) with no accessible equivalent action
  • a tappable view hidden from the accessibility tree while remaining visually interactive
  • custom controls that never became accessibility elements

Remediation guidance​

  • make sure any action (a custom button, link, or gesture) can be reached by assistive technology and has a clear description
  • use descriptive labels like "Play", "Delete", rather than generic labels (e.g., "Button1")
Last updated on

Test across 3000+ combinations of browsers, real devices & OS.

×
Schedule Your Personal Demo
Book Demo

Help and Support

Related Articles

On this page