WCAG 3.1.2: Language of Parts
Level AAQuick answer: Passages or phrases in another language should be identified so pronunciation and comprehension stay accurate.
What This Means
On ecommerce sites, Language of Parts 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 french product names appear in english pdp copy with no lang attribute. or bilingual care instructions mix spanish and english in the same paragraph., 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
- French product names appear in English PDP copy with no lang attribute.
- Bilingual care instructions mix Spanish and English in the same paragraph.
- Localized testimonials include untranslated phrases that screen readers mispronounce.
- Checkout legal text inserts foreign-language payment terms without marking them up.
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.
- Wrap foreign-language phrases in elements with the correct lang attribute.
- Mark multilingual legal, care, and ingredient content at the phrase level when needed.
- Coordinate with localization teams so CMS editors know where language switches occur.
- Skip proper names only when pronunciation changes do not matter.
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 -->
<p>Made with tela vaquera premium.</p>
<!-- After -->
<p>Made with <span lang="es">tela vaquera</span> premium.</p>FAQ
What is WCAG 3.1.2?
Passages or phrases in another language should be identified so pronunciation and comprehension stay accurate.
How does WCAG 3.1.2 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with french product names appear in english pdp copy with no lang attribute. and bilingual care instructions mix spanish and english in the same paragraph. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 3.1.2 violations?
Start by auditing the live storefront, then Wrap foreign-language phrases in elements with the correct lang attribute.; Mark multilingual legal, care, and ingredient content at the phrase level when needed.; Coordinate with localization teams so CMS editors know where language switches occur.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 3.1.2 → Free ADA Compliance Scan