🇨🇦Samuel Proulx🇨🇦<p><span>Hey, </span><a href="https://fed.interfree.ca/tags/MechanicalKeyboard" rel="nofollow noopener noreferrer" class="hashtag" target="_blank">#MechanicalKeyboard</a><span> people! I just got myself a </span><a href="https://fed.interfree.ca/tags/Ducky" rel="nofollow noopener noreferrer" class="hashtag" target="_blank">#Ducky</a><span> One X wireless mechanical keyboard. As a </span><a href="https://fed.interfree.ca/tags/screenreader" rel="nofollow noopener noreferrer" class="hashtag" target="_blank">#screenreader</a><span> 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 </span><a href="https://fed.interfree.ca/tags/QMK" rel="nofollow noopener noreferrer" class="hashtag" target="_blank">#QMK</a><span> 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 </span><a href="https://fed.interfree.ca/tags/accessible" rel="nofollow noopener noreferrer" class="hashtag" target="_blank">#accessible</a><span>, 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? </span><a href="https://fed.interfree.ca/tags/a11y" rel="nofollow noopener noreferrer" class="hashtag" target="_blank">#a11y</a><span> </span><a href="https://fed.interfree.ca/tags/keyboard" rel="nofollow noopener noreferrer" class="hashtag" target="_blank">#keyboard</a></p>