Hey, #MechanicalKeyboard people! I just got myself a #Ducky One X wireless mechanical keyboard. As a #screenreader user who finds myself constantly running out of keyboard shortcuts, multi-level actuation sounded really exciting to me. Unfortunately, the browser-based programmer at duckyhub.io is entirely inaccessible. Apparently it uses a standard called #QMK or something? I don't build mechanical keyboards; I use them because I love the feedback, so I'm not deep enough into the hobby to know much about this. A browser-based programmer gave me hope that programming would be #accessible, but at least with the official website, that hope turned out to be false. So before I return this thing, do these standards mean there might be other software I can try to program the keyboard, to see if it's more accessible for me? #a11y#keyboard
MostlyBlindGamer
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •Programming a keyboard with QMK is basically just writing an array or three in a C file.
🇨🇦Samuel Proulx🇨🇦
in reply to MostlyBlindGamer • • •MostlyBlindGamer
in reply to 🇨🇦Samuel Proulx🇨🇦 • • •backing up a bit, do you have a source on QMK support for the One X? I couldn’t find that anywhere.
If you’re set on QMK - and you should be! - we can discuss other options.
🇨🇦Samuel Proulx🇨🇦
in reply to MostlyBlindGamer • • •🇨🇦Samuel Proulx🇨🇦
in reply to MostlyBlindGamer • • •One X Wireless
Ducky