Perspective

I can use it, but only in one orientation

Content or functionality is unnecessarily restricted to portrait or landscape orientation.

How someone positions a device is not always a preference.

What happens

An app or page forces portrait or landscape even though the content does not inherently require that orientation.

Why it matters

A device may be mounted to a wheelchair, stand or other fixed setup. Rotating it may be difficult or impossible.

How to test it

On supported mobile/tablet experiences, rotate between portrait and landscape and verify content and functionality remain available. Check whether any restriction is genuinely essential to the activity.

Can automation detect it?

Limited. Static inspection may reveal orientation locks, but rendered/device testing is needed to understand actual behaviour and exceptions.

Relevant WCAG

This commonly relates to 1.3.4 Orientation.

What a pass does not prove

Supporting both orientations does not prove the layout reflows well, text scaling works, or controls remain comfortably operable.