Application Inclusivity Checklist

Note that this is more of a reminder of things to check. Good accessibility is much more than just filling out a checklist.

⭐ Golden Rule: If something might be difficult for someone, it doesn’t mean you CAN’T do it, you just need to make sure there is an alternative way to access the same content.

🥈 Silver Rule: Respect all user preferences regarding accessibility.


💡 Have you ever called an automated phone system where they asked you to press a number for what you want… Imagine if every button on your application was like that? Would you like to wait through potentially hundreds of options?

💡 Users without the ability to control their hands will commonly have their phone or iPad attached to their wheelchairs. Forcing them to get someone to rotate their device to use it is a bad experience


💡 Some common text practices are highly visual. Arrows (→), abbreviations (lbs), emoticons (:D), and kaomoji (◕‿◕) can be problematic without some specific work.

💡 Frequently test with different text sizes and weights to catch issues early.

💡 Make sure you test all of your text to make sure it sounds great with many common screen readers (Talkback or Voiceover)


💡 Turn on your screen reader and try using your app with your eyes closed. You will learn a lot about where you can improve very quickly.


💡 Don’t forget to test Back Buttons, Chevrons, Icons, and Logos.


💡 Color blindness might not be the only reason to differentiate without color. Some cultures might also place different significance on certain colors. check out this article for more information.

Common User Preferences

The application should function while following user preferences.

This list is not exhaustive. Please check your platform’s documentation for details on supported accessibility preferences and features.