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.

Małgorzata Szymczak
Accessibility Specialist & Junior Frontend Developer
Recommended articles
-
13.09.2024WCAG Academy
WCAG criterion: 4.1.1 – Parsing (Level A)
What’s it about? Sounds complicated, right? Let’s start by explaining what parsing is. And no, it’s not *pressing* like ironing…
-
07.05.2023Accessibility
Book Review of Anna Goc’s “Głusza”
Anna Goc’s book “Głusza” is a poignant reportage that sensitively portrays the lives of Deaf individuals. The author not only…
-
15.02.2024Blind perspective
Blind perspective: Walking into the unknown
Today, I would like to talk a bit about the issue of spatial orientation. Right away, I’ll mention that my…