-
Notifications
You must be signed in to change notification settings - Fork 125
Commit
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -10308,17 +10308,10 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2> | |
<p>[ARIA 1.1] Defines a human-readable, author-localized description for the <a>role</a> of an <a>element</a>.</p> | ||
<p>Some <a>assistive technologies</a>, such as screen readers, present the role of an element as part of the user experience. Such assistive technologies typically localize the name of the role, and they may customize it as well. Users of these assistive technologies depend on the presentation of the role name, such as "region," "button," or "slider," for an understanding of the purpose of the element and, if it is a widget, how to interact with it.</p> | ||
<p>The <code>aria-roledescription</code> property gives authors the ability to override how assistive technologies localize and express the name of a role. Thus inappropriately using <code>aria-roledescription</code> may inhibit users' ability to understand or interact with an element. Authors SHOULD limit use of <code>aria-roledescription</code> to clarifying the purpose of non-interactive container roles like <rref>group</rref> or <rref>region</rref>, or to providing a <em>more specific</em> description of a <rref>widget</rref>.</p> | ||
<p> When using <code>aria-roledescription</code>, authors SHOULD also ensure that:</p> | ||
<ol> | ||
<li>The element to which <code>aria-roledescription</code> is applied has a valid <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> role or has an implicit WAI-ARIA role semantic.</li> | ||
<li>The value of <code>aria-roledescription</code> is not empty or does not contain only whitespace characters.</li> | ||
</ol> | ||
<p>User agents MUST NOT expose the <code>aria-roledescription</code> property if any of the following conditions exist:</p> | ||
<ol> | ||
<li>The element to which <code>aria-roledescription</code> is applied does not have a valid WAI-ARIA role or does not have an implicit WAI-ARIA role semantic.</li> | ||
<li>The value of aria-roledescription is empty or contains only whitespace characters.</li> | ||
</ol> | ||
<p><a>Assistive technologies</a> SHOULD use the value of <code>aria-roledescription</code> when presenting the role of an element, but SHOULD NOT change other functionality based on the role of an element that has a value for <code>aria-roledescription</code>. For example, an assistive technology that provides functions for navigating to the next <rref>region</rref> or <rref>button</rref> SHOULD allow those functions to navigate to regions and buttons that have an <code>aria-roledescription</code>.</p> | ||
<p>User agents MUST NOT expose the <code>aria-roledescription</code> attribute if the value of aria-roledescription is empty or contains only whitespace characters.</p> | ||
<p>If <code>aria-roledescription</code> is applied to a generic or semantically <em>meaningless</em> presentational element (for example, <code>div</code> or <code>span</code> in HTML), user agents SHOULD NOT expose <code>aria-roledescription</code> unless the author also defines an explicit WAI-ARIA role value.</li> | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
cookiecrook
Author
Contributor
|
||
<p>If <code>aria-roledescription</code> is applied to a semantically <em>meaningful</em> host language element whose implicit role semantic is not defined by WAI-ARIA, user agents SHOULD expose <code>aria-roledescription</code>, even if the author does not provide an explicit WAI-ARIA role value.</li> | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
cookiecrook
Author
Contributor
|
||
<p><a>Assistive technologies</a> SHOULD use the value of <code>aria-roledescription</code> when presenting the role of an element, but SHOULD NOT change other functionality based on the role of an element that has a value for <code>aria-roledescription</code>. For example, an assistive technology that provides functions for navigating to the next <rref>region</rref> or <rref>button</rref> would allow those functions to navigate to regions and buttons that have an <code>aria-roledescription</code>.</p> | ||
<p>The following two examples show the use of <code>aria-roledescription</code> to indicate that a non-interactive container is a "slide" in a web-based presentation application.</p> | ||
<pre class="example highlight"><div role="region" aria-roledescription="slide" id="slide42" aria-labelledby="slide42heading"> | ||
<h1 id="slide42heading">Quarterly Report</h1> | ||
|
1 comment
on commit b6d1810
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we can take this up again now we have the generic role
I'm ok with this, but I have a couple of concerns:
So, IF we can come up with a definition of "semantically meaningless" (or come up with an alternative phrase, list of elements, or something which makes it 100% clear which elements we're talking about), would you be ok with turning the SHOULD NOT into a MUST NOT?