30 Days of Inclusive Design and Development on Android

The Ministry of Testing is starting a new challenge to promote accessibility testing. I think it’s an awesome idea! Here’s my take on an Android-flavoured version of the challenge.

I’ve only written 15 tasks here so you can take a day of rest between each of these to make it last the whole month of May. 😊

  1. Learn about different types of users and the range of abilities they may or may not have.
  2. Use Accessibility Scanner to scan your Android apps for easy-to-fix issues.
  3. Enable TalkBack on your device and complete three common tasks (like checking your email, or liking a Tweet) in your favourite apps.
  4. Write (and share!) a post about one of the Four Principles of Accessibility relating it to one of your products.
  5. Watch The Movie Guide to Accessibility then write a tweet about something you learned from it.
  6. Try to use your Android app without touching the screen (or mouse!) You can connect a keyboard with a USB-OTG adapter. As well as recognising what’s difficult or impossible, celebrate the parts that work well!
  7. Learn how to add focus support to your app.
  8. Test your app for colour accessibility (Material Color Tool, Stark — a Sketch plugin).
  9. Find five inclusive design enthusiasts to follow on Twitter. You can search for tags like `a11y` and `androiddev`.
  10. See how media apps like YouTube and Netflix behave when TalkBack is turned on compared to when it’s turned off.
  11. Identify information “widgets” in your UI where you can set explicit content descriptions for groups of elements (example of grouping, why you should set explicit descriptions).
  12. Learn how to hasten slowly! Discover how Renato Iwashima began transforming the LinkedIn Android app with a goal of inclusiveness with these articles (Beginning the Journey and Quick Tips).
  13. Identify action items in your UI and add custom usage hints to replace the non-descriptive “double tap to activate” (customise usage hints).
  14. Increase your system font size to the largest available to check your app for clipped content. If your device is running Android N or greater, you can also increase the display size.
  15. Provide alternative, parallel interfaces to optimise navigation for users of assistive technology. You can use libraries like accessibilitools to make this easier.

Finally, discuss how you can make inclusive design part of your normal day-to-day workflow with your team (design, development and QA) and share these ideas online.

If you have any other links, tools, talks and blogs you think will be helpful, please add them as a response!