- From: Matthew Tylee Atkinson <notifications@github.com>
- Date: Wed, 29 Oct 2025 08:53:30 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1152/3462385327@github.com>
matatk left a comment (w3ctag/design-reviews#1152) 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. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1152#issuecomment-3462385327 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1152/3462385327@github.com>
Received on Wednesday, 29 October 2025 15:53:34 UTC