You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the picker_selector divs were to have role="button" and tabindex="0" they would be keyboard focusable. Then keydown eventhandlers for arrowkeys could move them.
The text was updated successfully, but these errors were encountered:
role="button" has nothing to do with being focusable: tabindex="0" is enough.
If you use role="button" you tell assistive technologies that the element acts like a button, ie acts on mouse click, space and enter. Anyway the picker_selector is a slider, not a button.
Naturally you don't need to worry much about screen readers, but the keyboard actions are reasonable. If you opt to use role=slider make sure to add all other attributes required by the pattern. If not it is better to use no role at all.
You wanted some feedback on accessibillity.
If the picker_selector divs were to have role="button" and tabindex="0" they would be keyboard focusable. Then keydown eventhandlers for arrowkeys could move them.
The text was updated successfully, but these errors were encountered: