[core-aam PR 230] Update aria-labelledby AXAPI mapping to use AXTitle

[pkra]

Copies w3c/core-aam#230 by @rahimabdi

Closes w3c/core-aam#215

Browser bugs:

• Chrome: https://issues.chromium.org/issues/406819290
• Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1956960

[spectranaut]

Include co-author when merging.

[spectranaut]

Hi Rahim, this PRs has been moved, so please continue the work here :)

I have a few questions/comments for you:

1. 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.
2. 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.

[netlify]

✅ Deploy Preview for wai-aria ready!

Name	Link
🔨 Latest commit	773f9d2
🔍 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.

[rahimabdi]

Hello @spectranaut!

1. 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.

2. 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.

[rahimabdi]

@spectranaut May we close this PR out if you have no further concerns? Thank you!

[spectranaut]

Thanks for the fixes!

I just want to give the chance for you to ack or make a change re: James request.

Also, about this:

2. 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.

Interesting point... it still seems like browser ought to know about the change, an issue on the browser could say "the old way is support, but btw, you don't need to maintain that logic to separately exposing things in either AXDescription or AXTitle.

I'll make an issue on browsers when this change lands.

[eeejay]

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.

[cookiecrook]

@eeejay VO Eng manager confirmed it's fine to use AXTitle exclusively in implementations.

[eeejay]

@cookiecrook thanks. How far back has this been true in VO? Are there versions still in use that require AXDescription?