WCAG 3.0 is an active W3C Working Draft in development by the AGWG. Requirements, assertions, the conformance model and reporting tiers are still being developed and may change. The latest published draft is the 10 September 2026 Working Draft; this site follows the editors’ draft, which also includes exploratory provisions.
Where a platform has a default orientation, content supports it; where the platform has none, content supports both portrait and landscape. The same exemptions apply.
Why It Matters
Locking orientation overrides a physical setup the user cannot change, which is why this is a baseline rather than an enhancement.
Check that the orientation aligns with the platform default.
For platforms which do not have a default orientation:
Open the content.
Check that the orientation can align with both portrait and landscape orientations.
Expected results
#2 is true.
W3C Working Group Status
W3C Maturity Status:developing
Track / Group:user-control
The draft records no open editors' notes on this provision.
W3C Threads on This Provision
No GitHub issue in w3c/wcag3 carries this provision's label, so there
is no recorded discussion to show. Cross-cutting threads that name no
provision are listed on the
Discussions page.
WCAG 2.2 Criteria That Map Here
From this site's reviewed WCAG 2.2 → WCAG 3 map. The map is
an interpretation, not a W3C mapping: W3C has not published one yet.
If the platform has a default orientation, content supports that orientation. If the platform does not have a default orientation, content supports both portrait and landscape orientations.
:::except-when
* Content is aligned with the physical world.
* The orientation is essential.
:::
:::note
For extended reality, the platform default orientation aligns with the real world orientation.
:::
:::note
Content does not have to re-layout or change aspect ratio in a different orientation, it just needs to display in the device orientation.
:::