Skip to content

unit selection using Tab key [bounty: 16 XTR] #2697

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

Open
emna9 opened this issue Apr 24, 2025 · 3 comments
Open

unit selection using Tab key [bounty: 16 XTR] #2697

emna9 opened this issue Apr 24, 2025 · 3 comments
Labels
bounty Some amount of our token, XatteR, is offered coding This issue requires some programming input Deals with hotkeys, interaction & accessibility
Milestone

Comments

@emna9
Copy link
Contributor

emna9 commented Apr 24, 2025

When selecting units , navigation can only be done using the arrow keys (← ↑ ↓ →). The Tab key does not cycle through available units, which is expected behavior for accessibility and smoother keyboard navigation.

Steps to reproduce the behavior:

Launch the game

Go to unit selection screen

Press Tab or Shift + Tab

Nothing happens

Expected behavior
Tab should move the focus to the next unit in the list
Shift + Tab should move the focus backward

Desktop:

  • OS: Windows 11, Arch Linux
  • Browser: Firefox
  • Version: 135.0.1 (64-bit)
@DreadKnight DreadKnight added the coding This issue requires some programming label Apr 24, 2025
@DreadKnight DreadKnight added this to the 0.6 - Cyber Wolf milestone Apr 24, 2025
@DreadKnight DreadKnight changed the title Tab key does not work when selecting units , add keyboard navigation support unit selection using Tab key [bounty: 16 XTR] Apr 24, 2025
@DreadKnight DreadKnight added bounty Some amount of our token, XatteR, is offered input Deals with hotkeys, interaction & accessibility labels Apr 24, 2025
@Venkata-Sai-Vishwanath-robo

The current functionality is good enough in my opinion and might not require modification, as it aligns with both usability and accessibility best practices. Navigation between units using the arrow keys (← ↑ ↓ →) could be an intentional design choice.
This prevents users from having to tab through a potentially large number of individual unit elements, which would be inefficient and cumbersome.

This behavior is similar to how radio button groups work in accessible UI design: users use arrow keys to move between options while the entire group is treated as a single tabbable element. This minimizes the number of Tab stops and makes keyboard navigation smoother and more predictable.
https://www.w3.org/WAI/ARIA/apg/patterns/radio/

Do I get the bounty 😅? @DreadKnight

@emna9
Copy link
Contributor Author

emna9 commented May 10, 2025

Hi @Venkata-Sai-Vishwanath-robo ,
Thanks for your thoughts! While arrow keys are useful, adding Tab navigation would enhance accessibility and improve the overall user experience. Tab is a standard in many user interfaces, not just in gaming, as it allows for quicker, more efficient navigation through different elements. In games, it’s commonly used to cycle through units or menus, allowing players to move faster between selectable items, which is crucial when managing multiple elements. Beyond gaming, in software applications like email clients or web forms, Tab helps users quickly switch between fields or sections without having to manually scroll or use the mouse.
This addition would complement the arrow keys, not replace them, offering a more inclusive and streamlined experience for all players.

@yousefsassy
Copy link
Contributor

Hey @emna9 ! It would be great to have Tab and Shift + Tab cycle through units during selection. It’s a common behavior in most interfaces and would make keyboard navigation much smoother especially for accessibility. A small change that could really improve the UX.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty Some amount of our token, XatteR, is offered coding This issue requires some programming input Deals with hotkeys, interaction & accessibility
Projects
None yet
Development

No branches or pull requests

4 participants