1) TalkBack Experience

Talkback is a screen reader provided free in the Android Operating System. A developer can test if Talkback works with their app by going to settings, accessibility and turning on Talkback, than trying to use the app without sight. Optionally, you may want to download the shades app from the google store, which blanks your screen so you can't cheat.

2) Labelled Buttons And Controls

Buttons and controls should have a clear label that describes the purpose or action that is performed when pressing the button, activating the control or what to enter into a form field. The compiler should provide you with an alert when your controls are missing labels. The labelling of items is critical for talkback, brailleback, justspeak and any other accessibility service to function properly. Not having proper labels interfers with voice recognition systems like justspeak, screen readers like talkback and braille output to braille displays through brailleback.

3) High Contrast Black Background With Bright Text Available

One just needs to look at the most common features designed for low vision users built into CCTVs, Screen Magnification software and various Operating Systems and the majority of these features revolve around setting background/foreground colors and font sizes. For many people with low vision, a black or dark background is necessary to read material effectively. Even though some 3rd party manufacturers offer an invert function in their firmware, this is not effective as the inverted setting doesn't deliver a true white on black color scheme. In addition to this, the inverting function creates an unusable color combination if a screen within an application or a webpage is gray or black. Finally, inverting also usually inverts pictures and photos, making friends and family look like aliens. Many people with low vision
rely less on magnification on a mobile phone and rely on Talkback. However, when doing this they use their sight to speed up navigation and follow what's going on, on the screen itself. For example when you can see where buttons are, you can go to them directly with my finger, thus skipping over the linear top to bottom reading that is imposed by default with a screen reader and instead moving directly to the object you want.

4) Font Sizes Are Sufficiently Large Or Adjustable To Be Large Enough To Read Comfortably

Having a choice of fonts and font sizes will ensure that everyone will be able to read the text of your application. Supporting the native increase in font size is also important for readability.

5) App Or Game Usable Without relying on Hearing

If your app or game provides audio, you want to ensure that the application is usable without hearing. Some examples of how to do this would be: If you have an audio track or video with an audio track to provide captions so that when you can't hear the audio clearly, you can still follow along by reading the text. If sounds are required to be alerted that something is going on in the application or game then pair it with a visual indicator or vibration to alert the person using your app or game that something is happening.

6) Keyboard Accessible

The application should be usable by someone who is using a phone with a physical keyboard or using a bluetooth or usb keyboard without using the touch screen to operate the app or game. This also ensures that other adapted aids such as braille keyboards, macro pads, switch systems and alternate inpud devices will work with the app or game.

7) General Experience using this app or game with my accessibility tools and settings

An overall rating of the usability of the application for people with disabilities.