- Success Criterion 3.1.2
- Conformance level AA
Mixed-Language Legal or Product Text Left Entirely Unmarked
3.1.2 — Language of Parts
Scenario
Setting
A weather app's forecast screen
What’s wrong
Mixed-language product/legal content (e.g., French terms inside English page) unmarked.
Example
<p>Please visita nuestra tienda.</p>Why it matters
Screen-reader users hearing mixed-language content with the wrong voice rules.
How to test
Find mixed-language content (e.g., French legal terms inside an English page): check for lang markup on the foreign-language portion.
How to fix
The passage in another language must carry its own correct lang attribute.
<p>Please visit <span lang="es">nuestra tienda</span>.</p>A lang attribute on the foreign-language span switches the screen reader's pronunciation for just that phrase.
Outcome
On a weather app's forecast screen, this barrier is gone for screen-reader users hearing mixed-language content with the wrong voice rules — they get the same result as anyone else here.
Who is affected
Screen-reader users hearing mixed-language content with the wrong voice rules.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- No Way to Programmatically Tell Which Language a Passage Uses
- Foreign-Language Quote or Phrase With No Language Attribute
- Language Switcher Link With No Language Tag of Its Own
- Language Attribute Copy-Pasted Onto the Wrong Piece of Text
- Bilingual Layout Where One Column’s Language Goes Unmarked
- User-Generated Content in Another Language Never Tagged