aria
aria copied to clipboard
[core-aam PR 230] Update aria-labelledby AXAPI mapping to use AXTitle
Copies w3c/core-aam#230 by @rahimabdi
Closes https://github.com/w3c/core-aam/issues/215
Include co-author when merging.
Deploy Preview for wai-aria ready!
| Name | Link |
|---|---|
| Latest commit | 773f9d25c1deeddc376393675430205814504aa5 |
| Latest deploy log | https://app.netlify.com/sites/wai-aria/deploys/67e5c816ffa98c00082a735f |
| Deploy Preview | https://deploy-preview-2199--wai-aria.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Hello @spectranaut!
- This looks good, but from the issue, it looks like aria-label is updated to AXTitle as well, where you doing that in a separate PR? Seems to me like it could be done here as well.
Agreed (thank you), I've updated the PR to include both aria-label/aria-labelledby.
- Can you confirm whether there will need to be a change in firefox and chrome? Seems like it! if so we need to track those implementations.
No change is required for implementations, so related API tests should be crafted to allow either attribute. Although AXTitle is now the recommended AXAPI mapping for aria-label/aria-labelledby, engines may still use the legacy AXDescription attribute. James and I do not believe the older alternative needs to be documented by an evergreen spec.
@spectranaut May we close this PR out if you have no further concerns? Thank you!
Does VoiceOver and friends still make a distinction between AXTitle and AXDescription? Is this change already in Safari?
Trying to gauge how safe it is to throw out AXDescription in Firefox since it is a headache and something we don't want to invest more time in.
@eeejay VO Eng manager confirmed it's fine to use AXTitle exclusively in implementations.
@cookiecrook thanks. How far back has this been true in VO? Are there versions still in use that require AXDescription?