Query on WCAG SC 1.3.4: Orientation and Content Loss #4565
Replies: 2 comments 2 replies
-
While not explicit, to me "Content does not restrict its view and operation to a single display orientation" would also mean that if particular content/functionality is only available in one orientation, then it fails here. Because effectively, that content/functionality IS restricted to just a particular orientation. Of course, there's nuance here, because sometimes in a different orientation, content may not appear directly in the same place/on the same page, but instead be moved to a sub-page, a separate modal dialog or panel, or similar - similar to responsive layouts where sometimes content isn't just laid out differently, but more fundamentally reorganised to better serve that particular viewport size/orientation. |
Beta Was this translation helpful? Give feedback.
-
My recollection is that the SC text stopped short of saying all content and functionality were available like SC 1.4.4 does and only focused on the content not restricting the view. So, the criterion does seem to allow for situations where some functionality might not be available even if that is an issue for users. "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." |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a query regarding WCAG SC 1.3.4 (Orientation). When we change the orientation from portrait to landscape or from landscape to portrait, some informative content gets lost.
In this case, should we raise the issue under SC 1.3.4, or does this success criterion only cover the ability to switch orientation, regardless of whether content is lost?
Beta Was this translation helpful? Give feedback.
All reactions