The Smart Phone accessibility testing can be divided into two parts.
- Unit Testing
- Heuristic Testing
The Unit testing can be performed while developing the accessible code. there are a lot of integration test tools available on GitHub. The unit test considers easier than heuristic testing because you can look into the code and check WAI Aria roles and properties by manual and automatic testing tools. Normally, accessibility has been done after designing and coding and point out by accessibility consultant and QA testers. it is important to bring accessibility testing into a design process so tester can run continuous integration that helps the organization to reduce cost. The best practice is to run all test daily to make sure that project accessibility is not compromised.
Android Analyzer is the best example of for unit tester. The Pre built-in analyzer helps the developer and tester to test accessibility while developing the Andriod application. This tool has built-in rules set to develop a mobile application with WCAG 2.0 standards(which is obvious, not complete accessibility solutions). but this analyzer allows testers to run in accordance with any filter being applied, such as by standard guidelines failure and warn and generate a notification for accessibility violations.
Accessibility testing or you can say, accessibility in mind while starting any project by testing by the user with disabilities is must in this Agile era. Sometimes individual components are accessible, but when they are put together into a process accessibility issues can arise.
But on the other hand, heuristic testing is difficult because it needs manual testing while testing the interface with AT(Assistive Technology) like Screen Readers, Zoom, Stylus etc.
Most of the Heuristic testing, Depends on the personas based approach because real user testing is expensive and time-consuming.