Accessibility Testing Criteria, tell us what you think

02/06/2015

Why have we created a set of Accessibility Testing Criteria?

We’ve been talking to people in the industry and it’s become apparent that there are not enough apps out there that are truly Accessible. We know that both hardware and software have evolved their Accessibility features, however for the apps themselves, this is not always the case.

So it seemed like a good idea to try and help developers to make their apps Accessible, and as a result, enable them to tap into a wider audience.  

So with help from the Mobile Manufacturers Forum (MMF), we’ve come up with a set of Accessibility tests designed to make applications Accessible and easy to use for those with disabilities in certain categories (vision, hearing, speech, dexterity and cognition) on an Android device.

How have we done it?

We couldn’t have done it alone, we’ve carried out lots of research and had discussions with experts in this field and the wider industry.

The Accessibility Testing Criteria has been created with input from or referenced to many important industry organisations:

• Mobile Manufacturers Forum (MMF), their members and the GARI website
• W3C WCAG 2.0 recommendations on Accessibility
• Android developer site recommendations on Accessibility
• AT&T recommendation on website Accessibility
• AQuA members experience and their Accessibility teams

We are still learning, so if you think that you have something to say to help us improve on this then please let us know.

Take a look at the Accessibility Testing Criteria

› back