Skip to content

Commit

Permalink
Merge pull request #530 from w3c/ChrisLoiselle-patch-2
Browse files Browse the repository at this point in the history 
SHA: 0634423
Reason: push, by maryjom

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
  • Loading branch information
@maryjom @github-actions
maryjom and github-actions[bot] committed Oct 15, 2024
1 parent 72b44f0 commit 8106d62
Showing 1 changed file with 9 additions and 9 deletions.
18 changes: 9 additions & 9 deletions index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,7 @@
<link rel="stylesheet" type="text/css" href="wcag2ict.css">

<meta name="color-scheme" content="light">
<meta name="revision" content="a98813143eee30f97feed99627b6fcb9956aef2a">
<meta name="revision" content="06344239526eb15401aa3e61df5b03864d194e0d">
<meta name="description" content="This document, “Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)” describes how the Web Content Accessibility Guidelines (WCAG) versions 2.0 [WCAG20], 2.1 [WCAG21], and 2.2 [WCAG22] principles, guidelines, and success criteria can be applied to non-web Information and Communications Technologies (ICT), specifically to non-web documents and software. It provides informative guidance (guidance that is not normative and does not set requirements).">
<style>
var{position:relative;cursor:pointer}
Expand Down Expand Up @@ -212,16 +212,16 @@
}
},
"lint": false,
"gitRevision": "a98813143eee30f97feed99627b6fcb9956aef2a",
"publishISODate": "2024-10-10T00:00:00.000Z",
"generatedSubtitle": "W3C Editor's Draft 10 October 2024"
"gitRevision": "06344239526eb15401aa3e61df5b03864d194e0d",
"publishISODate": "2024-10-15T00:00:00.000Z",
"generatedSubtitle": "W3C Editor's Draft 15 October 2024"
}</script>
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED"></head>
<body class="h-entry informative"><div class="head">
<p class="logos"><a class="logo" href="https://www.w3.org/"><img crossorigin="" alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2021/logos/W3C" width="72">
</a></p>
<h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)</h1>
<p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2024-10-10">10 October 2024</time></p>
<p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2024-10-15">15 October 2024</time></p>
<details open="">
<summary>More details about this document</summary>
<dl>
Expand Down Expand Up @@ -734,7 +734,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
<p>This applies directly as written, and as described in <a href="https://www.w3.org/WAI/WCAG22/Understanding/captions-prerecorded#intent">Intent from Understanding Success Criterion 1.2.2</a>.</p>
<div class="note" role="note" id="issue-container-generatedID-35"><div role="heading" class="note-title marker" id="h-note-35" aria-level="7"><span>Note (Added)</span></div><div class="wcag2ict">

<p>The WCAG 2 definition of “<a href="https://www.w3.org/TR/WCAG22/#dfn-captions">captions</a>” notes that “in some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired.” Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and/or <a href="https://www.w3.org/TR/WCAG22/#dfn-text-alternative">text alternative</a> for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.</p></div></div><p></p>
<p>The WCAG 2 definition of “<a href="https://www.w3.org/TR/WCAG22/#dfn-captions">captions</a>” notes that “in some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired". Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and/or <a href="https://www.w3.org/TR/WCAG22/#dfn-text-alternative">text alternative</a> for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.</p></div></div><p></p>
</section></section><section id="audio-description-or-media-alternative-prerecorded"><div class="header-wrapper"><h5 id="x6-1-3-4-audio-description-or-media-alternative-prerecorded">1.2.3 Audio Description or Media Alternative (Prerecorded)</h5><a class="self-link" href="#audio-description-or-media-alternative-prerecorded" aria-label="Permalink for Section 1.2.3 Audio Description or Media Alternative (Prerecorded)"></a></div><p>(Level A)</p><blockquote class="wcag-quote"> <p>An <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-alternative-for-time-based-media" id="ref-for-dfn-alternative-for-time-based-media-2" title="document including correctly sequenced text descriptions of time-based visual and auditory information and providing a means for achieving the outcomes of any time-based interaction">alternative for time-based media</a> or <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-audio-descriptions" id="ref-for-dfn-audio-descriptions-1" title="narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone">audio description</a> of the <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-prerecorded" id="ref-for-dfn-prerecorded-3" title="information that is not live">prerecorded</a> <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-video" id="ref-for-dfn-video-1" title="the technology of moving or sequenced pictures or images">video</a> content is provided for <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-synchronized-media" id="ref-for-dfn-synchronized-media-2" title="audio or video synchronized with another format for presenting information and/or with time-based interactive components, unless the media is a media alternative for text that is clearly labeled as such">synchronized media</a>, except when the media is a <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-media-alternative-for-text" id="ref-for-dfn-media-alternative-for-text-3" title="media that presents no more information than is already presented in text (directly or via text alternatives)">media alternative for text</a> and is clearly labeled as such. </p> </blockquote>
<section id="applying-sc-1-2-3-audio-description-or-media-alternative-prerecorded-to-non-web-documents-and-software"><div class="header-wrapper"><h6 id="x6-1-3-4-1-applying-sc-1-2-3-audio-description-or-media-alternative-prerecorded-to-non-web-documents-and-software">Applying SC 1.2.3 Audio Description or Media Alternative (Prerecorded) to Non-Web Documents and Software</h6><a class="self-link" href="#applying-sc-1-2-3-audio-description-or-media-alternative-prerecorded-to-non-web-documents-and-software" aria-label="Permalink for Section Applying SC 1.2.3 Audio Description or Media Alternative (Prerecorded) to Non-Web Documents and Software"></a></div>
<p>This applies directly as written, and as described in <a href="https://www.w3.org/WAI/WCAG22/Understanding/audio-description-or-media-alternative-prerecorded#intent">Intent from Understanding Success Criterion 1.2.3</a>.</p>
Expand All @@ -752,7 +752,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
<p>This applies directly as written, and as described in <a href="https://www.w3.org/WAI/WCAG22/Understanding/captions-live#intent">Intent from Understanding Success Criterion 1.2.4</a>.</p>
<div class="note" role="note" id="issue-container-generatedID-39"><div role="heading" class="note-title marker" id="h-note-39" aria-level="7"><span>Note (Added)</span></div><div class="wcag2ict">

