The first step when designing for mobile is getting familiar with the native environment accessibility standards. 1.Support Native Mobile Accessibility Features
draft document already available online and Android accessibility guidelines. These suggestions are based on guidelines found in the WCAG 2.1. This existing documentation is very robust and detailed, so I’ve summarised below what I believe to be the most crucial best practices to follow when designing for an accessible mobile app. by June 2018 and current recommendations are extended to mobile design as well. W3C is working to officially release a new version of the document WCAG 2.1. Section 508 requires conformance to the WCAG 2.0 Level AA that addresses the most common barriers for disabled. In the US, Section 508 Law mandates all technology used and maintained by the federal government to be accessible for people with disabilities. WCAG provides the foundation for many laws worldwide on the subject of accessibility. It doesn’t cover native mobile apps specifically, but is more a general set of rules for web apps and websites. The current standard for designing web accessibility is a document by W3C called Web Content Accessibility Guidelines (WCAG) 2.0.
Design standards that include accessibility adherence has meant that:
When talking about accessibility it’s important to also take into account seniors as well as those whose senses are temporarily or permanently impaired.