2 minute read

WCAG 1.3.4: Orientation (Level AA)

Ever tried to use an app on your phone, only to find that it forces you into landscape mode?

It’s frustrating when you can’t rotate the screen to suit your needs. Orientation ensures that web content works in whichever way the user prefers—whether that’s portrait or landscape—so the experience is always accessible.

Who this impacts

  • People with mobility impairments: Some users may not be able to rotate their device or find certain orientations easier to use.
  • People using assistive technology: Screen readers and other tools may work better in specific orientations.
  • People with visual impairments: Depending on their device settings, some users may need a particular orientation for readability.
  • Everyone: Allowing content to be used in multiple orientations provides more flexibility and convenience.

How to meet Orientation

  1. Support both portrait and landscape: Ensure that your content adapts to different orientations without loss of functionality.
  2. Avoid locking orientation: Don’t force users into a single orientation unless absolutely necessary for a specific task.
  3. Test across devices: Make sure the content adapts well to different orientations and screen sizes.

Top Tips

  • Optimize for flexibility: Design interfaces that adapt seamlessly to different orientations.
  • Account for edge cases: Test with different devices and screen sizes to catch any potential issues with orientation changes.
  • Check for hidden content: Make sure elements aren’t cut off or misplaced when switching orientations.
  • Consider exceptions carefully: Only lock orientation if it’s essential to the task (e.g., a mobile game that relies on landscape mode).

Further reading

Previous articleNext article
Back to top