Orientation: Support Portrait and Landscape
Also called: Screen orientation, Portrait and landscape mode, Orientation lock
Definition
Orientation is WCAG success criterion 1.3.4: content must not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific orientation is essential.
Orientation in WCAG means that a website works in both portrait and landscape mode. When a page locks itself to one screen orientation – or hides its content behind a "Please rotate your device" message – people who cannot turn their phone or tablet are shut out. The fix is usually simple: let the layout adapt instead of forcing a direction.
What it means
WCAG 1.3.4 Orientation is a Level AA criterion, added in WCAG 2.1 and part of WCAG 2.2. Content must not restrict its view and operation to a single display orientation unless a specific orientation is essential. "Essential" means that without it the information or functionality would fundamentally change and cannot be achieved in another conforming way.
| Situation | Allowed to lock orientation? |
|---|---|
| Online shop, blog, news site, web app | No – must work in portrait and landscape |
| Video player, messaging, e-reader | No – W3C's examples show both orientations |
| Banking app capturing a check image in landscape | Yes – a check is about twice as wide as it is tall |
| Piano app keeping keys usable in landscape | Yes – the keys need their proportions |
| Content for a television or VR goggles | Yes – the display has only one orientation |
Who benefits: people whose device is mounted in a fixed position, for example on a power wheelchair, cannot rotate it. People with motor impairments may find it hard to turn a device. People with low vision may prefer landscape because it gives larger text. W3C also notes that layout changes based on screen size are outside this criterion – only restricting the orientation counts.
Examples
<!-- Fails (F100): content hidden in portrait, only a message is shown -->
<style>
@media (orientation: portrait) {
main { display: none; }
.rotate-hint { display: block; }
}
</style>
<!-- Passes: the layout adapts, nothing is hidden -->
<style>
.gallery { display: grid; grid-template-columns: repeat(auto-fit, minmax(160px, 1fr)); }
@media (orientation: landscape) {
.gallery { gap: 2rem; }
}
</style>Using @media (orientation: …) is fine for adjusting a layout. It becomes a failure only when it is used to block content or functions. The same applies to scripts that lock the orientation with the Screen Orientation API – W3C lists locking the view as failure F97.
Let every page work in portrait and landscape, use orientation media queries only to fine-tune the layout, keep controls large enough in both modes, and lock the orientation only when it is really essential.
Show a "rotate your device" screen instead of the content, hide the menu or checkout in one orientation, lock a whole web app to portrait, or call an orientation "essential" when it is just the preferred design.
How to check orientation
Questions
Does my website have to work in landscape mode?
Yes, unless a specific orientation is essential to the content. Under WCAG 1.3.4 a website must not restrict its view and operation to portrait or landscape. Most websites have no essential reason, so they must support both.
Is a "please rotate your device" message allowed?
Not if it replaces the content. W3C lists showing a message that asks users to reorient their device as failure F100. A short hint is fine as long as the page still works in the current orientation.
Can I use CSS orientation media queries?
Yes. Changing the layout for portrait or landscape is allowed and often helpful. Only using them to hide content or block functions fails the criterion.
Which laws require screen orientation support?
WCAG 1.3.4 is Level AA, the level referenced by EN 301 549 and therefore by the European Accessibility Act in the EU.
How do I test orientation without a phone?
Use your browser's DevTools device mode and switch between portrait and landscape. Real devices are still worth a final check. For code-level problems on many pages, the free WCAG scanner gives a quick overview.
Related terms
Reflow: Content That Fits at 400% Zoom
Reflow is WCAG success criterion 1.4.10. Content must work without loss of information or functionality and without scrolling in two directions at a width equal to 320 CSS pixels – or a height of 256 CSS pixels for horizontally scrolling content.
Read definition: Reflow: Content That Fits at 400% ZoomResize Text: Readable and Usable at 200%
Resize Text is WCAG success criterion 1.4.4. Except for captions and images of text, text must be resizable up to 200 percent without assistive technology and without loss of content or functionality.
Read definition: Resize Text: Readable and Usable at 200%Target Size: 24 × 24 px for Every Click Target
Target Size (Minimum) is WCAG success criterion 2.5.8. The size of the target for pointer inputs is at least 24 by 24 CSS pixels, unless spacing, an equivalent control, inline text, the user agent or an essential presentation makes an exception.
Read definition: Target Size: 24 × 24 px for Every Click Target