RE: Principle 4 - Robust (was Re: Help needed with numbering success criteria for WCAG 2.1)

Patrick,

I don’t quite understand the difference between what you say:

 “It's not about how a site/app reacts when orientation/viewport is changed, but rather that 
 it actually works in those orientations/changes.”

So, if a site works in landscape but is rotated to portrait and it now introduces a different menu structure let’s say with hamburger menus but they add more menu options in portrait than they had in landscape.

Is this “how it works” or “if it works”.

Alan

Alan Smith, CSTE, CQA

Sent from Mail for Windows 10

From: Patrick H. Lauke
Sent: Monday, June 27, 2016 4:00 AM
To: w3c-wai-gl@w3.org
Cc: public-mobile-a11y-tf@w3.org
Subject: Re: Principle 4 - Robust (was Re: Help needed with numbering success criteria for WCAG 2.1)

On 27/06/2016 01:57, David MacDonald wrote:
> Hi Patrick
>
> My thinking is that this fits well under perceivable. I'm hoping that we
> will expand Perceivable to
> Guideline 1.5 include dynamic and updating content. It might go well in
> there.
> https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_on_information_added_or_removed_from_a_page

Note that this is NOT about dynamic changes/updates. It's not about how 
a site/app reacts when orientation/viewport is changed, but rather that 
it actually works in those orientations/changes (e.g. if a tablet is 
fixed to landscape orientation and the user accesses a site, NOT about 
the user accessing the site in portrait and then turning the device into 
landscape). So no, that's a separate issue from the one I'm talking about.

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