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
I’ve been testing the Combobox component with VoiceOver/TalkBack. I noticed that when the options list is expanded and I swipe through it, once I reach the end of the options the virtual cursor simply continues to the next element on the page (outside of the combobox).
From an accessibility perspective, I was wondering:
Would it be more accessible if, after reaching the last option, the swipe navigation would loop back to the input (and then cycle again through the options)?
Or is the current behavior —letting the screen reader continue to the next page element— more consistent with the ARIA pattern?
I understand focus traps are only recommended for modals, not for inline widgets like comboboxes, but I’d love to hear your perspective. My concern is whether some users might accidentally “fall out” of the combobox popup when they actually wanted to stay inside it.
Thanks for clarifying —this would help me (and probably others) better understand the design decision here.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Deque team 👋,
I’ve been testing the Combobox component with VoiceOver/TalkBack. I noticed that when the options list is expanded and I swipe through it, once I reach the end of the options the virtual cursor simply continues to the next element on the page (outside of the combobox).
From an accessibility perspective, I was wondering:
Would it be more accessible if, after reaching the last option, the swipe navigation would loop back to the input (and then cycle again through the options)?
Or is the current behavior —letting the screen reader continue to the next page element— more consistent with the ARIA pattern?
I understand focus traps are only recommended for modals, not for inline widgets like comboboxes, but I’d love to hear your perspective. My concern is whether some users might accidentally “fall out” of the combobox popup when they actually wanted to stay inside it.
Thanks for clarifying —this would help me (and probably others) better understand the design decision here.
Beta Was this translation helpful? Give feedback.
All reactions