WCAG 1.3.4: Orientation
Level AAQuick answer: Shoppers must be able to use the storefront in portrait or landscape unless one orientation is genuinely essential.
What This Means
On ecommerce sites, Orientation usually shows up in repeating storefront components such as product cards, PDP media, search results, cart drawers, checkout forms, and support content. If the live experience depends on patterns like mobile checkout blocks the page in landscape with a rotate-your-device message. or gift-card balance tools only render in portrait because of rigid viewport rules., disabled shoppers can lose context or get blocked before purchase.
This criterion matters because D2C teams often fix the homepage but miss reusable app blocks, campaign pages, and mobile-specific UI. The practical standard is simple: build the same outcome for keyboard users, screen-reader users, low-vision users, and anyone relying on captions, labels, structure, or predictable behavior.
For Shopify, WooCommerce, and custom storefronts, the fastest remediation path is usually template-level work. Fix the repeated component once, then retest every place it appears across browse, buy, and post-purchase journeys.
Common Violations on Ecommerce Sites
- Mobile checkout blocks the page in landscape with a rotate-your-device message.
- Gift-card balance tools only render in portrait because of rigid viewport rules.
- Product zoom overlays break when a tablet user rotates the screen.
- Account dashboards hide filters in landscape because absolute positioning clips them.
How to Fix It
Start with the live customer journey, not isolated components in Storybook or Figma. Audit the problem on category pages, product detail pages, quick views, cart, checkout, account, and help templates.
- Let content reflow for both orientations instead of locking the viewport.
- Reserve orientation restrictions for truly essential experiences, not convenience.
- Test modals, drawers, and sticky CTAs after rotation on phones and tablets.
- Use responsive containers rather than fixed-height panels that collapse in landscape.
On Shopify, fix the theme section or app block that repeats the defect. On WooCommerce and WordPress, update the template override or plugin output. In custom React or headless storefronts, move the fix into shared components so merchandisers cannot reintroduce the issue with every campaign.
Code Example
<!-- Before -->
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
<!-- After -->
<meta name="viewport" content="width=device-width, initial-scale=1">FAQ
What is WCAG 1.3.4?
Shoppers must be able to use the storefront in portrait or landscape unless one orientation is genuinely essential.
How does WCAG 1.3.4 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with mobile checkout blocks the page in landscape with a rotate-your-device message. and gift-card balance tools only render in portrait because of rigid viewport rules. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 1.3.4 violations?
Start by auditing the live storefront, then Let content reflow for both orientations instead of locking the viewport.; Reserve orientation restrictions for truly essential experiences, not convenience.; Test modals, drawers, and sticky CTAs after rotation on phones and tablets.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 1.3.4 → Free ADA Compliance Scan