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
{{ message }}
Repository navigation
Access-key (Alt+mnemonic) navigation across primary action buttons #282
Follow-up from the "No accessibility support" cross-cutting finding in #262.
Zero access-key (AccessText/underscore-mnemonic) support exists anywhere in the app today — no AccessText usage at all. Adding it well needs its own per-view design pass, not a mechanical sweep: nearly every visible-text Button across the app's ~18 views would need a mnemonic, and several views already have multiple candidates that would collide on the same letter — e.g. MainView's command bar (ÜBERSICHT / STAMMDATEN / VERBINDEN / ÖFFNEN / NEUER EINSATZ / ÜBER).
Scope for this follow-up:
Pick mnemonics per view with manual collision resolution (not automatic/generated).
Decide whether Alt-mnemonics apply app-wide or are scoped to the highest-value primary actions first (e.g. HINZUFÜGEN/SPEICHERN buttons).
Add the underlying AccessText usage/pattern once established, and note it as a reusable idiom for future views.
Not in scope: keyboard reachability of buttons nested in DataGrid cell templates — verified separately (see #262) that Tab already reaches them in one press, so no gap there.
Moved from v0.8 to v0.11. A mnemonic is a letter of the button label, so the choice depends on the label text; once v0.11 decides how the UI is localized, every mnemonic has to be picked again per language. Choosing them before that decision means doing the work twice. It would also add a second shortcut system on top of the global shortcuts in #544, which is one more thing to learn mid-Einsatz.
One exception stays in v0.8: if the destructive ConfirmDialog button needs its own key (keyboard contract item 1 in #545), that single mnemonic is handled in #538.
Also, #537 and #543 list "are Buttons inside DataGrid cells Tab stops?" as open, while this issue says it was verified in #262. #537 will confirm it at runtime and correct whichever issue is wrong.
Confirmed in #553: Tab from the ETB grid reaches the first row button in one press (Tab_from_the_ETB_grid_reaches_its_row_buttons_in_one_press), and ForcesTabRenderTests shows the same for Forces. This issue's "not in scope" note is correct, and #537's question is answered.
Activity
DeepDiver1975 commentedon Oct 1, 2026
Moved from v0.8 to v0.11. A mnemonic is a letter of the button label, so the choice depends on the label text; once v0.11 decides how the UI is localized, every mnemonic has to be picked again per language. Choosing them before that decision means doing the work twice. It would also add a second shortcut system on top of the global shortcuts in #544, which is one more thing to learn mid-Einsatz.
One exception stays in v0.8: if the destructive ConfirmDialog button needs its own key (keyboard contract item 1 in #545), that single mnemonic is handled in #538.
Also, #537 and #543 list "are Buttons inside DataGrid cells Tab stops?" as open, while this issue says it was verified in #262. #537 will confirm it at runtime and correct whichever issue is wrong.
docs: move #282 to v0.11 and list #246 apart from the keyboard epic
docs: move #282 to v0.11 and list #246 apart from the keyboard epic (#…
DeepDiver1975 commentedon Oct 3, 2026
Confirmed in #553: Tab from the ETB grid reaches the first row button in one press (
Tab_from_the_ETB_grid_reaches_its_row_buttons_in_one_press), andForcesTabRenderTestsshows the same for Forces. This issue's "not in scope" note is correct, and #537's question is answered.