# Orientation Accessibility

Orientation accessibility allows people to use content in portrait or landscape without an unnecessary author-imposed restriction.

- Type: principle
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-10-19
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/orientation-accessibility/>)

## What it means

Orientation accessibility means that content does not require a particular display orientation unless that orientation is essential. WCAG 2.2 criterion 1.3.4 addresses this at Level AA. A user’s device-orientation preference differs from an application forcing a layout or blocking access until the device is rotated.

## Why it matters

Some people use mounted devices or cannot physically rotate them. Requiring a preferred orientation can therefore prevent access altogether, even when the screen could accommodate an alternative layout.

## When to use it

Apply it to mobile and tablet workflows, embedded experiences, and responsive web interfaces. Treat an essential-orientation exception narrowly; a designer’s preference or an easier implementation is not enough. Adapt presentation while preserving the task.

## How it works

1. Identify orientation locks, forced rotation prompts, and orientation-specific overlays.
2. Determine whether any restriction is truly essential to the activity.
3. Support usable layouts and controls in both orientations where it is not.
4. Test startup, rotation, forms, dialogs, and media in each orientation.
5. Check that transitions preserve entered data and the user’s place.

## A practical example

A field-service form initially blocks landscape with a “rotate your device” overlay. A worker’s mounted tablet cannot be turned. The team removes the block and adapts the form layout so the task remains available in either orientation.

## Where it breaks

Supporting both orientations does not guarantee reflow, adequate touch targets, or good use of space. Some activities genuinely depend on a specific orientation, but that exception needs a concrete functional reason. Device and browser behavior also require testing.

## Common mistakes

- Treating aesthetic preference as an essential restriction.
- Checking the landing screen but not later dialogs.
- Rotating the visual interface with CSS instead of supporting the available orientation.

## Sources

1. [Understanding Success Criterion 1.3.4: Orientation](<https://www.w3.org/WAI/WCAG22/Understanding/orientation.html>) — W3C Web Accessibility Initiative · Standards guidance
2. [F97: Failure due to locking the orientation to landscape or portrait view](<https://www.w3.org/WAI/WCAG22/Techniques/failures/F97>) — W3C Web Accessibility Initiative · Standards technique

## Related topics

- [Responsive Design](<https://wiki.soroush.uk/topic/responsive-design/>)
- [Reflow and Zoom](<https://wiki.soroush.uk/topic/reflow-and-zoom/>)
- [Inclusive Design](<https://wiki.soroush.uk/topic/inclusive-design/>)
