@matatk friendly ping as it's been a month since this was filed, but looks like this is getting attention, so thanks! Please let me know if you have any questions, if something isn't clear, etc. happy to fill in the gaps! Thanks again!

Hi @janewman. Thanks for your review request, and sorry for my slow reply. We have discussed this in some TAG calls, and also in a couple of Accessible Platform Architectures WG calls. My comment here is aimed at gathering a bit of information before TAG can come to consensus. Also many thanks to @AutoSponge for contributing many of the below questions on your proposal.

First of all: this is neat! It's a clear pain point for devs and users, and your proposed solution looks great. The explainer is well written. There are some things that we'd like some clarification on, though...

1. Orientation of certain types of construct, and aria-orientation don't seem to be mentioned - is orientation something the group considered?

2. Is there a reason why tree and treegrid controls are not mentioned? (grid is mentioned as future work)

3. Do you intend that the behavior tokens will always have the same names as their ARIA role counterparts?

4. Do you foresee adding anything that is not currently covered by ARIA?

Again I really liked this proposal. I'm also pleased that applying behaviours via CSS is not in scope for this proposal, as I'm concerned about the possibility for author error to make huge changes to the way pages work, without it being obvious to the author.

Thanks for your time, and in advance for info you may have on the above.