- Success Criterion 3.1.2
- Conformance level AA
User-Generated Content in Another Language Never Tagged
3.1.2 — Language of Parts
Scenario
Setting
A crowdfunding platform's campaign page
What’s wrong
User-generated content areas known to be another language with no lang handling strategy.
Example
<div class="campaign-update">
<h3>Update #4</h3>
<p>Merci a tous pour votre soutien incroyable cette semaine !</p>
</div> Why it matters
Campaign creators post updates in whatever language they speak, but the platform never detects or tags it, so backers hear French updates read as mangled English.
How to test
Check user-generated content areas known to include other languages: verify there's a strategy (even a simple lang wrapper) for marking non-page-language UGC.
How to fix
Run the detected or creator-selected language through a lang attribute at publish time, since user-generated content can't rely on one page-level declaration.
<div class="campaign-update">
<h3>Update #4</h3>
<p lang="fr">Merci a tous pour votre soutien incroyable cette semaine !</p>
</div> Outcome
A backer following the campaign hears each update read in its actual language, no matter who wrote it.
Who is affected
Screen reader-using backers following a campaign's updates need each post's actual language flagged, especially when creators post outside the platform default.
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
- Mixed-Language Legal or Product Text Left Entirely Unmarked
- Language Attribute Copy-Pasted Onto the Wrong Piece of Text
- Bilingual Layout Where One Column’s Language Goes Unmarked