WCAG 3.1.6: Pronunciation
Level AAAQuick answer: Where pronunciation affects meaning, content should help users know how a term is meant to be spoken.
What This Means
On ecommerce sites, Pronunciation 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 brand names with nonstandard pronunciation appear without guidance on press or about pages. or product ingredient names are easily mispronounced and could be confused with others., 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
- Brand names with nonstandard pronunciation appear without guidance on press or about pages.
- Product ingredient names are easily mispronounced and could be confused with others.
- Audio support pages reference terms whose spoken form changes meaning.
- International collections use names that screen readers pronounce incorrectly without hints.
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.
- Provide pronunciation help for terms where misunderstanding changes meaning.
- Use phonetic guidance, inline notes, or linked glossary entries when necessary.
- Mark language-of-parts correctly so pronunciation engines have a better chance.
- Focus on terms central to purchase or support understanding rather than every proper noun.
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>Ask for the Nuxe line in store.</p>
<!-- After -->
<p>Nuxe <span aria-label="pronounced nyooks">(pronounced 'nyooks')</span></p>FAQ
What is WCAG 3.1.6?
Where pronunciation affects meaning, content should help users know how a term is meant to be spoken.
How does WCAG 3.1.6 affect ecommerce sites?
It affects ecommerce anywhere shoppers interact with brand names with nonstandard pronunciation appear without guidance on press or about pages. and product ingredient names are easily mispronounced and could be confused with others. If those patterns are inaccessible, customers can miss product information, fail forms, or abandon checkout.
How to fix WCAG 3.1.6 violations?
Start by auditing the live storefront, then Provide pronunciation help for terms where misunderstanding changes meaning.; Use phonetic guidance, inline notes, or linked glossary entries when necessary.; Mark language-of-parts correctly so pronunciation engines have a better chance.. Prioritize templates and apps that repeat the issue across product, cart, checkout, and account pages.
Check if your store passes WCAG 3.1.6 → Free ADA Compliance Scan