<p>The WCAG 2 definition of “<a href="https://www.w3.org/TR/WCAG22/#dfn-captions">captions</a>” notes that “In some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired.” Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and/or <a href="https://www.w3.org/TR/WCAG22/#dfn-text-alternative">text alternative</a> for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.</p></div></div><p></p>
<p>The WCAG 2 definition of “<a href="https://www.w3.org/TR/WCAG22/#dfn-captions">captions</a>” notes that “In some countries, captions are called subtitles”. They are also sometimes referred to as “subtitles for the hearing impaired". Per the definition in WCAG 2, to meet this success criterion, whether called captions or subtitles, they would have to provide “synchronized visual and/or <a href="https://www.w3.org/TR/WCAG22/#dfn-text-alternative">text alternative</a> for both speech and non-speech audio information needed to understand the media content” where non-speech information includes “sound effects, music, laughter, speaker identification and location”.</p></div></div><p></p>
</section></section><section id="audio-description-prerecorded"><div class="header-wrapper"><h5 id="x6-1-3-6-audio-description-prerecorded">1.2.5 Audio Description (Prerecorded)</h5><a class="self-link" href="#audio-description-prerecorded" aria-label="Permalink for Section 1.2.5 Audio Description (Prerecorded)"></a></div><p>(Level AA)</p><blockquote class="wcag-quote"> <p><a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-audio-descriptions" id="ref-for-dfn-audio-descriptions-2" title="narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone">Audio description</a> is provided for all <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-prerecorded" id="ref-for-dfn-prerecorded-4" title="information that is not live">prerecorded</a> <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-video" id="ref-for-dfn-video-2" title="the technology of moving or sequenced pictures or images">video</a> content in <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-synchronized-media" id="ref-for-dfn-synchronized-media-4" title="audio or video synchronized with another format for presenting information and/or with time-based interactive components, unless the media is a media alternative for text that is clearly labeled as such">synchronized media</a>. </p> </blockquote>
<section id="applying-sc-1-2-5-audio-description-prerecorded-to-non-web-documents-and-software"><div class="header-wrapper"><h6 id="x6-1-3-6-1-applying-sc-1-2-5-audio-description-prerecorded-to-non-web-documents-and-software">Applying SC 1.2.5 Audio Description (Prerecorded) to Non-Web Documents and Software</h6><a class="self-link" href="#applying-sc-1-2-5-audio-description-prerecorded-to-non-web-documents-and-software" aria-label="Permalink for Section Applying SC 1.2.5 Audio Description (Prerecorded) to Non-Web Documents and Software"></a></div>
<p>This applies directly as written, and as described in <a href="https://www.w3.org/WAI/WCAG22/Understanding/audio-description-prerecorded#intent">Intent from Understanding Success Criterion 1.2.5</a>.</p>
Expand Down Expand Up @@ -1841,7 +1841,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
</dd></dl><p></p>
</section></section><section id="dfn-programmatically-determinable"><div class="header-wrapper"><h4 id="x7-3-18-dfn-programmatically-determinable">programmatically determined</h4><a class="self-link" href="#dfn-programmatically-determinable" aria-label="Permalink for Section programmatically determined"></a></div><blockquote class="wcag-quote"> <p>determined by software from author-supplied data provided in a way that different <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-user-agents" id="ref-for-dfn-user-agents-10" title="any software that retrieves and presents Web content for users">user agents</a>, including <a class="internalDFN" data-link-type="dfn" href="https://www.w3.org/TR/wcag22/#dfn-assistive-technologies" id="ref-for-dfn-assistive-technologies-7" title="hardware and/or software that acts as a user agent, or along with a mainstream user agent, to provide functionality to meet the requirements of users with disabilities that go beyond those offered by mainstream user agents">assistive technologies</a>, can extract and present this information to users in different modalities </p> <aside class="example" id="example-19"><div class="marker">Example 1</div><p><span>Example 1: </span>Determined in a markup language from elements and attributes that are accessed directly by commonly available assistive technology. </p></aside> <aside class="example" id="example-20"><div class="marker">Example 2</div><p><span>Example 2: </span>Determined from technology-specific data structures in a non-markup language and exposed to assistive technology via an accessibility API that is supported by commonly available assistive technology. </p></aside> </blockquote>
<section id="applying-programmatically-determined-to-non-web-documents-and-software"><div class="header-wrapper"><h5 id="x7-3-18-1-applying-programmatically-determined-to-non-web-documents-and-software">Applying “programmatically determined” to Non-Web Documents and Software</h5><a class="self-link" href="#applying-programmatically-determined-to-non-web-documents-and-software" aria-label="Permalink for Section Applying “programmatically determined” to Non-Web Documents and Software"></a></div>
<p>This applies directly as written and as described in the WCAG 2 glossary, replacing “user agents, including assistive technologies,” with “assistive technologies and accessibility features of software” and adding “and accessibility features of software” after “assistive technology”.</p>
<p>This applies directly as written and as described in the WCAG 2 glossary, replacing “user agents, including assistive technologies", with “assistive technologies and accessibility features of software” and adding “and accessibility features of software” after “assistive technology”.</p>
<p>With this substitution and addition, it would read:</p>
<dl><dt>programmatically determined (programmatically determinable)</dt><dd>

