#1152: Incubation: Scoped Focusgroup

Visit on Github.

Opened Sep 18, 2025

Explainer

https://open-ui.org/components/scoped-focusgroup.explainer/

The explainer

Where and by whom is the work is being done?

  • GitHub repo: https://github.com/openui/open-ui
  • Primary contacts:
    • Jacques Newman (@janewman), Microsoft, Explainer author, Chromium Implementor
    • Chris Holt (@chrisdholt), Microsoft, Prior Explainer co-author
    • Leo Lee (@leolee), Microsoft, team lead
  • Organization/project driving the design: Microsoft
  • This work is being funded by: Microsoft
  • Incubation and standards groups that have discussed the design:
  • Standards group(s) that you expect to discuss and/or adopt this work when it's ready: WhatWG

Feedback so far

You should also know that...

An earlier version of this feature was proposed and resolved here: https://github.com/w3ctag/design-reviews/issues/732

<!-- Content below this is maintained by @w3c-tag-bot -->

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1152

Discussions

Log in to see TAG-private discussions.

Discussed Oct 13, 2025 (See Github)

Matthew: Think it needs a bit more work. Will have another look.

Comment by @janewman Oct 14, 2025 (See Github)

@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!

Discussed Oct 20, 2025 (See Github)

Matthew: This is really neat. Like so many things I've seen in previous career would be fixed with this. That was the general consensus in APA. We discussed yesterday and we have some questions. Or some things that could be mentioned, possibly as future work. I might put them in the thread. I will probably post directly. I plan to do that today.

Discussed Oct 27, 2025 (See Github)

Matthew asked for more info

Comment by @matatk Oct 29, 2025 (See Github)

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.