Implement mappings for popover hint#2717
Conversation
✅ Deploy Preview for wai-aria ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
🚀 Deployed on https://deploy-preview-2717--wai-aria.netlify.app |
jnurthen
requested review from
aardrian,
cookiecrook,
scottaohara and
smhigley
| <tr> | ||
| <th><a href="https://developer.apple.com/reference/appkit/nsaccessibility">AX</a></th> | ||
| <td> | ||
| <div class="general">Use WAI-ARIA mapping</div> |
There was a problem hiding this comment.
May need something else here depending on the outcome of https://webkit.org/b/306041
| </p> | ||
| </section> | ||
| <section> | ||
| <h3 id="plain-content">Plain Content</h3> |
There was a problem hiding this comment.
Is there an HTML spec concept here we can reference instead? This overlaps the similar concept of block/flow content in a way that leaves ambiguity in my understanding of your intention.
There was a problem hiding this comment.
For example, images aren't always plain, as in the context of an animated SVG. Nor can an image (not even a bitmap) be referenced as plaintext, unless you bring in another concept like an object replacement character. This seems to blur the line, esp re: attributed strings and other similar rich text concepts like Flow contents.
There was a problem hiding this comment.
No this is somewhat of an ARIA semantic. At least in Chrome and how I've also implemented this in Firefox is to iterate over the popover & it's descendants and determine if the role matches.
I don't know if the heuristic is worth changing or the spec doesn't properly express this idea, but I am open to suggestions.
There was a problem hiding this comment.
May need something else here depending on the outcome of https://webkit.org/b/271485 and https://webkit.org/b/306041
| <!-- accessibility sibling will be defined in the ARIA specification --> | ||
| </ul> | ||
| <p> | ||
| Author-provided `aria-describedby` or `aria-details` attributes on the invoking element take precedence over these implicit relations. |
There was a problem hiding this comment.
we may want to mention that even if they resolve to the empty string or result in no associated details relation (e.g., aria-details="").
i remember talking a lot about this with aaron, and how to allow for people to opt out of an automatic description/details relation, if they needed to.
this comment applies to other instances of this text in this PR
|
Discussed today: https://www.w3.org/2026/02/12-aria-minutes.html#630f Conclusions:
|
5 participants
🚀 Netlify Preview:
🔄 this PR updates the following sspecs: