Skip to content

Commit

Permalink
prevent use of aria-hidden=true on document root elements (#1880)
Browse files Browse the repository at this point in the history
SHA: 951479e
Reason: push, by jnurthen

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
  • Loading branch information
scottaohara and github-actions[bot] committed Dec 11, 2024
1 parent b1c5f54 commit 0a7bc50
Showing 1 changed file with 9 additions and 8 deletions.
17 changes: 9 additions & 8 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -306,16 +306,16 @@
"aliasOf": "WAI-ARIA-1.1"
}
},
"publishISODate": "2024-12-09T00:00:00.000Z",
"generatedSubtitle": "W3C Editor's Draft 09 December 2024"
"publishISODate": "2024-12-11T00:00:00.000Z",
"generatedSubtitle": "W3C Editor's Draft 11 December 2024"
}</script>
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/2021/W3C-ED">
<link rel="stylesheet" media="(prefers-color-scheme: dark)" href="https://www.w3.org/StyleSheets/TR/2021/dark.css"></head>
<body class="h-entry" data-cite="dom accname-1.2 core-aam-1.2 infra HTML"><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">Accessible Rich Internet Applications (WAI-ARIA) 1.3</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-12-09">09 December 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-12-11">11 December 2024</time></p>
<details open="">
<summary>More details about this document</summary>
<dl>
Expand Down Expand Up @@ -12037,10 +12037,11 @@ <h4><span class="state-name" title="aria-hidden" aria-describedby="desc-aria-hid
<div class="state-description" id="desc-aria-hidden" role="definition">
<p><a href="#dfn-indicates" class="internalDFN" data-link-type="dfn" id="ref-for-dfn-indicates-11">Indicates</a>, when set to <code>true</code>, that an <a data-link-type="dfn" href="https://dom.spec.whatwg.org/#concept-element">element</a> and its entire subtree are hidden from assistive technology, regardless of whether it is visibly rendered.</p>
<p>User agents determine an element's <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-3">hidden</a> status based on whether it is rendered, and the rendering is usually controlled by <abbr title="Cascading Style Sheets">CSS</abbr>. For example, an element whose <code>display</code> property is set to <code>none</code> is not rendered. An element is considered <a data-link-type="dfn|abstract-op" href="#dfn-hidden" class="internalDFN" id="ref-for-dfn-hidden-4">hidden</a> if it, or any of its ancestors are not rendered or have their <code>aria-hidden</code> attribute value set to <code>true</code>.</p>
<p>Authors <em class="rfc2119">MAY</em>, with caution, use aria-hidden to hide visibly rendered content from assistive technologies <em>only</em> if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing redundant or extraneous content. Authors using aria-hidden to hide visible content <em class="rfc2119">MUST</em> ensure that identical or equivalent meaning and functionality is exposed to assistive technologies.</p>
<div class="note" role="note" id="issue-container-generatedID-52"><div role="heading" class="note-title marker" id="h-note-52" aria-level="4"><span>Note</span></div><p class="">Authors are advised to use extreme caution and consider a wide range of disabilities when hiding visibly rendered content from assistive technologies. For example, a sighted, dexterity-impaired individual might use voice-controlled assistive technologies to access a visual interface. If an author hides visible link text "Go to checkout" and exposes similar, yet non-identical link text "Check out now" to the accessibility <abbr title="application programming interface">API</abbr>, the user might be unable to access the interface they perceive using voice control. Similar problems can also arise for screen reader users. For example, a sighted telephone support technician might attempt to have the blind screen reader user click the "Go to checkout" link, which they might be unable to find using a type-ahead item search ("Go to…").</p></div>
<p>Authors <em class="rfc2119">MUST NOT</em> use <code>aria-hidden</code> to hide the root element or the host language element that <a href="https://html.spec.whatwg.org/multipage/dom.html#represents">represents</a> the contents of the primary document in view. For instance, the <code>html</code> or <code>body</code> elements in an <abbr title="Hypertext Markup Language">HTML</abbr> document. Authors <em class="rfc2119">MAY</em>, with caution, use <code>aria-hidden</code> to hide visibly rendered content from assistive technologies <em>only</em> if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing redundant or extraneous content. Authors using <code>aria-hidden</code> to hide visible content from screen readers <em class="rfc2119">MUST</em> ensure that identical or equivalent meaning and functionality is exposed to assistive technologies.</p>
<div class="note" role="note" id="issue-container-generatedID-52"><div role="heading" class="note-title marker" id="h-note-52" aria-level="4"><span>Note</span></div><p class="">Authors are advised to use extreme caution and consider a wide range of disabilities when hiding visibly rendered content from assistive technologies. For example, a sighted, dexterity-impaired individual might use voice-controlled assistive technologies to access a visual interface. If an author hides visible link text "Go to checkout" and exposes similar, yet non-identical link text "Check out now" to the accessibility <abbr title="application programming interface">API</abbr>, the user might be unable to access the interface they perceive using voice control software. Similar problems can also arise for screen reader users. For example, a sighted telephone support technician might attempt to have the blind screen reader user click the "Go to checkout" link, which they might be unable to find using a type-ahead item search ("Go to…"), since that text would have been hidden by the use of the attribute.</p></div>
<div class="note" role="note" id="issue-container-generatedID-53"><div role="heading" class="note-title marker" id="h-note-53" aria-level="4"><span>Note</span></div><p class="">As of <abbr title="Accessible Rich Internet Applications">ARIA</abbr> 1.3, <code><a href="https://w3c.github.io/aria/#aria-hidden" class="state-reference"><code>aria-hidden</code></a>="false"</code> is now synonymous with <code>aria-hidden="undefined"</code>.</p></div>
<div class="note" role="note" id="issue-container-generatedID-54"><div role="heading" class="note-title marker" id="h-note-54" aria-level="4"><span>Note</span></div><p class="">The original intent for <code>aria-hidden="false"</code> was to allow user agents to expose content that was otherwise hidden from the accessibility tree. However, due to ambiguity in the specification and inconsistent browser support for the <code>false</code> value, the original intent is no longer supported.</p></div>
<p>To prevent authors erroneously hiding entire window-rendered documents only to those using assistive technology, user agents <em class="rfc2119">MUST NOT</em> expose the hidden state to assistive technologies if it is specified on the root element or the host language element that <a href="https://html.spec.whatwg.org/multipage/dom.html#represents">represents</a> the contents of the primary document in view. For instance, the <code>html</code> or <code>body</code> elements in an <abbr title="Hypertext Markup Language">HTML</abbr> document, or the root <code>svg</code> element if it is rendered as its own primary document in the browser window. If authors were to specify <code>aria-hidden="true"</code> on the opening tag for an embedded document, for instance on a <code>math</code> or <code>svg</code> embedded within an <abbr title="Hypertext Markup Language">HTML</abbr> document, user agents would still be expected to hide these elements from assistive technologies.</p>
</div>
<table class="state-features">
<caption>Characteristics:</caption>
Expand Down Expand Up @@ -14719,7 +14720,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
</dd><dt id="bib-core-aam">[CORE-AAM]</dt><dd>
<a href="https://www.w3.org/TR/core-aam-1.1/"><cite>Core Accessibility API Mappings 1.1</cite></a>. Joanmarie Diggs; Joseph Scheuhammer; Richard Schwerdtfeger; Michael Cooper; Andi Snow-Weaver; Aaron Leventhal. W3C. 14 December 2017. W3C Recommendation. URL: <a href="https://www.w3.org/TR/core-aam-1.1/">https://www.w3.org/TR/core-aam-1.1/</a>
</dd><dt id="bib-core-aam-1.2">[CORE-AAM-1.2]</dt><dd>
<a href="https://www.w3.org/TR/core-aam-1.2/"><cite>Core Accessibility API Mappings 1.2</cite></a>. Valerie Young; Alexander Surkov. W3C. 14 November 2024. W3C Candidate Recommendation. URL: <a href="https://www.w3.org/TR/core-aam-1.2/">https://www.w3.org/TR/core-aam-1.2/</a>
<a href="https://www.w3.org/TR/core-aam-1.2/"><cite>Core Accessibility API Mappings 1.2</cite></a>. Valerie Young; Alexander Surkov. W3C. 22 November 2024. W3C Candidate Recommendation. URL: <a href="https://www.w3.org/TR/core-aam-1.2/">https://www.w3.org/TR/core-aam-1.2/</a>
</dd><dt id="bib-css3-selectors">[CSS3-SELECTORS]</dt><dd>
<a href="https://www.w3.org/TR/selectors-3/"><cite>Selectors Level 3</cite></a>. Tantek Çelik; Elika Etemad; Daniel Glazman; Ian Hickson; Peter Linss; John Williams. W3C. 6 November 2018. W3C Recommendation. URL: <a href="https://www.w3.org/TR/selectors-3/">https://www.w3.org/TR/selectors-3/</a>
</dd><dt id="bib-dom">[DOM]</dt><dd>
Expand All @@ -14739,7 +14740,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
</dd><dt id="bib-svg2">[SVG2]</dt><dd>
<a href="https://www.w3.org/TR/SVG2/"><cite>Scalable Vector Graphics (SVG) 2</cite></a>. Amelia Bellamy-Royds; Bogdan Brinza; Chris Lilley; Dirk Schulze; David Storey; Eric Willigers. W3C. 4 October 2018. W3C Candidate Recommendation. URL: <a href="https://www.w3.org/TR/SVG2/">https://www.w3.org/TR/SVG2/</a>
</dd><dt id="bib-uievents-key">[uievents-key]</dt><dd>
<a href="https://www.w3.org/TR/uievents-key/"><cite>UI Events KeyboardEvent key Values</cite></a>. Travis Leithead; Gary Kacmarcik. W3C. 30 May 2023. W3C Candidate Recommendation. URL: <a href="https://www.w3.org/TR/uievents-key/">https://www.w3.org/TR/uievents-key/</a>
<a href="https://www.w3.org/TR/uievents-key/"><cite>UI Events KeyboardEvent key Values</cite></a>. Travis Leithead; Gary Kacmarcik. W3C. 26 November 2024. W3C Proposed Recommendation. URL: <a href="https://www.w3.org/TR/uievents-key/">https://www.w3.org/TR/uievents-key/</a>
</dd><dt id="bib-webidl">[WEBIDL]</dt><dd>
<a href="https://webidl.spec.whatwg.org/"><cite>Web IDL Standard</cite></a>. Edgar Chen; Timothy Gu. WHATWG. Living Standard. URL: <a href="https://webidl.spec.whatwg.org/">https://webidl.spec.whatwg.org/</a>
</dd><dt id="bib-xml-names">[XML-NAMES]</dt><dd>
Expand All @@ -14748,7 +14749,7 @@ <h4><span class="property-name" title="aria-valuetext" aria-describedby="desc-ar
</section><section id="informative-references"><div class="header-wrapper"><h3 id="d-2-informative-references"><bdi class="secno">D.2 </bdi>Informative references</h3><a class="self-link" href="#informative-references" aria-label="Permalink for Appendix D.2"></a></div>

<dl class="bibliography"><dt id="bib-at-spi">[AT-SPI]</dt><dd>
<a href="https://developer-old.gnome.org/libatspi/stable/"><cite>Assistive Technology Service Provider Interface</cite></a>. The GNOME Project. URL: <a href="https://developer-old.gnome.org/libatspi/stable/">https://developer-old.gnome.org/libatspi/stable/</a>
<a href="https://gnome.pages.gitlab.gnome.org/at-spi2-core/libatspi/"><cite>Assistive Technology Service Provider Interface</cite></a>. The GNOME Project. URL: <a href="https://gnome.pages.gitlab.gnome.org/at-spi2-core/libatspi/">https://gnome.pages.gitlab.gnome.org/at-spi2-core/libatspi/</a>
</dd><dt id="bib-atk">[ATK]</dt><dd>
<a href="https://developer.gnome.org/atk/stable/"><cite>ATK - Accessibility Toolkit</cite></a>. The GNOME Project. URL: <a href="https://developer.gnome.org/atk/stable/">https://developer.gnome.org/atk/stable/</a>
</dd><dt id="bib-axapi">[AXAPI]</dt><dd>
Expand Down

0 comments on commit 0a7bc50

Please sign in to comment.