Mobile Accessibility Advent Calendar Part 2

Day 13 of the Mobile Accessibility Advent Calendar!

 

One of the top issues seen in mobile applications, is the improper grouping of content. What do I mean by improper grouping? In Android and iOS applications you can create content and have the whole item be tappable, like the iOS settings menu. You can also create components such as cards that can have multiple different pieces of information in them, like in commercial applications where you have an image of the item, description of item, and the price.

 

By default, when creating components such as these each individual item is accessible one by one for screen reader users. This causes a very frustrating experience when navigating complex applications. So what's the solution? Group similar content together to make each accessibility focus point clear and concise for the user.

 

• For good and bad examples of grouping see my article here: 




• More information on how to group content in Android:

  
  
  

  Question I am often asked is, "it seems like mobile accessibility is the right thing to do, but is there anything that is actually enforcing that my application be accessible?" or "All I see is things that say 'web' accessibility but nothing for mobile, so we are off the hook right?".

  
  
  

  In the past year or so, it is no longer web that is being called out, it is mobile applications as well! So when anyone asks does the application need to be accessible, emphatically say YES! Besides from the question of WCAG (which we will get to in another post), there are things in law that now point to the need to have your mobile applications be accessible.
  
  
 

  
  
  
  
  
  • 
    Oklahoma State Mobile Apps:
    
  
  
  
  
  

  
  
  
  Day 15 of the Mobile Accessibility Advent Calendar!
  

  
  
  

  The daily conversation I have with folks in the mobile space is one of two questions:

  
  
  
  
  
  1. "Where are the standards for mobile accessibility!?!?!" 
  
  
  2. "Does WCAG actually apply to mobile??"
  
  
  
  
  

   
  
  The answer in short, WCAG does apply to mobile applications. Yes, before anyone gets up in arms and says the word "web" is literally in the title that doesn't make sense, it will. The principals that WCAG is built on are easily transferable to mobile applications.

  
  
  

  Does every little thing within WCAG apply? Not necessarily. Are there resources and guidance in WCAG that are web based and can make it difficult to translate it into what is needed for mobile? Sure!

However if you are looking for a starting set of resources to help guide you in the right direction for guidelines there are a couple really good ones!



  
  
  
  
  
  • 
    BBC Mobile Standards:
    
    
  
  
  
  
  

  There are also some mobile specific standards (built on principal of WCAG but their own guidelines):
  
   
  
  Evinced Mobile Standards (MCAG):
   



• Voice Control - Allows users to use voice to control iOS device. One of the common testing methodologies I suggest with this is saying "show numbers" and ensuring all the actionable items on the screen are accounted for AND function.
  More on Voice Control
   


• Keyboard - Yes, you read this correctly. No it isn't an assistive technology per say, however keyboard users exist in iOS. To say that they don't would be a mistake, testing your application with keyboard and Voice Over on (and off) will ensure that multiple inputs can work with it.
  
 


Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
↗ Original-Artikel auf dev.to lesen