Re: Query regarding 1.3.4

Hi Kevin,

> It doesn't fail the failure criteria of 1.3.4 because it allows changes
in orientation

Respectfully, it *IS* a failure of SC 1.3.4, because according to
Ramakrishnan, there *IS* "... *loss of content or functionality*" (their
actual words). The SC does not speak to *how *that may happen (opening the
page in either view, or when the view changes due to device rotation), only
that the content MUST render and function correctly in both views. Again,
the normative text clearly states:

"*Content does not restrict its view and operation to a single display
orientation*, such as portrait or landscape, unless a specific display
orientation is essential."
https://www.w3.org/TR/WCAG21/#orientation


SC 1.3.4 is NOT about change of orientation, it is about ensuring content
works in both views.

As others have noted, a tablet could be physically locked into landscape
mode (because it is mounted on a motorized scooter for example), but if
page content is 'locked' into only rendering in Portrait mode, it fails.

JF

On Tue, Nov 8, 2022 at 4:28 PM Kevin Prince <kevin.prince@fostermoore.com>
wrote:

> Strictly speaking it's a bug that needs fixing for all. It doesn't fail
> the failure criteria of 1.3.4 because it allows changes in orientation - it
> just handles them badly.
>
> Kevin
>
> *Kevin Prince *
> Product Accessibility & Usability Consultant
>
> *Foster Moore*
> A Teranet Company
>
> *E* kevin.prince@fostermoore.com
> Christchurch
> *fostermoore.com <http://www.fostermoore.com/>*
> -----Original Message-----
> From: Ramakrishnan Subramanian <ram.eict2013@gmail.com>
> Sent: Wednesday, 9 November 2022 5:06 am
> To: w3c-wai-ig@w3.org
> Subject: Query regarding 1.3.4
>
> CAUTION: This email originated from outside of the organization.
>
>
> Dear Members,
> I would like to know whether loss of content or functionality that happens
> when the device orientation is changed would be A Failure of Success
> criteria 1.3.4? or is it a best practice?
> Some Examples of loss of content /functionality that I refer during the
> change of orientation may include content truncation / overlapping / unable
> to scroll etc.
>
>
> --
>
> Thanks and Regards
> Ramakrishnan
>
>

-- 
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"