Florian<p>I'm a <a href="https://cupoftea.social/tags/screenReader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>screenReader</span></a> user, which makes me essentially a <a href="https://cupoftea.social/tags/keyboard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>keyboard</span></a> only user with some extra spells at my disposal, but pretty much for any program I start using, if I have to use it a lot, I need to learn the hotkeys. It's not optional; i don't have the equivalent of a pointing device that does different thingss depending on what you point at in what way, I have to learn the hotkeys. Even on <a href="https://cupoftea.social/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>macOS</span></a>, where they tried to unify the UI experience for screen reader users as much as they can, you gotta learn the hotkeys or gestures to control the screen reader at the very least. And I can do that, but many can't, which is where a huge part of the supposed skill issues we see in <a href="https://cupoftea.social/tags/accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>accessibility</span></a> come from. This stuff is powerful, but not very intuitive for a great many users, and I don't really have a solution for that in mind <a href="https://cupoftea.social/tags/blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blind</span></a> <a href="https://cupoftea.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>a11y</span></a> <a href="https://cupoftea.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a></p>