first alternative highlighted after retry

[otacke]

first alternative highlighted after retry

[falcon-git]

I think this is by design to provide a good user experience for keyboard users. I agree that it looks a bit buggy if you're not using the keyboard. Not sure what to do about it.

[otacke]

Hmm, just for that purpose, it would be a little "overkill" to listen for keydown and mousedown (and touch) events in order determine whether the last interaction before the reset came from the keyboard or the mouse (or a touch device), wouldn't it?

[falcon-git]

It would be a way of solving it. I didn't think of that. Good idea! I'll discuss it with those who implemented it tomorrow to see if they think it is "overkill".

[otacke]

Sounded just weird to me for such a tiny issue :-)

[falcon-git]

Yes, but we have the same issue in a lot of content types. It is not only MultipleChoice, so if we could solve it in a nice way(code wise) for all it would be a step forward.

[otacke]

In that case, I am going to file in a patent first thing in the morning ;-)

[icc]

Hehe...

I wonder if this could be made better by simply making the focus effect a bit softer. The purple background almost makes it seem like the option is selected instead of highlighted.

I can't recall where but I imagine that I've read something about that moving the focus to where the next "action" is needed is a good UX approach, especially when going "backwards". It may have been a WCAG thing.

[otacke]

I see. But wouldn't that have potential for confusing people with visual impairment?

For example, if you have a form with some instructions at the top and some input fields below, setting focus to the first input field would be great for people who're not impaired. They can still see the text and start typing right away. On the other hand, if you're blind and cannot see the text, you wouldn't get the context if the focus was on the input field right away, would you?

From this perspective, multiple choice seems to use the focus wisely: not setting focus on first start, but on retry.

[icc]

Actually, I believe you do get the relevant context using a readspeaker if the HTML is set up correctly, and if not I guess that the user would normally 'zoom out' to the parent element until it makes sense.

[otacke]

I don't know. Will have to learn about that.