Level AAPerceivableNew in 2.1
1.3.4

Orientation

Don't lock your store to portrait or landscape only, it must work whichever way the device is held.

In plain English

Some people keep their phone or tablet fixed in one orientation, mounted on a wheelchair, a stand, or an assistive rig, and cannot just turn it. If your store forces portrait (or forces landscape), those people are stuck. This rule says: work in both orientations. Do not lock it, unless a specific orientation is truly essential (which, for a store, it is not).

Who this is for

  • People who use a mounted device, on a wheelchair or a stand, where rotating is not an option.
  • Anyone, who expects a site to adapt when they turn their phone.

How to check and fix it yourself

On a phone, rotate between portrait and landscape on your key pages. Everything should reflow and stay usable. The usual cause of failure is a CSS or meta setting that pins orientation, remove it and let your responsive layout do its job.

Rotate to landscape on a product page → layout adapts, still usable.  ✓
Site shows "please rotate your device" and blocks landscape.          ✗

Where we can help

Orientation locking is rare but easy to ship by accident (often via a theme setting or an app). We test both orientations across your templates and flag any that break. It is one of the checks in our WCAG 2.2 overview.

Frequently asked questions

What does orientation require?+

Success Criterion 1.3.4 (Level AA, added in WCAG 2.1) says content must not be restricted to a single display orientation, portrait or landscape, unless a specific orientation is essential. The store should work whichever way someone holds their device.

Why does locking orientation cause problems?+

Many people have their device mounted in a fixed position, on a wheelchair, a stand, or a desk, and cannot easily rotate it. If your site only works in portrait, someone whose phone is fixed in landscape is locked out.

When is a fixed orientation allowed?+

Only when it is essential, for example a piano-playing app or a cheque-scanning view that genuinely requires one orientation. A normal store has no such need, so it should support both.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 1.3.4?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit