[core-aam] add new AX API mappings for colindextext/rowindextext

[cookiecrook]

Closes w3c/core-aam#53

Test, Documentation and Implementation tracking

Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.

• "author MUST" tests: n/a
• "user agent MUST" tests:
  • not testable in WPT, so n/a
  • @spectranaut may wish to add platform mapping tests
• Browser implementations (link to issue or commit):
  • WebKit: #257142
  • Gecko: #1931415
  • Blink: #378698863
• Does this Mac-specific change need AT implementation?
  • VoiceOver change is not prioritized b/c there is not a platform equivalent
• Related APG Issue/PR: n/a
• MDN Issue/PR: n/a

[netlify]

✅ Deploy Preview for wai-aria ready!

Name	Link
🔨 Latest commit	8b86586
🔍 Latest deploy log	https://app.netlify.com/sites/wai-aria/deploys/673342bda62fc60008b9af31
😎 Deploy Preview	https://deploy-preview-2362--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.

[cookiecrook]

@twilco @minorninth FYI

[jnurthen]

@aleventhal @jcsteh @spectranaut We'd like to merge this before the CR snapshot - can we get this reviewed as soon as possible please. Thanks.

[spectranaut]

@cookiecrook it seems like this new mapping is not implemented in any other the browsers, from a quick code search?

I added the implementation tracking, because it seems like we should be doing implementation tracking for this CL. Before it lands we should have issues on the browsers to implement.

Because this still needs implementation, should it really block the CORE-AAM snapshot? Perhaps if you really want it in, we can at least make issues on the browsers before merging.

[aleventhal]

Funny you mention that, I'm working on a CL for it -- doesn't work yet:
https://chromium-review.googlesource.com/c/chromium/src/+/6012688

[cookiecrook]

doesn't work yet

Yes, it's new. So that ARIA WG doesn't have to publish a "TBD" in the spec.

[cookiecrook]

should it really block the CORE-AAM snapshot?

Otherwise I would expect it to be pulled or marked as At-Risk because this is a new feature without AT support on one platform, and without preceding vendor commitment. I outlined the concerns at:

• Reconsider whether ARIA should ship new features that have incomplete API mappings and missing AT support. #2361
• Consider listing known downstream AT support in AAMs, to avoid shipping speculative or otherwise unsupportive API mappings core-aam#238

[cookiecrook]

Perhaps if you really want it in, we can at least make issues on the browsers before merging.

I have linked the WebKit tracker and the one Aaron filed for Blink. I hesitate to file one for Gecko without acknowledgement from @jcsteh or @nmlapre that they want to do the mapping work before there is AT commitment.

[spectranaut]

I have linked the WebKit tracker and the one Aaron filed for Blink. I hesitate to file one for Gecko without acknowledgement from @jcsteh or @nmlapre that they want to do the mapping work before there is AT commitment.

Sometimes I open issues on gecko and link back to the ARIA PR when I want to get review from firefox :) Personally I think it's fine to open an issue in this case, I don't think this change is controversial and besides it is coming from the API maintainers of AX API.

[spectranaut]

Discussed in today's ARIA working group meeting: https://www.w3.org/2024/11/14-aria-minutes.html#8070

We will add this to the AAM, and open issues on browsers, as eventually, probably, VoiceOver will do something with this value.

[spectranaut]

Per working group discussion, merging.