Tip 1: Ensure screen readers makes sense
As a tester, you should ensure that when you’re testing with screen readers or text-to-speech functionality (i.e. iOS’s VoiceOver or Android’s TalkBack), you go beyond just checking that each widget or control announces it’s function. You need to ensure that the whole screen makes sense when you get screen readers to read out the whole page from top to bottom. Often, vision impaired users will explore the entire page to build their mental model before they deep dive into interacting with the page.
Tip 2: Champion accessibility Acceptance Criteria (AC)
Ensure you are part of your product or project team’s backlog refinement sessions and you champion accessibility by including accessibility acceptance criteria into your stories. As you’re at the end of the process before a feature is released, you can ensure accessibility doesn’t fall through the cracks.
Tip 3: Become familiar with tools and features
Android has a great app called Accessibility Scanner which allows you test the accessibility of your Android app quickly. It doesn’t replace the need to manually test but is a great first pass.
Also go through the various phones’ accessibility settings and become an expert in text-to-speech and how the various gestures work, as well as other settings to do with colour, contrast and text and display sizes.