Client Keyboard Nav Paths

[ninavizz]

This is a sub-task within #18

---

Problem

When a journalist is using the Qubes Workstation and they want to navigate the Client with keyboard-keys only, what will that look like as a clickthrough of focus-states?

Considerations

Not exactly sure what the easiest, available, or best way(s) to code focus states are, in QT. Wd be good to discuss at some point soon... I certainly have ideas, but wd love to discuss with dev.

I typically spec "Focus States" as some variation of border styling across elements, with square or rounded-corner-square 'highlights' around complex shapes (such as stars or 'more' menus) but am also unsure what options might be for the toggle-paths. /cc @eloquence @creviera @redshiftzero

Acceptance Criteria

• Clickable wireframe demonstrating interactivity
• Mockup(s) demonstrating VisDe treatment

[ninavizz]

@redshiftzero @eloquence @creviera Hey gang — question: How much work is it in QT to create keyboard nav paths (not shortcuts, but tab-tab-tab-tab-return-type-tab-return type paths)? These are really important for accessibility, but also for any B2B or enterprise app. Most users expect this, and when asked a few Newsroom customers have responded favorably to this as meeting their current nav habits.

My hunch is that this is now laughably out of scope for Beta—especially since many of the other features and other visual UI things, are also marginally within scope... and it's important for this to have parity with that.