Perceivable · Level AA · Introduced in WCAG 2.1
WCAG 1.3.4: Orientation
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
Content should work in both portrait and landscape unless a particular orientation is essential to its purpose. Users may have a device mounted in a fixed position and be unable to rotate it.
A practical example
An appointment form displays a “rotate your phone” overlay in landscape. Remove the restriction and let its fields and actions reflow so a person using a wheelchair-mounted phone can finish the booking.
How to check it
- Open representative pages in portrait and landscape, including forms, dialogs and media controls.
- Check for rotation messages, blocked controls, clipped content or application code that forces an orientation.
- Document any claimed essential orientation and explain why the underlying function genuinely requires it.
What can be missed
A designer's preferred composition is not the same as essential orientation. Test the actual app or browser configuration rather than assuming a responsive screenshot proves both orientations work.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.