-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle group focus highlights in scenery #708
Comments
Maybe nodes can have a group focus highlight that is made visible whenever a descendant node receives focus, handled in FocusOverlay? |
Discussed in 11/9/17 accessibility meeting. Lets discuss again at a design meeting for keyboard navigation. There are concerns that adding another focus highlight will require additional spacing for all Nodes that use this. The more complex the focus highlight is, the more space it will take up. We may not have that space for a lot of common code components. There was also concern that a "grouping" highlight wouldn't solve the problem that these kinds of UI inputs don't indicate different keyboard interaction. Perhaps that would be better solved with a different UI solution that isn't specific to a11y and keyboard navigation. |
Discussed in 11/14/17 accessibility meeting: We are going to hold off on this and not indicate element grouping with focus highlights since it paints us into a corner and we would have to make sure there is additional spacing for this in every set of grouped elements. We will handle this on a case by case basis to ensure that the interaction pattern for a group of elements is clear. Closing. |
In addition, I think we decided that this "case by case" basis may be through focusHighlight grouping, or through universal design in the sim itself, depending on what the sim needs. |
In a 12/5 a11y design meeting we decided to add this outer highlight for all radio buttons and scenery-phet/NumberControl, but there might be others in the future. I think this should be handled generally in scenery, @zepumph @mbarlow12 what do you think? |
Sounds awesome. We could have a node have a flag to mark a parent node as a group highlight.
the Panel Node can have an option Then in FocusOverlay, we just have to add a step that iterates over parent accessibleInstances and searches for groupHighlight opt ins. Perhaps we will want flexibility to customize the groupHighlight, similar to FocusHighlightPath, so potentially the option will be of type {{boolean}}, or {{node}}, or {{shape}}, or allow any of these {{boolean|node}}. |
That seems great @zepumph, thats what I was thinking as well. |
Oops, meant to reopen this. |
Initial pass done in the above commits. Right now, there is only support for a flag that enables a group focus highlight. Remaining work includes ability to pass a custom Shape or Node group focus highlight, and potentially support for multiple group focus highlights in case multiple ancestors need to show a group highlight if a node has focus. |
@jessegreenberg @zepumph Is this feature still in development at all? It seems like the GroupFocusHighlight has been working well for some time—can we close? |
Thanks @mbarlow12, yes this can be closed. I updated some documentation around this issue. The enhancements listed in #708 (comment) have not been necessary since this issue was opened and I don't want to reconsider the API until they are required for some reason. |
There is one more todo I see in Accessibility.js that applies to this issue I think. What do you think? |
The TODO is still there and is
We haven't needed this for 4 years, but it would be nice to support for completion. Doubt it is something we will get to soon. |
The next steps will be done in #1608. Closing this one since we have supported groupFocusHighlight for a long time. |
Reopening because there is a TODO marked for this issue. |
Just moved a TODO over to 1608. |
In phetsims/scenery-phet#341, we added a custom highlight around NumberControls when they have focus, so that they look something like
After a11y meeting on 11/7/17, it sounds like this kind of highlight will should be used for any grouped elements such as radio buttons, carousels, combo boxes, and menus. It would be great if scenery could generally support this.
@zepumph @mbarlow12 lets discuss this next a11y meeting.
The text was updated successfully, but these errors were encountered: