Re: Query regarding 1.3.4

>  By definition orientation is subject to change, and so it seems pretty
clear the intention is content works in either orientation, including after
a change in orientation.

+1, that *IS* the intent.

JF

On Tue, Nov 8, 2022 at 11:19 AM Bristow, Alan <Alan.Bristow@elections.ca>
wrote:

> It seems like a hard fail of:
>
> Content does not restrict its view and operation to a single display
> orientation, such as portrait or landscape...
>
> https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/#134-orientation-aa
>
> While the content may work perfectly in both and only fail when
> transitioning from one to the other, I see nothing that indicates working
> in the initial orientation is all that is needed. By definition orientation
> is subject to change, and so it seems pretty clear the intention is content
> works in either orientation, including after a change in orientation.
>
> Regards,
>
> Alan
> . . . . -   . . - - -
> Alan Bristow ( he / him / il )
> Web Developer / Développeur Web
> Elections Canada / Élections Canada
> alan.bristow@elections.ca
>
>
> ________________________________________
> From: Ramakrishnan Subramanian <ram.eict2013@gmail.com>
> Sent: Tuesday, November 8, 2022 11:05 AM
> To: w3c-wai-ig@w3.org
> Subject: Query regarding 1.3.4
>
> 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"