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
The Dragon Naturally Speaking user was confused on how to use the arrow keys to move around the map.
Here's the current behavior:
• A user can move the map using the arrow keys, but this is only possible when the keyboard focus is specifically over the map section.
• When the keyboard focus shifts to other components of the webpage, such as SVG elements or other interactive components, the ability to move the map using arrow keys is lost.
To improve the user experience, it would be helpful to implement context-aware commands that clearly indicate to the user when certain commands can and cannot be used. Alternatively, the navigation could be redesigned to allow map movement regardless of where the keyboard focus is on the page. However, this approach should be handled carefully to avoid further confusion when users intend to interact with other components.
The text was updated successfully, but these errors were encountered:
When the focus is on the controls (i.e. zoom in button, zoom out button, etc.) - we can support the use of arrow keys to work alongside tab (down or right arrow) and shift-tab (left or up arrow) to navigate the controls. Do you think this would be an appropriate improvement to make?
Similarly, the + and - keys only work when the map is focused, we can expand this to allow the use of +,- when focus is elsewhere as well.
The Dragon Naturally Speaking user was confused on how to use the arrow keys to move around the map.
Here's the current behavior:
• A user can move the map using the arrow keys, but this is only possible when the keyboard focus is specifically over the map section.
• When the keyboard focus shifts to other components of the webpage, such as SVG elements or other interactive components, the ability to move the map using arrow keys is lost.
To improve the user experience, it would be helpful to implement context-aware commands that clearly indicate to the user when certain commands can and cannot be used. Alternatively, the navigation could be redesigned to allow map movement regardless of where the keyboard focus is on the page. However, this approach should be handled carefully to avoid further confusion when users intend to interact with other components.
The text was updated successfully, but these errors were encountered: