The default human language of Web pages, non-web documents or software can be programmatically determined. (Level A)

Rationale

The purpose of this checkpoint is to ensure that user agents can correctly present content written in multiple languages using the presentation and pronunciation rules for that language.

When you identify the primary language of content, it enables assistive technology to present text and other linguistic content correctly. In example, for a web page the lang attribute of the <html> element allows you to specify the language and enables both assistive technologies and conventional user agents to render the content more accurately.

Note: Where software platforms provide a “locale / language” setting, applications that use that setting and render their interface in that “locale / language” would comply with this requirement. Applications that do not use that setting, but instead use an accessibility-supported method for exposing the human language of the software would also comply.

Refer to Understanding SC 3.1.1  for more information (external link to WCAG).

Development Techniques

Review the General techniques as well as other tabs applicable to your technology.  Prioritize the use of technology-specific techniques, and implement the General techniques as needed. You are always required to find, understand and implement accessible code techniques to meet the checkpoint. The documented techniques and supplements are not exhaustive; they illustrate acceptable ways to achieve the spirit of the checkpoint. If numbered, techniques are in order of preference, with recommended techniques listed first. Where used, IBM information that complements the WCAG techniques is indicated as supplemental.

General techniques

Any item in this section represents a technique deemed sufficient. Where used, IBM information that complements the WCAG techniques is indicated as supplemental.

General supplements

The following examples and comments provide additional information beyond that available in the WCAG techniques. 

Use the “locale / language” setting or an accessibility-supported method for exposing the human language of content

If available, use the language or locale setting, or an accessibility-supported method for exposing the human language of your content.

Web (HTML, ARIA, CSS) techniques

In addition to the General techniques, the Web (HTML, ARIA, CSS) techniques in this section represent a technique or combination of techniques deemed sufficient for meeting this checkpoint.

Mobile (iOS) techniques

Meet the "Use the 'locale / language' setting" supplemental General technique by:

Internationalizing the user interface

iOS provides a user preferred locale / language setting in Settings (Settings > General > Language & Region > [device] Language).  Your native iOS application meets this checkpoint when it sets the localized content based on the Language user setting. Refer to About Internationalization and Localization.  Hybrid applications meet this requirement when they set the language of the content section using the lang attribute of the <html> element.

Eclipse techniques

Instructions: The Eclipse techniques in this section represent a technique or combination of techniques deemed sufficient for meeting this checkpoint (3.1.1).

Use locale and language settings

Render the application interface using the platform locale and language settings.

Launch applications in a specific locale and language

Eclipse provides the ability to launch applications in a specific locale and language using the -nl locale startup argument which is equivalent to osgi.nl=locale.

Windows-based (MSAA+IA2) techniques

Instructions: The Windows-based (MSAA+IA2) techniques in this section represent a technique or combination of techniques deemed sufficient for meeting this checkpoint (3.1.1). 

Use locale and language settings

Render the application interface using the platform locale and language settings.

Use IAccessible2 Object

If an application uses a locale and language other than those defined by the platform, the IA2Locale must be returned through the IAccessible2 object.


Most links in this checklist reside outside ibm.com at the Web Content Accessibility Guidelines (WCAG) 2.0. W3C Recommendation 11 December 2008: http://www.w3.org/TR/WCAG20/

Copyright © 1994-2017 World Wide Web Consortium, (Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University, Beihang University). All Rights Reserved.

Copyright © 2001, 2017 IBM Corporation