this post was submitted on 29 Jan 2026
0 points (50.0% liked)

Blind Main

592 readers
5 users here now

The main community at rblind.com, for discussion of all things blindness.

You can find the rules for this community, and all other communities we run, here: https://ourblind.com/comunity-guidelines/ Lemmy specifics: By participating on the rblind.com Lemmy server, you are able to participate on other communities not run, controlled, or hosted by us. When doing so, you are expected to abide by all of the rules of those communities, in edition to also following the rules linked above. Should the rules of another community conflict with our rules, so long as you are participating from the rblind.com website, our rules take priority. Should we receive complaints from other instances or communities that you are repeatedly, knowingly, and maliciously breaking there rules, we may take moderator action against you, even if your posts comply with all of the rblind.com rules linked above.

founded 2 years ago
MODERATORS
 

@doubletap I'm listening to today's episode ("The Best NVDA Add-ons and Keyboard Tricks You Need") and really enjoyed the discussion around #NVDA workflows and keyboard customisation. I smiled when one of you mentioned struggling to remap an Applications key on a Keychron, because I ran into exactly the same issue after buying my Keychron shortly after Christmas.
What finally worked for me was not using the Menu / Applications keycode directly at all. Even though it's exposed in the Keychron Launcher, it didn't actually do anything reliably on Windows with NVDA.
Instead, I created a macro for Shift+F10, which is the standard Windows keyboard equivalent for the context menu and is very screen-reader friendly. In the Keychron Launcher, I went to Macro, selected a macro slot, chose Start Recording, pressed Shift+F10, stopped recording, and then assigned that macro to the key I wanted.
One important gotcha I ran into: the launcher shows what look like “duplicate” key entries in the macro (for example multiple F10s or Shift appearing twice). Those aren't mistakes. They're the key-down and key-up events. If you delete them, you can end up with Shift getting stuck. Leaving the macro exactly as recorded solved that for me.
Once I did this, the key worked reliably everywhere I’ve tried it, like File Explorer, browsers, and with NVDA, and it's honestly been more dependable than trying to use the Applications key directly. Thought I'd share in case it helps others listening to this episode or experimenting with Keychron keyboards.
#ScreenReader #Accessibility #Blind #keyboard @mastoblind @main

top 3 comments
sorted by: hot top controversial new old
[–] doubletap@tweesecake.social 1 points 15 hours ago (1 children)

@RareBird15 @mastoblind @main Can I just ask, how did you stop the recording on the macro?

[–] RareBird15@allovertheplace.ca 1 points 15 hours ago

@doubletap @mastoblind @main If I remember right, I just hit space on the button. It didn't seem to count arrow key movements or space. I think I might have even left the focus on the button for starting and stopping recording so all I had to do was press the spacebar.

[–] doubletap@tweesecake.social 1 points 1 day ago

@RareBird15 @mastoblind @main Thanks for this. This is really useful info. And I’m glad you enjoyed the chat.