I think I wrote about this before: the Submit Move button was not a real, honest button (i.e. a HTML Input element with that text inside). I don’t know how it was done exactly, but the effect for me was that I couldn’t give it the focus the way I’m used to with Firefox, namely search for the text, then escape from the search.
But at least it was directly preceded on the screen by the ruleset name, like “AGA” or “Japanese”. That meant I could search for that string, escape, hit Tab once, and I was focussed right on Submit.
But all this is now past tense: today I did something to purge my cache completely, or maybe the code changed today in a strange conincidence. Now, although I can search for the text “Submit”, and it is highlighted, it doesn’t get focus. And the trick with “AGA” doesn’t work either anymore, the focus seems to be fixed on the board or something.
Please don’t underestimate the importance of this issue for me, even if it seems minor to you. I have a mobility impairment that makes using the mouse (or any pointing device) quite hard. I have lost a job or maybe two because of that, on sites for time tracking and payroll and what not. So now to see the same happening with my favorite site … it’s depressing on top of the physical problem.
We’re keen to support this properly - we’ve been trying to take good steps in the opposite direction (IE in the direction of improving, not worsening!).
maybe there is something going on in your environment that is interfering
This turned out to be the case It was Firefox’ Containers extension. Until now I’ve been using a separate Firefox profile for OGS (and a number of other things), I was hoping to simplify with Containers, but alas. And I remember I tried it before and it always seemed a bit half-finished, or maybe bought from a third party and never toouched after, it just doesn’t look right. But had it been just looks I could live with that. Now I know that it breaks behavior too.
So after I switched back to a separate profile, it works again just as before, ie. I can’t put focus on the control directly but searching for surrounding text works. Sorry for false alarm.
Don’t worry - we often just need someone to test on another machine. That said - this still sounds like an issue?
I notice two other things:
space bar doesn’t work once the submit button is focused. It seems like the behavior is overridden to send me to analysis mode. I have to press Enter instead.
there is no way to focus away from chat. Once I’m in the chat box, i can’t get out
Usually what it takes is just making sure the html is clear that it’s a button. <input> and <button> are focusable by default. Also adding tabindex makes elements focusable.
The weird thing here is that we already have a button so idk what’s going on. The good news is that tabbing around does work, and that’s what most kb users expect. The ctrl-f esc thing is a little more niche (tho very useful, so would be nice if it worked!)
If you’re interested in learning more, this doc talks about how good kb accessibility looks: WebAIM: Keyboard Accessibility
I have some code lying around on my notebook that adds a setting to automatically focus the submit button. When I was done with it, I had my mouse back and didn’t need it anymore. I remember I wasn’t satisfied with how it turned out in Git, but maybe it’s time to take a look at it again.
It was Firefox’ Containers extension. Until now I’ve been using a separate Firefox profile for OGS (and a number of other things), I was hoping to simplify with Containers, but alas. And I remember I tried it before and it always seemed a bit half-finished, or maybe bought from a third party and never toouched after, it just doesn’t look right. But had it been just looks I could live with that. Now I know that it breaks behavior too.