Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Focus management consideration

See original GitHub issue

Currently the component uses both .focus() and aria-activedescendant to announce the focused option.

According to spec a composite widget like this, should keep focus on the textbox and focus should be managed by aria-attributes (and CSS for visual highlighting), which is what I have done in my demo.

It would be good to investigate how well this works for AT.

Issue Analytics

State:
Created 6 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

edwardhorsfordcommented, Apr 27, 2017

I think the current approach seems to work well (for accessibility) - but has the downside that without focus on the input, it’s not obvious that you can continue to type in to it.

1reaction

tvararucommented, Apr 27, 2017

Agree this would be good to investigate.

Historical context: While spiking initial implementations for this I attempted to use aria-activedescendant on its own incorrectly, leading me to falling back to the current .focus() approach, which I saw work well in Leonie’s prototype.