I’ve been implementing accessibility in surge. It’s going well with the 6.1 API. Awesome.
So one thing I’ve heard form our testers is that they want to ‘group’ our controls. That is, all our filter controls are in a filter section etc…
Unfortunately in our UI the controls for a particular function aren’t in a distinct rectilinear area of our UI.
So what I did to get this working was add 8 invisible components to my whole UI and then parent the sub-components to one of those 8. This works inasmuch as I get the accessible hierarchy I want. But it means I keep getting z-order bugs.
I’ve looked at the API and am not sure where I inject a ‘grouping’ parent other than an actual component in the accessibility. What I really want is for my component layout to be ‘all parented by my plugin’ but for my accesibility grouping names to have identities which have an extra logical level.
I’m already writing my own accessibility handlers but it doesn’t seem like I can figure out how to make a fake parent.
So I guess my question is: how are people generating distinct accessibility groups for components which share the same component hierarchy parent. Does this make sense?