- Success Criterion 1.3.4
- Conformance level AA
App Manifest Locking Orientation for Ordinary, General Content
1.3.4 — Orientation
Scenario
Setting
A podcast app's episode list
What’s wrong
PWA manifest "orientation": "portrait" for general content.
Example
Try this on a podcast app's episode list: PWA manifest "orientation": "portrait" for general content.
Why it matters
People whose devices are mounted or who cannot rotate a display freely. The practical effect on a podcast app's episode list: they can't perceive the control's boundary or state.
How to test
Check the web app manifest.json for an "orientation" key locked to portrait or landscape for general content: this fails unless the content is orientation-essential.
How to fix
The page/app must remain fully usable in both portrait and landscape, with the layout intact after rotation.
Outcome
That one change on a podcast app's episode list means they read the text clearly against its background.
Who is affected
People whose devices are mounted or who cannot rotate a display freely.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- App Locked Into One Screen Orientation With No Real Reason
- Page That Just Asks Users to Rotate Their Device to Continue
- Screen Orientation Locked in Code With No Essential Justification
- CSS That Hides or Breaks Content in One Orientation Only
- Critical Controls Cropped or Unusable in One Orientation
- Video Player Forcing Landscape Fullscreen for Ordinary Content