How to Translate Shopify Store Accessibility Content for International Markets: ARIA Labels, Screen Reader Text and WCAG Compliance Across Languages
Most Shopify merchants going multilingual translate their product titles and descriptions — then stop. But if your store serves screen reader users in Germany, Japan or Brazil, an untranslated aria-label="Add to cart" or a missing alt attribute leaves those customers locked out just as effectively as having no translation at all. Shopify accessibility translation multilingual work isn't optional if you want to sell legally and ethically in markets where WCAG compliance is increasingly tied to consumer protection law.
This guide walks through exactly which accessibility strings live in your Shopify store, where they break when you go multilingual, and how to fix them systematically.
Why Accessibility Content Breaks When You Go Multilingual
When you add a second language to Shopify using Markets, the storefront switches rendered text based on locale. But accessibility content often lives outside the fields merchants translate first — it's embedded in theme Liquid, hardcoded in JavaScript, or stored as metafields. The result: a French shopper using VoiceOver on iOS hears English button announcements mid-sentence in a French storefront.
The specific failure points fall into three categories:
- ARIA attributes —
aria-label,aria-describedby,aria-roledescriptionvalues that name interactive elements - Screen reader–only text — visually hidden
<span class="sr-only">strings that add context (e.g. "Remove item from cart") - Form and error text — field labels, placeholder text, and validation messages that assistive tech reads aloud
Before addressing each, it helps to run The Complete Shopify Translation Checklist for Going Multilingual to audit which content types you've already covered, then layer accessibility strings on top.
Where Accessibility Strings Live in a Shopify Theme
Theme locale files (locales/*.json)
Most modern Shopify themes — Dawn, Refresh, Sense — store ARIA labels and sr-only text inside locale JSON files. You'll find keys like:
"accessibility": {
"skip_to_text": "Skip to content",
"close_modal": "Close dialog",
"open_menu": "Open navigation menu",
"loading": "Loading"
}
These are the strings to translate first. Because they live in the theme's locale system, they should surface inside Shopify's translation editor. If they don't, or if your theme is custom, you may need to extract them manually. The How to Translate Shopify Theme Content: Buttons, Navigation and System Text guide covers the full scope of theme locale keys.
Inline Liquid and JavaScript
Some themes set ARIA labels dynamically — for example, a quantity selector might render aria-label="Increase quantity for {{ product.title }}" directly in a .liquid file. When Shopify translates product.title, the surrounding ARIA string often stays in English unless you've added a t: filter:
aria-label="{{ 'accessibility.increase_qty' | t: product: product.title }}"
If your theme doesn't use the t: filter here, those strings will never appear in the translation editor and won't be picked up by any translation app.
Image alt text
Alt text is the most commonly missed accessibility field in multilingual stores. Every product image, collection banner, and editorial image needs locale-specific alt text. A detailed breakdown of the workflow is in How to Translate Shopify Store Videos, Alt Text and Media Content for International Markets.
Checkout and form fields
Checkout is a separate surface. Labels, error messages, and validation text that screen readers announce during checkout have their own translation requirements — covered in depth in How to Translate Shopify Store Checkout Fields, Error Messages and Validation Text for International Customers.
WCAG 2.1 Requirements That Apply Across Languages
WCAG 2.1 Success Criterion 3.1.1 requires that the language of each page be programmatically determinable. SC 3.1.2 extends this to individual passages that are in a different language from the rest of the page. In practical terms, this means:
- Your
<html lang="fr">attribute must match the active locale - Any English string persisting on a French page — including ARIA labels — is a WCAG failure
- Form instructions and error messages (SC 3.3.1, 3.3.2) must be in the user's language
Shopify handles <html lang> automatically when you use native Markets, which is one reason to avoid iframe-based workarounds. But the language attribute being correct doesn't help if the text it governs is still in English.
In the EU, the European Accessibility Act (EAA) comes into full force for e-commerce in June 2025, making WCAG 2.1 AA a practical legal requirement for selling to EU consumers. If your store also handles restricted products, note that How to Translate Shopify Store Age Verification and Restricted Product Compliance Pages for International Markets covers the compliance content that sits alongside accessibility concerns.
How to Audit and Translate Accessibility Strings Systematically
Step 1: Extract all locale keys related to accessibility
Open your theme's locales/en.default.json and search for these patterns: aria, sr_only, screen_reader, skip, close, open, loading, toggle, expand, collapse. List every key you find.
Step 2: Check which keys surface in Shopify's translation editor
In Shopify Admin → Themes → Actions → Edit default theme content, scroll through "General" and "Accessibility" sections. Any key not visible here won't be auto-translated by any app without manual mapping.
Step 3: Translate via the Shopify Translations API
Apps like StoreLingo use Shopify's native Translations API to write locale strings back into your theme's translation layer — no theme file edits required. This means your accessibility strings can be translated alongside product content in the same workflow. For stores with hundreds of products, How to Bulk-Translate Hundreds of Shopify Products in Minutes shows how to scale that efficiently.
Step 4: Handle brand-specific terminology carefully
Some ARIA strings reference product or brand names. Use a translation glossary to prevent AI from translating terms that should stay consistent — like a brand name used inside aria-label="Add [BrandName] to wishlist". How to Use a Translation Glossary to Protect Brand Terms Across Your Shopify Store explains exactly how to set that up.
Step 5: Test with actual screen readers
- macOS / iOS: VoiceOver (free, built-in)
- Windows: NVDA (free) or JAWS (commercial)
- Android: TalkBack
Switch your storefront to each target locale, navigate using only the keyboard and screen reader, and listen for any English strings surfacing in a non-English context.
Third-Party Widgets and Accessibility
Accessibility overlays and third-party review apps often inject their own ARIA labels that are outside Shopify's translation layer entirely. Those strings are controlled by the widget vendor. The workaround is to either configure the widget's own locale settings, or use Shopify's postMessage API if the widget supports it. The broader challenge of third-party content is covered in How to Translate Shopify App Blocks and Third-Party Widget Content for International Stores.
Legal Pages and Accessibility Policy
If your store publishes an accessibility statement — increasingly expected in Germany, France, and the Netherlands — that page needs to be translated with the same rigour as your terms and conditions and privacy policy. An untranslated accessibility statement on a French storefront is a contradiction in terms.
Add StoreLingo on the Shopify App Store →
FAQ
Do Shopify themes automatically translate ARIA labels when I add a new language?
Only if those ARIA labels are stored as locale keys in the theme's JSON files and use the t: filter in Liquid. Hardcoded strings or those set in JavaScript will not be translated automatically and need to be extracted and mapped manually.
Which WCAG success criteria specifically apply to multilingual accessibility in Shopify? The most directly relevant are SC 3.1.1 (Language of Page), SC 3.1.2 (Language of Parts), SC 1.1.1 (Non-text Content, which covers alt text), and SC 3.3.1–3.3.2 (Error Identification and Labels in Context). All of these require that the text assistive technology reads aloud matches the language of the active storefront locale.
Can a translation app translate ARIA labels without editing my theme files? Yes, if the ARIA strings are registered as translatable content via Shopify's Translations API. Apps that write translations through the native API — rather than injecting JavaScript overlays — can update these strings without touching your theme code, which keeps your theme upgradeable and your store speed intact.
Choose from 47 languages
StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.
Add to Shopify →