Missing view state in spoken output

Interactive controls that have states (selected, checked, etc.) must expose their current state programmatically so screen readers can announce it correctly. For non-native elements, ensure the correct state is exposed if applicable.

Success criteria

The rule checks for the following potential violations:

• Missing state information
  Interactive elements do not expose their current state to accessibility services, so screen readers cannot announce it.

How to fix

To fix violations related to missing view state in spoken output, follow these steps:

• Android: Use standard widgets where possible (CheckBox, ToggleButton, etc.). For custom controls, expose correct state by setting appropriate accessibilityClassName and maintaining state properties (isSelected, isChecked, etc.) so TalkBack can announce the state correctly.
• iOS: Use standard controls where possible (UISwitch, UISegmentedControl). For custom controls, set appropriate accessibilityTraits (e.g., .selected, .checked) and maintain correct state flags so VoiceOver can announce the state correctly.

Applicability

All mobile apps (Android/iOS), including native, React Native, Flutter, and hybrid apps where labels are used.

Example

Add example scan report or screenshot here.

For any missing information, please refer to the original Confluence documentation or add a placeholder as needed.