- From: John Foliot <notifications@github.com>
- Date: Thu, 31 May 2018 06:22:14 -0700
- To: w3c/screen-orientation <screen-orientation@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/screen-orientation/pull/117/review/124801827@github.com>
johnfoliot commented on this pull request. > + </h2> + <p> + The Web Content Accessibility Guidelines 2.1 specification [[WCAG21]] includes a Success Criterion (<a href="https://www.w3.org/TR/WCAG21/#orientation">SC 1.3.4</a>) related to screen orientation. + </p> + + <p> + The intent of this Success Criterion is to ensure that all content and functionality is available regardless of the display + orientation (portrait or landscape). Some websites and applications automatically set the screen to a particular display + orientation and expect that users will respond by rotating their device to match. + </p> + + <p> + However, some users may have their devices mounted in a fixed orientation (e.g. on the arm of a power wheelchair). Therefore, + websites and applications need to support both orientations by making sure content and functionality is available in + each orientation. While the order of content and method of functionality may have differences the content and functionality + must always be available. When a particular orientation is essential, the user needs to be advised of the orientation >> While the order of content and method of functionality may have differences the content and functionality must always be available. > I don't quite understand what this means. It is a recognition that with CSS (i.e. flexbox, media queries) layout and content rendering may change when the orientation changes, however all content and functionality must be preserved. This may seem obvious on the surface, however... :) >> When a particular orientation is essential, the user needs to be advised of the orientation ... > It's a bit preachy... maybe: > When a particular orientation is essential, developers should inform users of the orientation requirement. This is essentially an RFC 2119 MUST requirement. Replacing 'should' with 'must' would be preferred, however it is recognized that this is non-normative text in this Specification, so defer to Editors judgement. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/screen-orientation/pull/117#discussion_r192096432
Received on Thursday, 31 May 2018 13:22:36 UTC