Get Accessibility Properties#1960
Conversation
| <tr> | ||
| <td><dfn>no such accessible</dfn> | ||
| <td>404 | ||
| <td><code>no such accessible</code> |
There was a problem hiding this comment.
Unless we’re trying to match existing precedent for this “no such” phrasing, I’d prefer:
| <td><code>no such accessible</code> | |
| <td><code>accessible node not found</code> |
There was a problem hiding this comment.
Or if people really want to keep the precedent, let’s call it “no such accessible node” rather than “no such accessible”
| <tr> | ||
| <td><dfn>stale accessible reference</dfn> | ||
| <td>404 | ||
| <td><code>stale accessible reference</code> |
There was a problem hiding this comment.
Do we have confidence that the implementations will retain the difference between “was here but is now stale” and “not found for some other reason”? If not, the first 404 may suffice.
|
|
||
| <p> An <dfn>accessibility ID</dfn> is a string value representing a handle to an <a>accessible object</a> in a specific WebDriver session. | ||
|
|
||
| <p> <dfn>Accessibility properties</dfn> is a JSON <a>Object</a> that contains the relevant <a>WAI-ARIA states and properties</a> of an <a>accessible object</a>, as well as the following properties: |
There was a problem hiding this comment.
Not to downgrade ARIA, but it’s a subset here:
| <p> <dfn>Accessibility properties</dfn> is a JSON <a>Object</a> that contains the relevant <a>WAI-ARIA states and properties</a> of an <a>accessible object</a>, as well as the following properties: | |
| <p> <dfn>Accessibility properties</dfn> is a JSON <a>Object</a> that contains the relevant <a>accessibility properties</a> of an <a>accessible object</a>, as well as the following properties: |
|
|
||
| <dl> | ||
| <dt>"<code>accessibilityId</code>" | ||
| <dd>The <a>accessibility ID</a> of this <a>accessible object</a>. |
| <dd>The <a>accessibility ID</a> of the parent of this <a>accessible object</a> in the <a>accessibility tree</a>, including <a>ignored accessible objects</a>. | ||
|
|
||
| <dt>"<code>children</code>" | ||
| <dd>A list of <a>accessibility IDs</a> representing the children of this <a>accessible object</a> in the <a>accessibility tree</a>, including <a>ignored accessible objects</a>. |
There was a problem hiding this comment.
| <dd>A list of <a>accessibility IDs</a> representing the children of this <a>accessible object</a> in the <a>accessibility tree</a>, including <a>ignored accessible objects</a>. | |
| <dd>A list of <a>accessibility IDs</a> representing the child nodes of this <a>accessible node</a> in the implementation’s <a>accessibility tree</a>. |
| <dd>A list of <a>accessibility IDs</a> representing the children of this <a>accessible object</a> in the <a>accessibility tree</a>, including <a>ignored accessible objects</a>. | ||
| </dl> | ||
|
|
||
| <p> <dfn>Ignored accessible objects</dfn> are accessible objects that represent <a>elements which are excluded from the accessibility tree</a>. The <a>accessibility properties</a> of these <a>accessible objects</a> must only have the keys <va>accessibilityID</var>, <va>parent</var>, <va>children</var> and <va>role</var> set to <code>"none"</code>. |
There was a problem hiding this comment.
Ignored accessible children may not be implementable as written. The “ignored” state is usually on the non-accessibility rendered object which can—module implementation details—result in no backing accessibility node to return in the child list.
| <p>To <dfn>get a known accessible object</dfn> given <var>session</var> and <var>reference</var>: | ||
|
|
||
| <ol class="algorithm"> | ||
| <li><p>TO DO: Should we create a parallel to the specification of <a>get a known element</a>? Do we need to make a parallel structure to <a>browsing context group node map</a> and <a>node id map</a>? |
There was a problem hiding this comment.
I don’t think we need it, unless the element ID can’t be returned in the property bag.
| </ol> | ||
|
|
||
| <section> | ||
| <h3><dfn>Get Accessibility Properties for Accessible Object</dfn></h3> |
| <p>The following terms are defined | ||
| in the Accessible Rich Internet Applications (WAI-ARIA) 1.2 specification: [[wai-aria-1.2]] | ||
| <ul> | ||
| <li><dfn><a href="https://w3c.github.io/aria/#dfn-accessible-object"></a>accessible object</dfn> |
There was a problem hiding this comment.
Maybe we should sync an ARIA edit with this PR?
| <li><dfn><a href="https://w3c.github.io/aria/#accessibility_tree">accessibility tree</a></dfn> | ||
| <li><dfn><a href="https://w3c.github.io/aria/#tree_exclusion">elements which are excluded from the accessibility tree</a></dfn> | ||
| <li><dfn><a href="https://w3c.github.io/aria/#introroles">WAI-ARIA role</a></dfn> | ||
| <li><dfn><a href="https://w3c.github.io/aria/#introstates">WAI-ARIA states and properties</a></dfn> |
There was a problem hiding this comment.
We’ll need a landing spot for the new “accessibility properties” ref above because this ARIA list is a subset.
See WICG/aom#203
Added/update sections:
To dos:
accessibility idThis change is
Preview | Diff