A. Appendix A: Accessibility Checklist

Written by Tori Gonda

Use these checklists to remind you what to look out for in your app. You can also pick and choose items for an audit, QA steps, or a PR checklist. While these lists don’t cover all the guidance from WCAG, they provide a good overview of the more common items you’ll see on Android.

Each item references the chapter in this book that covers the topic, so you can easily find where it is in the book.

Quick peek checklist

Use this abbreviated checklist when you only have time to do a quick, initial pass. These are often quick wins and might work well for a PR checklist.

• Images and icons have content descriptions. “Chapter 2, Hello, Accessibility!” and “Chapter 4, Perceivable — Layout & Labeling”.
• Screen orientations are supported. “Chapter 4, Perceivable — Layout & Labeling”.
• Inputs are labeled. “Chapter 4, Perceivable — Layout & Labeling” and “Chapter 9, Understandable”.
• Text is scalable. “Chapter 4, Perceivable — Layout & Labeling”.
• Instructions don’t rely on characteristics such as size, shape and color. “Chapter 5, Perceivable — Time-Based Media & Cues”.
• Text and icons have adequate color contrast. “Chapter 6, Perceivable — Colors”.
• Touch targets are at least 48dp by 48dp. “Chapter 7, Operable — Navigating the Screen”.
• There is no flashing. “Chapter 8, Operable — Movement & Timing”.

Thorough checklist

Use this checklist when you’re doing a full audit or are trying to remember a rule.

• Images and icons have content descriptions. “Chapter 2, Hello, Accessibility!” and “Chapter 4, Perceivable — Layout & Labeling”.
• Views that are clickable are also focusable. “Chapter 2, Hello, Accessibility!”.
• Headers are labeled. “Chapter 4, Perceivable — Layout & Labeling”.
• Views are laid out logically and predictably. “Chapter 4, Perceivable — Layout & Labeling”.
• Related items are grouped. “Chapter 4, Perceivable — Layout & Labeling”.
• All screen orientations are supported. “Chapter 4, Perceivable — Layout & Labeling”.
• Inputs are labeled. “Chapter 4, Perceivable — Layout & Labeling” and “Chapter 9, Understandable”.
• Text is scalable. “Chapter 4, Perceivable — Layout & Labeling”.
• Time-based media has alternatives and is controllable. “Chapter 5, Perceivable — Time-Based Media & Cues” and “Chapter 8, Operable — Movement & Timing”.
• Instructions don’t rely on characteristics such as size, shape and color. “Chapter 5, Perceivable — Time-Based Media & Cues”.
• Text and icons have adequate color contrast. “Chapter 6, Perceivable — Colors”.
• Support dark mode. “Chapter 6, Perceivable — Colors”.
• All items are reachable via keyboard navigation. “Chapter 7, Operable — Navigating the Screen”.
• Content descriptions are unique. “Chapter 7, Operable — Navigating the Screen”.
• Focus order preserves meaning. “Chapter 7, Operable — Navigating the Screen”.
• The purpose of links is clear. “Chapter 7, Operable — Navigating the Screen”.
• Gestures have one-tap alternatives. “Chapter 7, Operable — Navigating the Screen”.
• Touch targets are at least 48dp by 48dp. “Chapter 7, Operable — Navigating the Screen”.
• Allow adjustable timing. “Chapter 8, Operable — Movement & Timing”.
• There is no flashing. “Chapter 8, Operable — Movement & Timing”.
• Support right-to-left layouts. “Chapter 9, Understandable”.
• Language is clear. Avoid idioms and explain abbreviations. “Chapter 9, Understandable” and “Chapter 11, Designing for Neurodiversity”.
• Navigate consistently. “Chapter 9, Understandable”.
• Provide support for errors. “Chapter 9, Understandable” and “Chapter 11, Designing for Neurodiversity”.
• Use system views when possible. “Chapter 10, Robust”.
• Custom views communicate with accessibility services. “Chapter 10, Robust”.