Skip to main content

Accessibility Checklist

The checklist is based on the Guidelines and is focused on the testing side of accessibility.

caution

Addressing the issues called out in this checklist will help improve the experience for everyone who uses the app, but it won't guarantee that the app will be 100% accessible!

Feature​

  • Are you able to use it by using Screen Curtains (iOS) or setting to 0 the screen luminosity?

Order​

Components​

What is this thing? Does the screen reader announce:

  • Role (ex. button)
  • Name (ex. "Submit")
  • State (ex. disabled, checked, expanded, etc...)

What happens when I click the thing?

  • Is it clear what will happen if you click the thing?

Hint?

  • Is the label enough?

Predictable/Consistent

  • Is the appearance consistent across the app?
  • Is the behaviour consistent across the app?

*Size*

  • Has a minimum size of 44/48px?

NOTE: hitSlop does not guarantee a minimum size

Animations​

  • Ensure animations are subtle and do not flash too much.
  • Are translation animations disabled if the user has chosen reduce motion from the device settings?

BottomTabNavigator​

  • Does the screen reader announce the element as: selected status BUTTON TITLE, index of total, tab, double-tap to activate?

Example:

  • selected Home, 1 of 5
  • Account, 5 of 5

Button​

When I focus on an element, the screen reader should read it in the correct order on all devices:

  • Label: Purpose is clear and matches its label
  • Role: Identifies as a button
    • iOS: Identifies as button
    • Android: Identifies as a button and also reads "double tap to activate"
  • Group: Its label is grouped and focused with the button
  • State: Reads its state, i.e. disabled/dimmed
note

When testing on Android, it's important to note that some states, such as "ticked" or "checked," are read before the button label.

Focus​

  • Does the first element/header of the screen receive the focus automatically when navigating to a new screen/modal?

Form​

  • Can you navigate through the various fields using the corresponding keyboard "next" key?
  • Can you submit the form using the "enter" key?
  • Invalid fields: Is the error read with the text once the latter gets the focus?
  • Is the label announced when a TextInput is selected?

Headings​

  • Is there at least one heading in the Screen/Modal/Drawer/Bottom sheet?
  • Is the section title announced as "header"?
  • Does a header get automatically focused when the screen/modal/drawer/bottom sheet appears?

Lists & Grids​

  • Does TalkBack announce "in list/grid" and/or "out of list/grid"?
  • If there is a filtering: Does the screen reader automatically announce how many items the list is showing?

Text​

  • Is the text readable with a font size scaled up to 300%?
  • If the text is uppercase, does the screen reader read it correctly or does it spell the words?
  • Are you able to focus all the links within a Text?

Time limits​

  • Does the user have enough time to read an auto-hiding message?