WCAG 3.1.1: Language of Page
Level AQuick answer: Each page should declare its primary language so screen readers and translation tools interpret it correctly.
What This Means
On ecommerce sites, Language of Page 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 the storefront omits the lang attribute entirely. or a spanish microsite still declares lang="en" from the base layout., 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
- The storefront omits the lang attribute entirely.
- A Spanish microsite still declares lang="en" from the base layout.
- Help pages embedded in checkout inherit the wrong language from the parent frame.
- Country-specific landing pages reuse templates without updating the document language.
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.
- Set the html lang attribute to the dominant language of each page.
- Switch lang dynamically for localized templates generated from CMS content.
- Check transactional and support pages, not just the homepage.
- Include language review in international rollout QA.
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 -->
<html>
<!-- After -->
<html lang="en">FAQ
What is WCAG 3.1.1?
Each page should declare its primary language so screen readers and translation tools interpret it correctly.
How does WCAG 3.1.1 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with the storefront omits the lang attribute entirely. and a spanish microsite still declares lang="en" from the base layout. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 3.1.1 violations?
Start by auditing the live storefront, then Set the html lang attribute to the dominant language of each page.; Switch lang dynamically for localized templates generated from CMS content.; Check transactional and support pages, not just the homepage.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 3.1.1 → Free ADA Compliance Scan