[Collection issue] Run a user study on keyboard accessibility issues

[melanierichards]

The purpose of this issue is to collect feedback on accessibility issues we'd like user research on. This issue will collect questions that specifically address the needs of people who primarily/only use keyboard input in order to interact with controls. Please comment as we come across questions, and we can either:

a) Seek out prior art/studies on these behaviors b) Design a user study to address these questions once we have enough behaviors we want to verify

For accessibility questions unrelated to keyboard input, let's start a new collection issue. It may be the case that we can combine issue buckets for a user study, but depending on the nature of the questions we may want to recruit a different set of participants.

[melanierichards]

The motivating discussion for this is #171, which tracks a behavior where the spacebar on a <select> control changes based on timing.

@devongavett on that issue:

Our implementation attempts to recreate native behavior. As the user types characters, they are appended to a search string. If no character has been typed after 500ms, the search string is reset. If the user types a space character, and there is already a search string containing non-whitespace, then we append the space to the search string and prevent the selection behavior. If a space is typed but there is no existing search string, then the option is selected and the listbox is closed. So, it depends whether preceding characters had been typed within the last 500ms. We did a bunch of testing, and this matches native typeahead behavior pretty closely, so I would imagine users are familiar with it already.

github-actions[bot] commented 2 years ago

There hasn't been any discussion on this issue for a while, so we're marking it as stale. If you choose to kick off the discussion again, we'll remove the 'stale' label.

• © Githubissues.
• Githubissues is a development platform for aggregating issues.

[github-actions[bot]]

There hasn't been any discussion on this issue for a while, so we're marking it as stale. If you choose to kick off the discussion again, we'll remove the 'stale' label.