Skip to content
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

Editorial: aria-controls spec update #1996

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Editorial: aria-controls spec update #1996

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
00ed611
aria-controls spec update
scottaohara Aug 16, 2023
4f5d006
Update index.html
scottaohara Sep 29, 2023
1cd5a8d
Update index.html
scottaohara Sep 29, 2023
8963a79
Update index.html
scottaohara Oct 4, 2023
db45a39
Update index.html
scottaohara May 10, 2024
1b59637
Update index.html
scottaohara May 10, 2024
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
10 changes: 7 additions & 3 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11175,13 +11175,17 @@ <h2>Definitions of States and Properties (all aria-* attributes)</h2>
<div class="property" id="aria-controls">
<pdef>aria-controls</pdef>
<div class="property-description">
<p><a>Identifies</a> the <a>element</a> (or elements) whose contents or presence are controlled by the current element. See related <pref>aria-owns</pref>.</p>
<p>For example:</p>
<p><a>Identifies</a> the <a>element</a> (or elements) whose contents or presence are controlled by the current element or composite widget. See related <pref>aria-details</pref>.</p>
scottaohara marked this conversation as resolved.
Show resolved Hide resolved
scottaohara marked this conversation as resolved.
Show resolved Hide resolved
<p>The <code>aria-controls</code> property is for referencing elements which are modified through user interaction of the current element or composite widget the user is interacting with. The presense of <code>aria-controls</code> enables <a>assistive technologies</a> to make users aware of the current element's association with the controlled elements, or that an association exists for instances where the controlled element was previously in the hidden state, but through user interaction of the controlling element, the associated element has become accessible.</p>
scottaohara marked this conversation as resolved.
Show resolved Hide resolved
<p>Instance where an <code>aria-controls</code> association could be made:</p>
<ul>
<li>A table of contents tree view can control the content of a neighboring document pane.</li>
<li>A tree view representing a table of contents where choosing a treeitem updates content of a neighboring document pane.</li>
<li>A group of checkboxes can control what commodity prices are tracked live in a table or graph.</li>
<li>A tab controls the display of its associated tab panel.</li>
<li>A radio button group applies filter choices to a listing of search results.</li>
</ul>
<p>
<p>Additionally, the <code>aria-controls</code> property supports referring to multiple elements. For example, a button is pressed to highlight different instances of spelling errors in a document. A user agent MAY expose to a user that there are X number of controlled elements and allow for a mechanism to cylcle through those elements, and returning to the controlling element when the user chooses to do so.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<p>Additionally, the <code>aria-controls</code> property supports referring to multiple elements. For example, a button is pressed to highlight different instances of spelling errors in a document. A user agent MAY expose to a user that there are X number of controlled elements and allow for a mechanism to cylcle through those elements, and returning to the controlling element when the user chooses to do so.</p>
<p>Additionally, the <code>aria-controls</code> property supports referring to multiple elements. For example, a button is pressed to highlight different instances of spelling errors in a document. A user agent MAY expose to a user that there are X number of controlled elements and allow for a mechanism to cycle through those elements, and returning to the controlling element when the user chooses to do so.</p>

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And do we mean "user agent" here or "assistive technologies"?

For example:

Assistive technologies SHOULD enable users to quickly navigate to elements with role banner

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes. thank you. i had started to write the sentence based on what use agents should expose, but then drifted into what AT could provide. I'll get this corrected.

</div>
<table class="property-features">
<caption>Characteristics:</caption>
Expand Down