WCAG 2.1 · Level AA · Perceivable
1.3.4 Orientation
Manual verification
How to validate 1.3.4 by hand
Check that content is not locked to portrait or landscape orientation unless a specific orientation is essential.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Open the page on a device or emulator in portrait orientation and complete the primary task.
- Rotate to landscape and repeat, then rotate back; check whether content and functionality remain available.
- If one orientation is blocked, determine whether that orientation is essential to the activity or required by the device.
Evidence to record
Record device viewport/orientation, the blocked or lost content/function, and why the constrained orientation is or is not essential.
Scope and exceptions
Some activities inherently require a particular orientation. A layout preference or branding choice alone is not evidence that orientation is essential.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.