You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<meta name="description" content="This document 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).">
<h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT)</h1>
248
-
<p id="w3c-state"><a href="https://www.w3.org/standards/types#ED">W3C Editor's Draft</a> <time class="dt-published" datetime="2025-08-19">19 August 2025</time></p>
250
+
<p id="w3c-state"><a href="https://www.w3.org/standards/types#NOTE">W3C Group Note</a> <time class="dt-published" datetime="2025-08-21">21 August 2025</time></p>
249
251
<details open="">
250
252
<summary>More details about this document</summary>
@@ -326,31 +328,20 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
326
328
To comment, file an issue in the <a href="https://github.com/w3c/wcag2ict/"><abbr title="World Wide Web Consortium">W3C</abbr> WCAG2ICT</a> GitHub repository. Create separate GitHub issues for each topic, rather than commenting on multiple topics in a single issue. It is free to create a GitHub account to file issues. If filing issues in GitHub is not feasible, send email to <a href="mailto:[email protected]">[email protected]</a> (comment archive).</p>
327
329
<p>
328
330
This document was published by the <a href="https://www.w3.org/groups/wg/ag">Accessibility Guidelines Working Group</a> as
329
-
an Editor's Draft.
330
-
</p><p>Publication as an Editor's Draft does not
331
-
imply endorsement by <abbr title="World Wide Web Consortium">W3C</abbr> and its Members. </p><p>
332
-
This is a draft document and may be updated, replaced, or obsoleted by other
333
-
documents at any time. It is inappropriate to cite this document as other
<a href="https://www.w3.org/policies/patent-policy/#sec-Disclosure">section 6 of the <abbr title="World Wide Web Consortium">W3C</abbr> Patent Policy</a>.
353
-
340
+
Policy</a>
341
+
does not carry any licensing requirements or commitments on this
342
+
document.
343
+
344
+
354
345
</p><p>
355
346
This document is governed by the
356
347
<a id="w3c_process_revision" href="https://www.w3.org/policies/process/20250818/">18 August 2025 <abbr title="World Wide Web Consortium">W3C</abbr> Process Document</a>.
@@ -2024,7 +2015,7 @@ <h1 id="title" class="title">Guidance on Applying WCAG 2 to Non-Web Information
2024
2015
2025
2016
<div class="note" role="note" id="wcag-noteissue-container-generatedID--26"><div role="heading" class="note-title marker" id="wcag-noteh-note--26" aria-level="5"><span>Note 1</span></div><p class="">This success criterion should be considered as always satisfied for any content using HTML or XML.</p></div>
<p>Since this criterion was written, the HTML Living Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs. [<cite><a href="https://www.w3.org/TR/WCAG21/#bib-html" title="HTML Standard">HTML</a></cite>]</p>
2029
2020
2030
2021
<p>Although the HTML standard treats some of these cases as non-conforming for authors, it is considered to "allow these features" for the purposes of this success criterion because the specification requires that user agents support handling these cases consistently. In practice, this criterion no longer provides any benefit to people with disabilities in itself.</p>
0 commit comments