3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA).
This success criterion requires that the contents written in multiple languages on the same web page has the human language defined in a programmatically determinable way. In other words, where the default language of the page is, say English but the page has phrases, sentences, paragraphs or passages from any other language, then the secondary language of such texts must be programmatically determined.
Exceptions
Any words that are adopted into the default language and that is part of a phrase or immediately surrounding text need not meet this criterion technical terms can be ignored.
Benefits
Visual browsers would be able to display correct characters for the language of parts and change the reading order for the languages that have right to left reading
Braille translating software would be able to provide correct Braille characters and contractions
Screen readers would be able to switch to apt pronunciation rules
Traditional browsers would be able to process the texts aptly
Machine based translation technologies would be able to translate the texts from one language into another when there is a change of language
In the modern browsers, when such secondary language texts occur, users would be able to look up the meaning using a dictionary.
Points to Ponder
Ensure to use appropriate language code (lan=”fr”) wherever the text is in other language
Ensure appropriate language token is used in the lang attribute (lang=”pt-br”).
Digital accessibility is my passion. Working with as many industry leaders, striving to achieve digital inclusiveness and spread #a11y awareness in every
nuke and corner of the digital world!
If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A) Intent of this Success Criterion The intent of this Success Criterion is to ensure that when users navigate sequentially through content, they encounter information in…
Success Criterion 1.4.11 Non-text Contrast (Level AA): The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and…
Success Criterion 2.5.3 Label in Name (Level A): For user interface components with labels that include text or images of text, the name contains the text that is presented visually.A best practice is to have the text of the label at the start of the name. Imagine you are using the voice control feature in…
After 5 years of research, much deliberations, constant feedback, several drafts and edits, the Web Content Accessibility Guidelines (WCAG) 2.2 has arrived as a W3C recommendation. This version was made as a W3C recommendation on October 05, 2023 and calls for appreciations and celebrations as the inclusivity of the digital world has achieved one more…
1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) This success criterion intends to provide captions for all the videos that have audio in the form of dialogues, voiceover and other sound…
2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of…