Expand Down Expand Up @@ -2095,7 +2095,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
<li><a href="#bypass-blocks">2.4.1 Bypass Blocks</a> — The WCAG2ICT interpretation of this success criterion replaces "sets of Web pages" with "sets of software programs" which are extremely rare - especially for closed functionality software. However, being able to bypass blocks of content that are repeated within software is generally considered best practice.</li>
<li><a href="#page-titled">2.4.2 Page Titled</a> — Where the software is part of a product that provides a single function, or has a menu-driven interface, the intent of this success criterion would be met without needing an explicit title.</li>
<li><a href="#link-purpose-in-context">2.4.4 Link Purpose (In Context)</a> — This success criterion relies upon text and context being made available in a programmatically determinable form.</li>
<li><a href="#multiple-ways">2.4.5 Multiple Ways</a> — The WCAG2ICT interpretation of this success criterion replaces "set of Web pages" with "set of software programs." Such sets, particularly in the context of closed functionality software, are exceedingly rare. There are a number of notes in the section <a href="#applying-sc-2-4-5-multiple-ways-to-non-web-documents-and-software">Applying SC 2.4.5 Multiple Ways to Non-Web Documents and Software</a> that are applicable to closed functionality software.</li>
<li><a href="#multiple-ways">2.4.5 Multiple Ways</a> — The WCAG2ICT interpretation of this success criterion replaces "set of Web pages" with "set of software programs". Such sets, particularly in the context of closed functionality software, are exceedingly rare. There are a number of notes in the section <a href="#applying-sc-2-4-5-multiple-ways-to-non-web-documents-and-software">Applying SC 2.4.5 Multiple Ways to Non-Web Documents and Software</a> that are applicable to closed functionality software.</li>
<li><a href="#focus-visible">2.4.7 Focus Visible</a> — Presumes that there is a mode of operation where focus can be moved and controlled by keyboard. Some closed systems may offer tactilely discernible input such as a numeric keypad or other functional groups of keys, but do not offer any mechanism for conveying focus because the user interface is designed not to need that. For example, the keys are used to select options from a spoken menu rather than to move an onscreen focus element between multiple options. In this case, there is no concept of focus, thus there is no need for a visible indicator and this success criterion would be satisfied.</li>
<li><a href="#pointer-cancellation">2.5.2 Pointer Cancellation</a> — As noted in the section <a href="#applying-sc-2-5-2-pointer-cancellation-to-non-web-documents-and-software">Applying SC 2.5.2 Pointer Cancellation to Non-Web Documents and Software</a>, examples of ‘essential’ functionality are features for meeting environmental energy usage requirements (like waking a device from sleep, power saver mode, and low power state).</li>
<li><a href="#label-in-name">2.5.3 Label in Name</a> — Requires information in a programmatically determinable form; specifically, the programmatic name contains the text of the visual label.</li>
Expand Down

0 comments on commit 8106d62

Please sign in to comment.