• Success Criterion 1.3.4
  • Conformance level AA

1.3.4 · Orientation

Lesson overview · Orientation

In plain language

The site must work in both portrait and landscape unless one orientation is truly essential.

Who it affects

People whose devices are mounted or who cannot rotate a display freely.

How to check

Rotate the device/emulator both ways: everything must remain usable, with no 'please rotate' blocker. Worked example — A photo-sharing app's upload screen: rotate to the 'wrong' orientation and inspect: CSS media queries that hide or break all content in one orientation (e.g., @media(orientation:landscape){display:none}) fail.

Common misconception

Teams assume this only applies to phones. It also covers any device that can be mounted or fixed in place, like a tablet on a wheelchair, where the user genuinely cannot rotate it. Real example: on a real-estate marketplace's listing page, the app locks itself to portrait or landscape — users with a mounted device (e.g., on a wheelchair) can't rotate and can't use it.

Learn more

get in touch

Know where you stand. Know what to work on next.

Tell us what you’re working on and where you need support. Our accessibility specialists can help with audits, remediation, VPAT/ACR, accessible development, and ongoing compliance.

Free 30-minute consultation (opens in new tab)

Free 30-minute call: talk through where you stand, scope a project or get a quote.

Need technical answers now? Book the $100 one-hour consultation to walk through an audit, talk with a developer or review your site live.

Let’s find the barriers before your users do

Indicates a required field.


Your information is kept private and never shared with third parties.

Scenarios in this lesson