CSS Media queries are not used to lock display orientation
Start building more accessible experiences
Compliance Data & Impact
Disabilities Affected
- Attention Deficit
- Dyslexia
- Sighted Keyboard Users
- Low Vision
- Mobility
- Cognitive
Standard(s)
- WCAG 2.1 (AA)
- WCAG 2.1 Experimental
WCAG Success Criteria [WCAG 2.1 (AA)]
- 1.3.4: SHOULD: Orientation
WCAG Success Criteria [WCAG 2.1 Experimental]
- 1.3.4: MUST: Orientation
How to Fix the Problem
Do not use CSS or other techniques to lock device orientation. Test content orientation views to ensure that content continues to be accessible to all users, including assistive technology users, in any orientation.
Why it Matters
Assistive technology users may be unable to access orientation features with their devices or assistive technologies.
Rule Description
The screen orientation (e.g. portrait or landscape) of mobile applications should not be locked in one mode. Users should be able to change the orientation of their device between portrait and landscape with the page adjusting accordingly in order to remain understandable. Also, when opening a page, it should display in the user’s current orientation.
The Algorithm (in simple terms)
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.
Resources
Deque University Course Pages (subscription required)
No related course information available.
Refer to the complete list of axe 3.5 rules.
Was this information helpful?
Your response was as follows:
Date/Time feedback was submitted: