Re: Multiple ways for apps

On 04/09/2019 12:37, Michelle Parfitt wrote:
> Hi everyone,
> 
> I was wondering if anyone had any advice/good examples of mobile apps 
> which followed the WCAG guideline 2.4.5 Multiple Ways? I've found a few 
> information heavy apps that do this well by having a menu and also a 
> search bar (for example for news outlets), however, for apps such as 
> Instagram, the search function is not used to navigate around the app 
> (just find new content) and the only way to navigate  to all areas of 
> the app is via the tray at the bottom (which seems to be quite common 
> e.g. is also the case on the Easyjet app). This provides one way of 
> navigation. I assume this means it fails and Instagram and other apps 
> like it would need to add another way of navigating. Has anyone seen new 
> innovative ways of providing more than one way to navigate apps other 
> than provide a search function?

I'll be honest, for apps like instagram etc I contend it wouldn't even 
make sense to have multiple ways, I generally count that as not applicable.

Arguably, also, on small sites where each page is linked from a standard 
header on all pages, I pass these as each page can then be reached from 
each other page, so multiple ways are, in my estimation, satisfied. 
Similarly, if an app has the same navigation mechanisms always clearly 
present on each page, I'd argue then that again each screen/view can be 
reached from any other one, so multiple ways is satisfied.

The core idea behind multiple ways is that there aren't specific pages 
that the user can ONLY ever reach from one other specific place (so if 
they don't remember that, they'd be left wondering "how did i reach that 
again?")

P
-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke

Received on Tuesday, 17 September 2019 15:22:54 UTC