- From: Matthew Tylee Atkinson <notifications@github.com>
- Date: Mon, 05 Jan 2026 09:02:01 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/1152/3711298217@github.com>
matatk left a comment (w3ctag/design-reviews#1152) Thanks for your clear and comprehensive reply, @janewman - this sounds good. Just one point I'd like to clarify regarding question 1, about orientation. I think I wasn't clear in my question (sorry about that), and that you've answered "will focusgroup affect the exposed `aria-orientation` attribute value?" - but I was meaning to ask "will focusgroup be affected by the given `aria-orientation` attribute value?" Your answer, plus your reminders of the relevant parts of the explainer, do answer my question though - by default, both axes of arrow keys will respond, and the author can limit that to the `inline` or `block` axis as desired. It also seems that the value of `aria-orientation` is _not_ influential in any way (though the `role` of controls may be). If I'm understanding correctly, this does mean that there may be some cases where the author needs to specify both an `aria-orientation` value, and an optional `inline` or `block` constraint for the `focusgroup`, but that doesn't seem too onerous (and is consistent with the rest of how `focusgroup` works). tl;dr: Again this all sounds reasonable. It will be great to see this feature come to the web! -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/1152#issuecomment-3711298217 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/1152/3711298217@github.com>
Received on Monday, 5 January 2026 17:02:05 UTC