Improve keyboard navigation with KP_BEGIN and KP_END #2865

New issue

Closed

opened 2026-02-20 22:13:54 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-20 22:13:54 -05:00

Owner

Originally created by @Hartmnt on GitHub (Jun 24, 2024).

Originally assigned to: @Hartmnt on GitHub.

Description

In #5984 the accessibility of the entire application was overhauled. Mumble was made keyboard navigable. However, I failed to notice that KP_BEGIN and KP_END were also used by screen reader users for keyboard navigation.

Thanks to user squeaktoy for bringing this to my attention: https://github.com/mumble-voip/mumble/pull/5984#issuecomment-2123446439

We need to go through all UI elements and see how they react to pressing KP_BEGIN and KP_END (or "Home" and "End")

Mumble version

1.5.634

Mumble component

Client

Reproducible?

Yes

Originally created by @Hartmnt on GitHub (Jun 24, 2024). Originally assigned to: @Hartmnt on GitHub. ### Description In #5984 the accessibility of the entire application was overhauled. Mumble was made keyboard navigable. However, I failed to notice that ``KP_BEGIN`` and ``KP_END`` were also used by screen reader users for keyboard navigation. Thanks to user squeaktoy for bringing this to my attention: https://github.com/mumble-voip/mumble/pull/5984#issuecomment-2123446439 We need to go through all UI elements and see how they react to pressing ``KP_BEGIN`` and ``KP_END`` (or "Home" and "End") ### Mumble version 1.5.634 ### Mumble component Client ### Reproducible? Yes

deekerman

2026-02-20 22:13:54 -05:00

closed this issue
added the
client

bug

accessibility
labels

deekerman commented

2026-02-20 22:13:56 -05:00

Author

Owner

@squeaktoy commented on GitHub (Jun 25, 2024):

I did notice that KP_BEGIN works differently on Windows/NVDA than it does on Linux/Orca. On Orca it reads out useless info while on NVDA it does read what you would get if you focus the element through regular navigation.

@squeaktoy commented on GitHub (Jun 25, 2024): I did notice that `KP_BEGIN` works differently on Windows/NVDA than it does on Linux/Orca. On Orca it reads out useless info while on NVDA it does read what you would get if you focus the element through regular navigation.