1.7 Identify language changes in text
Contents
WAI checkpoint 4.1
Full WAI text: "Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions)."
Natural language refers to spoken, written or signed languages, such as English, Irish, Irish Sign Language and Braille. The predominant natural language of a web page should be identified in the underlying HTML. If there are passages of text contained in a page, which are presented in a different language to the predominant natural language you should flag the change. This also applies to text equivalents, such as alt text or captions, for information presented in visual or audio format.
Rationale
Speech synthesisers and Braille devices need to be told what the natural language is so they can present the information using the correct pronunciation. Failing to identify the natural language could cause these devices to mispronounce words, making the information difficult to undestand.
Identifying the natural language also facilitates automated translators: software or machines capable of reading the contents of a page and translating it into another language.
Directions and Techniques
WAI recommended technique on identifying changes in the natural language
Identify changes in the natural language with the "lang" attribute. This HTML attribute describes the natural language of the text. Use it to identify the primary natural language and any changes to the natural language. Follow the WAI recommendations on using the LANG attribute
How you could check for this:
There are no specific test methods recommended for this guideline.
Guidelines for Web Accessibility - Priority 1- 1.1 Provide a text equivalent for every non-text element
- 1.2 Ensure that information does not rely on colour perception
- 1.3 Avoid causing the screen to flicker
- 1.4 Provide an auditory description of the visual information in multimedia presentations
- 1.5 For multimedia, ensure that timing of alternative descriptions is synchronised with the presentation
- 1.6 Use the clearest and simplest language appropriate
- 1.7 Identify language changes in text
- 1.8 Ensure that equivalents for dynamic content are updated when the dynamic content changes
- 1.9 For data tables, identify row and column headers
- 1.10 For complex data tables, use mark-up to associate data cells and header cells
- 1.11 Add titles to frames
- 1.12 Ensure that documents can be read without style sheets
- 1.13 Provide text links to emulate server-side image maps
- 1.14 Use client-side image maps rather than server-side image maps where possible
- 1.15 Ensure that scripts and applets that provide the only source of important functionality are directly accessible or compatib
- 1.16 Ensure that pages are usable without support for scripts, applets, or other programmatic objects
- 1.17 If you cannot make a page accessible, provide an equivalent accessible page
