Skip to content

3.1.2-draft #278

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

3.1.2-draft #278

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions comments/3.1.2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,10 @@
[wcag:language-of-parts]
[wcag2ict:applying-sc-3-1-2-language-of-parts-to-non-web-documents-and-software]

Placeholder
This applies directly as written, and as described in Intent from [Understanding Success Criterion 3.1.2](https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts#intent).

[issue:15]
**3.1.2 Language of Parts** The [human language](https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts#dfn-human-language) of each passage or phrase in the content can be [programmatically determined](https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts#dfn-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](https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts#dfn-text).

[note:The exception to this criterion applies when the underlying technology, platform, or operating system imposes technical limitations. In such cases, the requirement should be followed as closely as possible within the available technical capabilities. An example of the exception is where the underlying technology does not support marking up language of parts of text, or where it would require marking up all text in all locations within the software.]

[example:A German mobile app includes the English phrase “Welcome back.” On Android, the phrase is programmatically determined as English using LocaleSpan, allowing TalkBack to use the correct English pronunciation. On iOS, the same phrase is programmatically determined using accessibilitySpeechLanguage, ensuring that VoiceOver also uses the correct English pronunciation rather than the German pronunciation.]
19 changes: 12 additions & 7 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3524,14 +3524,19 @@ <h2>Success Criterion 3.1.2 Language of Parts</h2>
</footer>
</details>
</p>
<p>Placeholder</p>
<p>This applies directly as written, and as described in Intent from <a href="https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts#intent">Understanding Success Criterion 3.1.2</a>.</p>
<p><strong>3.1.2 Language of Parts</strong> The <a href="https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts#dfn-human-language">human language</a> of each passage or phrase in the content can be <a href="https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts#dfn-programmatically-determined">programmatically determined</a> 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 <a href="https://www.w3.org/WAI/WCAG22/Understanding/language-of-parts#dfn-text">text</a>.</p>
<p>
<div class="note" title="Work In Progress">
<p>
<a href="https://github.com/w3c/matf/issues/15" target="_blank">
Read issue #15 on GitHub
</a>
</p>
<div class="note wcag2mobile">
<p>The exception to this criterion applies when the underlying technology, platform, or operating system imposes technical limitations. In such cases, the requirement should be followed as closely as possible within the available technical capabilities. An example of the exception is where the underlying technology does not support marking up language of parts of text, or where it would require marking up all text in all locations within the software.</p>

</div>
</p>
<p>
<div class="example wcag2mobile">
<div class="marker">Example</div>
<p>A German mobile app includes the English phrase “Welcome back.” On Android, the phrase is programmatically determined as English using LocaleSpan, allowing TalkBack to use the correct English pronunciation. On iOS, the same phrase is programmatically determined using accessibilitySpeechLanguage, ensuring that VoiceOver also uses the correct English pronunciation rather than the German pronunciation.</p>

</div>
</p>

Expand Down