WCAG Guideline 1.3.4: Orientation Explained
Estimated read time: 8–10 minutes
Guideline 1: Perceivable
The first principle of WCAG, Perceivable, ensures that information and user interface components must be presented to users in ways they can perceive. This means content can’t be invisible to all of a user’s senses—whether they are seeing, hearing, or feeling the content through assistive technology.
Guideline 1.3: Adaptable
Guideline 1.3 focuses on creating content that can be presented in different ways (for example, simpler layout) without losing information or structure. This is essential for users who rely on assistive technologies or need content in alternative formats.
What Is Guideline 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."
Guideline 1.3.4 is a Level AA requirement in the Web Content Accessibility Guidelines (WCAG) .
- Users must be able to view and operate content in both portrait and landscape orientations.
- Don’t lock your site or app to a single orientation unless it’s essential (e.g., a piano app).
- Ensure all functionality and information is available in both orientations.
This ensures that users who use assistive technology, have their device mounted, or prefer a certain orientation can still access your content.
Why Does It Matter?
- Inclusivity: Some users can’t rotate their devices or use assistive tech that requires a specific orientation.
- Legal Compliance: Orientation is a Level AA requirement in WCAG 2.2 and referenced in accessibility laws worldwide.
- Usability: Supporting both orientations improves the experience for all users, especially on mobile.
For more, see WebAIM's orientation guide .
What Needs Orientation Support?
- Mobile apps and web pages
- Forms and interactive content
- Media players and games
- Any content that could be used in different orientations
All such content should be usable in both portrait and landscape unless a specific orientation is essential.
How to Support Multiple Orientations
- Use responsive design techniques to support both orientations
- Avoid CSS or JavaScript that locks orientation
- Test all features in both portrait and landscape
- Only restrict orientation if absolutely necessary
For more, see the MDN orientation docs .
Common Mistakes to Avoid
- Locking content to portrait or landscape without a valid reason
- Features that break or disappear in one orientation
- Not testing with assistive technology or mounted devices
- Ignoring user preferences for orientation
Audit your site regularly and use accessibility checkers to ensure all content supports multiple orientations. For more, see the BBC's Mobile Accessibility Guidelines .
Differences Between A, AA, and AAA for Guideline 1.3.4 in WCAG 2.2
- Level A: No requirement for 1.3.4.
- Level AA: Requires content to support both portrait and landscape orientations unless essential. This is the core requirement for 1.3.4 and is mandatory for AA conformance.
- Level AAA: For Guideline 1.3.4, there are no additional requirements beyond Level AA in WCAG 2.2. Meeting Level AA for this guideline also satisfies Level AAA.
For more, see the W3C’s official documentation for 1.3.4 Orientation .
Quick Checklist
- Content works in both portrait and landscape
- No features break in either orientation
- No orientation is locked unless essential
- Tested with assistive technology and mounted devices
- User preferences for orientation are respected
Summary
Guideline 1.3.4 is essential for making your site usable and accessible for everyone. By supporting both orientations, you support users with disabilities, improve usability, and meet legal requirements. Make orientation flexibility a standard part of your development process.