Improve tab+keyboard accesibility

[angrykoala]

The main features on Gaucho should be accessible using tab to navigate around the buttons. The style of the highlight should be in accordance with the rest of the application (and taking in account is a Desktop app)

Some things to consider:

• By default, no button should be highlighted, and they should not highlight when using the mouse, only when tabbing.
• When tabbing through a suite, the task should be selected, to show the logs/edit
• When the command input is selected in edit mode, the tab won't jump to the next element, this is a feature explicitly added, but, unless a solution is found, should be removed to improve accessibility.
• Some default highlights are disabled in the css as they didn't work properly, enable to start working on this

This is a long issue that may be split in several tasks if needed

[PhilTerz]

This is a good list. The command feature preventing tabbing in edit mode is a somewhat common issue I've seen so there may be a fix... I'll try to look into it

[angrykoala]

Thanks @PhilTerz Solving that thing in particular should be trivial, as the implementation explicitly changes that by capturing the tab event (so, basically, just removing that code).

[PhilTerz]

Okay perfect, will do that

[PhilTerz]

Submitted a PR for the command tab issue. Was playing around to see the current tab work for the rest of the app. Lots more there so I will definitely look into that this week!

[angrykoala]

This issue has been stale from some time, the basic interactions with Gaucho have changed a lot, as now (to mimic a desktop app) no highlight (except minor visual changes) is used for mouse.

The focus of this task should be in making gaucho work with just keyboard (using tabs+key shortcuts) when possible. Other accessibility improvements will have their own issue assigned