Skip to main content
Version: 2.x

Native Accessibility Checks

This page details the complete set of accessibility checks that AMA automatically runs on your app to help identify and resolve common issues. AMA currently supports 13 rules:

Pressable element checks​

Missing accessibility role

This issue is reported when a Pressable element does not specify an aria-role attribute.

Missing accessibility label

This issue is reported when a Pressable component has no visible text and does not define an aria-label attribute.

Contrast ratio too low

This issue is reported when a Pressable does not have sufficient contrast between its text and background color.

Tappable area too small

This issue is reported when a Pressable element has a tap target smaller than the recommended size.

Text in all caps

This issue is reported when a Pressable uses all-caps text and does not define a properly cased aria-label.

Accessibility label in all caps

This issue is reported when a Pressable element has an aria-label written entirely in capital letters.

Text element checks​

Contrast ratio too low

This issue is reported when a Text element does not have sufficient contrast between its text and background color.

Text in all caps

This issue is reported when a Text element uses all-caps text and does not define a properly cased aria-label.

No headings used

This issue is reported when no elements on the screen are marked with an aria-role of heading.

UI Interactions​

Missing accessibility state handling

This issue is reported when an interactive element changes state but the corresponding ARIA state is not updated.

Examples include:

  • aria-checked
  • aria-expanded
  • aria-selected
  • aria-disabled
  • aria-busy  

Forms​

Return key not handled

This issue is reported when a form field does not handle the keyboard return action, preventing focus from moving to the next field.

Missing visible label

This issue is reported when a form field has no visible text label associated with it.

Duplicate accessible name

This issue is reported when a form field exposes both a visible label and an aria-label with the same value, resulting in a duplicated accessible name.