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
-
07.08.2024AccessibilityHow to Audit and Create a Digital Accessibility Audit Report. Part One
In our blog, we describe all the criteria from WCAG 2.2. You might be wondering how we can use these…
-
22.04.2024AccessibilityThere is no sustainability without accessibility… and vice versa
Accessibility and sustainability go hand in hand with digital products. Our digital products benefit the environment and society when we…
-
28.06.2022AccessibilityAlternative Text for Images
Imagine this situation: all your web browsers suddenly stop working and do not display any images. On the websites, only…