Frank Elavsky

> This is incredibly valuable feedback. Thank you @frankelavsky. You bet, happy to hear that. Thanks for adding the write-up here @domoritz. I'll do my best to respond to any...

Just hopping in here to agree with @majornista that avoiding tedious navigation would be ideal. It might be worth considering (down the road) some kind of abstract interaction layer that...

Yeah, sounds like a good strategy for now is: 1. reasonable defaults for most use cases 2. guardrails against bad authoring possibilities 3. (distant goal) expressiveness and control for the...

Thanks David! I think some of the cool things about this are also totally open to design critique, as they may not always be a good choice: - placing the...

There is an ongoing [discussion over in aria](https://github.com/w3c/aria/issues/991#issuecomment-2147964294) about how best to structure data visualizations, and I think that this idea you've proposed @AdamSobieski actually goes even further than charts...

While this PR isn't ready to be merged, what I hope for is some feedback on the general approach before populating the prototype's approach across all other visualization types. Right...

@marshallpete sounds good and thanks! Note that I recommend entering the chart via keyboard. It'll show a big group indicator and `comma`-`period`goes between high level groups. These are visually all...

> The data navigator will need to include both the focused element and any item before or after it in the navigation order, so that as the user swipes to...

Just a reflection of the coding to-dos before this will be hand-off ready: - [x] Limit navigation to 2 dimensions (up/down, left/right) plus drill in/out (@frankelavsky) - [ ] Add...

> Ok I think I added all the needed focus rings as well as the signals and calls to control them. It aint pretty but we are in POC mode....