Skip to content

SC 1.3.4 Orientation & restrictions of content and functionality #3908

Open
@anevins12

Description

@anevins12

SC:

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/WCAG22/#orientation

What does restricting mean in relation to "view" and "operation" of content?

I get that this SC is intended to have authors respect orientation settings. At the same time, the wording "restrict its view and operation" gives me the impression that content still has to be readable and functional where present.

For example, a paragraph of text respects both portrait and landscape mode and avoids a scenario of text being read sideways. However, the first word of each sentence in the paragraph is cut-off when landscape.

What good is respecting orientation if the content isn't viewable?

Then again, if a paragraph of text is read sideways because orientation is not respected, how does that restrict view? Or if it contained a link, how would that restrict its operation?

In addition, does the below part of the Understanding document mean that the functionality or content can change but that information and functionality is not lost?

Changes in content or functionality due to the size of display are not covered by this criterion which is focused on restrictions of orientation.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions