CSS Media queries are not used to lock display orientation

Rule ID: css-orientation-lock
Ruleset: axe-core 3.3
User Impact: Serious
WCAG: 1.3.4

What if your accessibility tools could do more?

Axe can catch a lot of accessibility issues, but what if accessibility tools could do more? Join our beta program for a new tool that takes an exciting new approach to accessibility testing.

Compliance Data & Impact

User Impact

Disabilities Affected

  • Attention Deficit
  • Dyslexia
  • Sighted Keyboard Users
  • Low Vision
  • Mobility/Dexterity
  • Cognitive

Requirement(s)

  • Note: Experimental rule
  • WCAG 2.0 (AA): SHOULD

WCAG Success Criteria

  • 1.3.4 Orientation

Section 508 Guidelines

  • Not specified or not applicable

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

Refer to the complete list of axe 3.3 rules.

Was this information helpful?

You have already given your feedback, thank you.

Your response was as follows:

Was this information helpful ?
Date/ Time feedback was submitted :