Published November 9, 2026
WCAG 1.3.4 Orientation, Level AA
Does WCAG ban portrait-only or landscape-only pages?
Yes at Level AA, unless a specific orientation is essential. Success criterion 1.3.4 Orientation requires that content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless that orientation is essential. The text is in the W3C WCAG 2.2 Recommendation.
What does orientation require?
The page must remain usable when the device is rotated. A person who mounts a tablet in a fixed cradle, or who cannot rotate a phone, must still reach the same content and controls. The W3C explanation is in Understanding Success Criterion 1.3.4. Responsive layouts that adapt to both orientations are the usual way to meet it. Which version added 1.3.4 is on the WCAG 2.1 vs 2.2 page.
When is a single orientation essential?
Only when the content would lose meaning or function in the other orientation. Understanding lists cases such as a piano app that needs keys side by side, a check deposit view that matches a landscape paper form, or a slide deck meant for a landscape projector. Brand preference, “it looks better,” or a designer’s mockup is not essential. When the exception does not apply, remove orientation locks in CSS, meta tags, and platform APIs.
How does orientation relate to reflow and resize?
1.3.4 is about allowing both orientations. It does not replace 1.4.10 Reflow, which checks a 320 CSS pixel width without two-direction scrolling, covered on the reflow page. It also does not replace 1.4.4 Resize Text at 200%, covered on the resize text page, or 1.4.12 Text Spacing, covered on the text spacing page. A page can unlock rotation and still fail those layout checks.
Does the Title II web rule include orientation?
Yes. The Department of Justice rule for state and local government websites names WCAG 2.1 Level AA. That level includes 1.3.4. Governments with a population of 50,000 or more have until April 26, 2027. Smaller governments and special districts have until April 26, 2028. Who must comply is on the Title II web rule page. A scanner may miss an orientation lock that only appears on a device. A person checks that, which is why a passing score is not conformance, as covered on the scanner page. The fix belongs in the templates and app settings, which is remediation.
Questions and answers
Does WCAG ban portrait-only or landscape-only pages?
Yes at Level AA, unless a specific orientation is essential. Success criterion 1.3.4 Orientation requires that content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless that orientation is essential. Specification: https://www.w3.org/TR/WCAG22/#orientation
What counts as an essential orientation?
Examples in Understanding include a piano app that needs landscape keys side by side, a bank check that must be landscape to match the paper form, or a projector slide that is landscape only. A marketing page locked to portrait for design preference is not essential. Explanation: https://www.w3.org/WAI/WCAG22/Understanding/orientation.html
Does locking orientation with CSS or a meta tag fail?
Yes when the page cannot be used after the device is rotated. Techniques that force one orientation with CSS transforms, viewport meta, or an API message that blocks the other orientation fail unless the exception applies. Reflow at a narrow width is a separate check: https://www.adasupport.org/reflow
Does the Title II web rule include orientation?
Yes. The DOJ rule names WCAG 2.1 Level AA, which includes 1.3.4. Governments of 50,000 or more have until April 26, 2027. Smaller governments and special districts have until April 26, 2028. Deadlines: https://www.adasupport.org/title-ii-web-rule
Related guides
Ask for a review of a specific page
Send the URL and the template you care about. The reply names the highest-risk WCAG failures and the order to fix them.
Request an audit