Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyboard and screen reader accessibility #11

Open
kornelski opened this issue Apr 2, 2014 · 0 comments
Open

Keyboard and screen reader accessibility #11

kornelski opened this issue Apr 2, 2014 · 0 comments

Comments

@kornelski
Copy link
Owner

I'd love to hear advice how to implement this properly.

VoiceOver on iOS

"select, tap-then-hold" gesture works, so it allows swiping and reordering, but it's hard to preform - both VoiceOver and Slip have their timer to detect hold, so to swipe you have to hold just the right amount of time :(

Any ideas how to improve that?

Keyboard accessibility

What are conventions for such UI? I'd like to avoid inventing something "weird". I'm thinking about:

  • grabbing focused element by pressing Enter
  • moving it up/down with arrow keys
  • dropping with Enter

Should I use other keys? Are there different approaches (like pressing a numeric key to select nth element?) Should I use clipboard analogy (cut, paste) and how to do that without breaking actual clipboard?

I suppose the list elements have to be focusable (the library would add tabindex). Is there a way to make it usable without focus? (Users who don't need keyboard accessibility may dislike the focus ring and some subtle changes in behavior that focusability brings).

Should the list have aria-live? If not, do I need to somehow announce that the order has been changed?

@kornelski kornelski changed the title Add aria attributes Keyboard and screen reader accessibility Mar 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant