11

When using the Stacks Editor, tab navigation on Q&A pages is messed up. Ex. the "post answer" button being the first thing that gets tabbed to on a new page load without clicking anything. That should be the "skip to main content" thing. And it's making it so I can't tab straight from the answer body input to the post answer button, which is what I want and how it used to work and how I think it should work for good UX.

Improve this question
6
  • 3
    @ShadowWizzard 1) what is unclear about "stacks editor"? 2) go back to the old editor and try to repro and tell me what you find. Commented Mar 13 at 9:26
  • 1
    With the old editor if you load the page and press tab once, you go to the body of the editor. Second tab press gets you to the post button. With the new editor, first tab gets you to the post button. Second+ tab starts from the top of the page and you have to tab quite a bit to get to the editor. Even then you also have to tab through all the buttons of the editor. In both cases the tab index of the post button is 120. Commented Mar 13 at 9:29
  • 2
    @VLAZ FWIW, the tabbing on the old editor had massive problems, to the point where you couldn't even use certain features via keyboard. (You still can't use Stack Snippets with a keyboard, but at least uploading an image doesn't require knowing the obscure key combo not mentioned anywhere.) See for example my review of the Ask Question page. Commented Mar 13 at 13:15
  • @Laurel "Also, I don't know about the new editor, but the old one was immediately focused if you clicked Tab (which is annoying if you want anything else on the page)." But the new behaviour is undoubtedly worse than before. Just immediately focusing the post button. Commented Mar 13 at 13:53
  • Is it possible to just completely remove tabindex? (If possible, please figure out why this behaviour was added and who relies on it, first.) Commented Mar 19 at 13:21
  • @wizzwizz4 Presumably, it was added so people will quickly tab to the answer area to write there, then tab again to post. At least that's how it works using the old editor. I'm not going to claim it's good behaviour but it seems to be the deliberate behaviour that was put in place. Commented Mar 19 at 13:30

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.