WCAG 2.1 – Criterion 1.3.4 – Orientation (Level AA)
Article content
Today, we present to you WCAG criterion 1.3.4 (Level AA) regarding orientation.
In simplest terms, content and functions cannot be restricted to displaying in just one orientation – horizontal or vertical. The user must be able to decide how they interact with a given website or application.
The aim of this success criterion is to ensure that developers do not limit the use of a mobile application or website to a specific mode.
Individuals who may potentially have difficulty rotating a mobile device to a horizontal position should not be restricted in accessing content. For example, people who have a phone attached to the handle of an electric wheelchair.
Are there exceptions? Yes.
Content that somewhat forces a particular orientation due to its format.
W3C – World Wide Web Consortium – provides simulations of pianos as an example. Handling the application in a vertical orientation would be ineffective, and the keys might be too small.
Piotr Źrołka
Accessibility expert & CEO
Recommended articles
-
27.09.2024Blind perspectiveBlind Perspective: Ask the Chat
Artificial intelligence—who hasn’t heard of it? Today, you can encounter it practically everywhere. In a few previous articles, I’ve already…
-
20.09.2024WCAG AcademyWCAG Criterion 4.1.2 – Name, Role, Value (Level A) part 1
Good morning on this Friday! As we start the weekend, we have a post for you about WCAG. Today, we’re…
-
12.07.2024AccessibilityWCAG 2.1 – Criterion 3.3.2 – Labels and Instructions (Level A)
Hints… Do they have any connection to WCAG? Yes, indeed. Labels and hints (or instructions) are described by the WCAG…