westbrookMar 6
Luke

People at OpenUI have been working on a revamped implementation of focusgroup.

Please go try it out, check it does what you expect! Provide feedback, let us know if it's broken.

I'm especially interested to know how the accessibility is for it. Thought has been put in to ensure behaviours have semantics attached.

https://developer.chrome.com/blog/focusgroup-rfc

Request for developer feedback: focusgroup  |  Blog  |  Chrome for Developers

Try out focusgroup and comment on the proposal.

Chrome for Developers
Mar 5 at 6:14pmWeb
Show threadJames ScholesMar 6
@Lukew @sundress To what extent does this go beyond what the APG asserts as required behaviours for each pattern? For example, does it implement Home and End keys for jumping to each end of a toolbar even though the APG claims those keys are optional?
Show threadLukeMar 6

@jscholes @sundress so I happened to test this yesterday and that behaviour isn't implemented right now. My feelings are it probably should be. Is it something that's conditional on the type of behaviour you select or do you think it should be the case for all of them?

https://github.com/openui/open-ui/issues/1397 - I've opened an issue to discuss it.

[Focusgroup] Should home and end keys do something? · Issue #1397 · openui/open-ui

It's not uncommon that Home + End can be used to quickly go to the first and last items within certain focusgroup patterns. For example, toolbars often have this, MDN (and APG) describe these as op...

GitHub
Show threadJames ScholesMar 6

@Lukew @sundress It wouldn't hurt to implement Home/End specifically for all of the current behaviour tokens, even if native implementations of some of them (e.g. menu) haven't historically done so.

More broadly, wherever the word "optional" appears in the APG, I tend to pretend it doesn't and treat all of the things it's attached to as required.