Taiga UI family
Web Accesibility question on Tui ComboBox and Select #6701
-
|
According to the W3C, for single select combo boxes, the tab button is supposed to select the currently active descendant element and then move to the next element in the DOM. In the current release of taiga v3.65.0 I noticed that space bar and enter work to select items, but tab does not. I am wondering if there is a way to determine the active descendant (without querying the DOM) in a tui-data-list-wrapper or combo box so that I may patch that data after finding the select option it correlates to. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Taiga UI has active descendant actually focused at all time — instead of having the select component focused and active descendant appear focused. So you can listen to keydown.tab event. But you would only get the DOM element, not the underlying tuiOption. Better to create a feature request. However I don't think it's a good idea and I haven't seen a UI library that does that. Native Select element just always has active descendent selected, it does not allow you to navigate around options with arrows and then decide not to change value. So I would say it's a mistake in W3C part. |
Beta Was this translation helpful? Give feedback.
Taiga UI has active descendant actually focused at all time — instead of having the select component focused and active descendant appear focused. So you can listen to keydown.tab event. But you would only get the DOM element, not the underlying tuiOption. Better to create a feature request. However I don't think it's a good idea and I haven't seen a UI library that does that. Native Select element just always has active descendent selected, it does not allow you to navigate around options with arrows and then decide not to change value. So I would say it's a mistake in W3C part.