Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Access-key (Alt+mnemonic) navigation across primary action buttons

Open
  • Is something wrong?
#282 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
accessibility

Research direction

Start by reading the related finding in #262 and inspect the app’s roughly 18 views, especially MainView’s command bar and its visible button labels. Decide whether mnemonics are app-wide or limited to primary actions, then resolve collisions per view and establish a reusable AccessText pattern. Done means the chosen buttons have usable, non-colliding Alt-mnemonics and the pattern is documented for future views.

Written by the indexing model from the issue text.

Description

help wanted ux

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.

Dominant language
C#
Stars
1
Forks
3
Avg merge
4h 34m
Merged PRs (30d)
182

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeForFire/lagebuch

All issues in CodeForFire/lagebuch

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.