You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When data features are visible, a mouseover gives a tooltip that describes what this dimension encodes.
This information is neither keyboard nor screen-reader accessible. Note that the tooltips are available on all graphs, so it would not make sense to expose them at this level of detail (you'd end up with hundreds to navigate through) but the information needs to be available in another way for both screen reader users and keyboard users.
The text was updated successfully, but these errors were encountered:
Since this seems to be the one major omission re keyboard accessibility, can you come up with a simple place to put this information?
I'll give 2 suggestions to prompt ideas...
Option 1
When features are toggled on, display a simple info dialog that introduces what data features are, and contains a bullet list (helpful semantic structure for a SR) which describes each dimension in order. Pro - simple, more discoverable than the mouseover, helpful for everyone. Con - slightly annoying to "get back to" as you'd need to toggle them off then on again
Option 2
When features are toggled on, add a keyboard-only tabbable info tooltip or button (i.e. visually hidden unless tabbed to) which allows access to this information. Pro - easy to refer back to. Con - can't work out where to put it... it would need to be after the hamburger menu for discoverability after turning data features on. It's not a column title, so doesn't belong near the other tooltips.
When data features are visible, a mouseover gives a tooltip that describes what this dimension encodes.
This information is neither keyboard nor screen-reader accessible. Note that the tooltips are available on all graphs, so it would not make sense to expose them at this level of detail (you'd end up with hundreds to navigate through) but the information needs to be available in another way for both screen reader users and keyboard users.
The text was updated successfully, but these errors were encountered: