Skip to content

Conversation

@patrickhlauke
Copy link
Member

Closes #2639 which raised a concern about the mismatch of terms in WCAG ("human language") and the i18n glossary ("natural language"). Keep the actual term as "human language" (as it's too pervasive in normative and non-normative documents to just change), while adding the mention of "natural" (as well as "constructed" - for instance, Esperanto) in the definition itself.

Closes #2639 which raised a concern about the mismatch of terms in WCAG ("human language") and the i18n glossary ("natural language"). Keep the actual term as "human language" (as it's too pervasive in normative and non-normative documents to just change), while adding the mention of "natural" (as well as "constructed" - for instance, Esperanto) in the definition itself.
@netlify
Copy link

netlify bot commented Dec 3, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit c488893
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/693032b1329468000881a025
😎 Deploy Preview https://deploy-preview-4787--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use term "natural language" instead of "human language" in glossary?

2 participants