Goal
Allow content to be viewed in any orientation (portrait or landscape) without losing functionality.
Success Criterion · WCAG 1.3.4
Orientation
Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
Level AAWCAG 2.1Perceivable1.3 · Adaptable
Copy button ready
What to do
Do not lock content to a single display orientation unless a specific orientation is essential.
Why it matters
Users with mounted devices or mobility impairments may be unable to rotate their screens.
Success criterion
What WCAG 1.3.4 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
Intent
Why WCAG created this requirement
- Users with mounted devices cannot rotate to a different orientation.
- Users with motor impairments may have difficulty physically rotating devices.
- Content should adapt to both portrait and landscape orientations.
- Orientation locks should only be used when essential to core functionality.
Benefits
Who gains when you pass
- Users with wheelchair-mounted tablets can access content without unmounting their device.
- Users with devices on bed mounts or stands can use their preferred orientation.
- Users with motor impairments who cannot easily rotate devices maintain access.
- Users in various physical positions can view content comfortably.
- Content works regardless of device default orientation settings.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users with mounted devices may be completely unable to use orientation-locked content.
Users with motor impairments may struggle to rotate devices to the required orientation.
Content becomes inaccessible in the "wrong" orientation even when the user cannot change it.
Users may need to unmount assistive device setups to use orientation-locked applications.
Exception guidelines
Use the WCAG 1.3.4 exceptions correctly
Document the rationale for each exception and note which alternative support you provide.
Essential orientation
Content may be locked to a specific orientation when that orientation is essential to its functionality.
Requirement
The orientation must be genuinely essential—a piano keyboard that needs width, a check deposit matching physical check dimensions, etc. User preference is not essential.
Overview
Content must be viewable and operable in both portrait and landscape orientations. Some users have devices mounted in a fixed position (wheelchair mounts, bed mounts) or have mobility impairments that prevent them from rotating their device. Locking content to one orientation can make it completely inaccessible to these users. Only restrict orientation when it is essential to the functionality (like a piano keyboard app that requires landscape).
- Test your content in both portrait and landscape to ensure it remains functional.
- Do not use CSS or JavaScript to lock orientation unless essential.
- Essential orientation: a piano app that simulates a keyboard layout, or a check deposit that needs to match check dimensions.
- Most content, including videos, does not require a locked orientation—users can choose to rotate if desired.
- Responsive design naturally supports both orientations.
Reference: All summaries and highlights originate from Understanding WCAG 1.3.4 and the W3C quick reference.
Fast facts
- Conformance level
- Level AA
- WCAG version introduced
- WCAG 2.1
- Principle
- Perceivable
- Guideline
- 1.3 · Adaptable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Form page
Pass
A multi-field form displays properly in both portrait (single column) and landscape (two columns) without losing any fields.
Fail
A form locks to portrait orientation, making it unusable for a user with a landscape-mounted tablet.
Video player
Pass
A video player works in both orientations; users can choose to rotate to landscape for a larger view if they prefer.
Fail
A video player forces landscape orientation, making it inaccessible on mounted devices that cannot rotate.
Piano app (essential)
Pass
A piano keyboard app that simulates a full keyboard requires landscape orientation—this is essential to its function.
Fail
N/A—when orientation is truly essential, locking is acceptable.
News article
Pass
A news article reflows text appropriately in both orientations with comfortable reading width.
Fail
A news site locks to portrait orientation "for better reading" even though this is not essential.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document any content that requires a specific orientation with justification.
- Include orientation testing in QA checklists.
- Note responsive breakpoints and how they handle orientation changes.
- Track any orientation-related user complaints or issues.
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Understanding 1.3.4
Official W3C interpretation, techniques, and intent for Orientation.
Quick Reference 1.3.4
Filterable list of sufficient techniques and failures.
Failure F97
Failure due to locking the orientation to landscape or portrait view.
Technique G214
Using a control to allow access to content in different orientations which is otherwise restricted.
MDN: Screen Orientation API
Documentation on the Screen Orientation API and its proper use.
Implementation checklist
Capture progress and blockers
- Test all content in both portrait and landscape orientations.
- Remove any CSS or JavaScript that locks screen orientation unless essential.
- Use responsive design techniques that adapt layout to available viewport dimensions.
- Verify all functionality is available in both orientations.
- Document any orientation locks with justification for why they are essential.
- Test on actual mobile devices, not just browser resizing.
- Ensure media (videos, images) adapts appropriately to orientation changes.
Testing ideas
Prove conformance with evidence
- Rotate the device or emulator between portrait and landscape.
- Verify content displays appropriately in both orientations.
- Check that all functionality remains accessible in both orientations.
- Test that no content is cut off or hidden in either orientation.
- Verify no orientation lock is triggered unless essential.
- If orientation is locked, verify the lock is truly essential to functionality.
- Test on multiple devices with different default orientations.
Related success criteria