Chapter 7 Accessibility

There can be scenarios when disabling this feature can provide a more accessible experience. One example is in a wordsearch application I built. The application made the letters appear as big as possible, so any additional scaling by the operating system would result in parts of the text being cut off. I advise using this option sparingly.

Testing Your Application’s Accessibility

Each platform supported by .NET MAUI has its own set of guidelines around testing for accessibility and even tools to aid that journey. In this section, you are going to take a brief look at what each platform provider offers.

Android

Google, much like each of the other platform providers, does recommend that you perform a manual test, such as turning on TalkBack and verifying that the user experience is as you have designed.

Google also offers some analysis tools to detect whether any accessibility guidelines are not being met. There is a good list provided by Google with a breakdown of the functionality provided by each tool at https://developer.android.com/guide/topics/ui/accessibility/ testing#analysis.

iOS

Apple doesn’t offer as much as Google on this front. There is the Accessibility Inspector but it only focuses on allowing you to view the information that the screen reader will be provided. I don’t feel this is as good as taking a dry run through your application with the VoiceOver assistant turned on. Further information on

215