WCAG 1.3.4 Orientation
Content must not be restricted to only one screen orientation, portrait or landscape, unless a specific orientation is essential, such as a piano or check-scanning app.
Table of contents
What WCAG 1.3.4 Requires
Content must not be restricted to only one screen orientation, portrait or landscape, unless a specific orientation is essential, such as a piano or check-scanning app.
How to Test It by Hand
Rotate a mobile device (or use the browser's device toolbar) and confirm the page works in both orientations.
Common Failures
- A page or app is locked to portrait mode with CSS or JavaScript for no functional reason.
Testing WCAG 1.3.4 With AccessBell
This criterion depends on meaning or context, so it needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it is not missed.
Run a free scan to spot issues on your own pages.
Related Criteria in Adaptable
- 1.3.1 Info and Relationships (Level A, WCAG 2.0)
- 1.3.2 Meaningful Sequence (Level A, WCAG 2.0)
- 1.3.3 Sensory Characteristics (Level A, WCAG 2.0)
- 1.3.5 Identify Input Purpose (Level AA, WCAG 2.1)
- 1.3.6 Identify Purpose (Level AAA, WCAG 2.1)
Frequently Asked Questions
What does WCAG 1.3.4 require?
Content must not be restricted to only one screen orientation, portrait or landscape, unless a specific orientation is essential, such as a piano or check-scanning app.
Can AccessBell test WCAG 1.3.4 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 1.3.4?
Level AA, added in WCAG 2.1. Level AA is the level referenced by the ADA, Section 508 and most accessibility laws.
Sources
- W3C: Understanding 1.3.4 Orientation (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.