Note: This requirement does not apply to individual words or to phrases that have become part of the primary language of the content.
The intent of this success criterion is to ensure that user agents can correctly present content written in a language that is different from the language of the delivery unit as a whole. This applies to graphical browsers as well as screen readers, Braille displays, and other voice browsers.
Both assistive technologies and conventional user agents can render text more accurately if changes of language within the delivery unit are identified. Screen readers can switch to the pronunciation rules for the language of the foreign text, then switch back to the pronunciation rules of the primary language at the end of the foreign phrase or passage. Visual browsers can display characters and scripts in appropriate ways. This is especially important when one language reads from left to right and the other reads from right to left, or when the foreign phrase or passage uses a different alphabet than the primary language. Users with disabilities who know the language of the foreign passage or phrase as well as the language of the delivery unit as a whole will be better able to understand the content.
The following combinations of techniques are deemed to be sufficient by the WCAG Working Group for meeting success criterion 3.1 L2 SC1.
Instructions: Select the situation below that matches your content. Beneath it, are the option(s) that are known and documented to be sufficient for that situation. For the technology-specific techniques, see the options for the technology you are using listed immediately below.
Situation A: If the foreign passage or phrase has the same text direction as the primary content, the following would be sufficient:
Situation B: If the foreign passage or phrase has a different text direction from the primary content, the following would be sufficient:
"Generally, block-level elements may contain inline elements and other
block-level elements. Generally, inline elements may contain only data and
other inline elements. Inherent in this structural distinction is the idea
that block elements create "larger" structures than inline elements." [HTML 4.01
7.5.3 Block-level and inline elements] Examples of block-level elements
are blockquote, div, p, and h1-h6. Example of
inline elements include span, strong, and code.
lang attribute on block-level or inline (text-level)
elements (HTML 4.01)lang attribute AND the xml:lang attribute
on block-level or inline (text-level) elements (XHTML served as
text/html)xml:lang attribute on the block-level or inline
(text-level) elements (XHTML served as application/xhtml+xml)Editorial Note: Modify based on proposal for Identifying the primary language. As with L1SC1 - break into 3 techniques or find one way to reference all three approaches?
dir attribute to a block level element to change its
directionality. dir attribute on an inline element to resolve problems
with nested directional runs.The following are common mistakes which are considered failures of this success criterion by the working group.
Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.