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

Improve Keyboard Navigation #267

Open
IanLunn opened this issue Jun 12, 2015 · 0 comments
Open

Improve Keyboard Navigation #267

IanLunn opened this issue Jun 12, 2015 · 0 comments
Milestone

Comments

@IanLunn
Copy link
Owner

IanLunn commented Jun 12, 2015

Problem

When using the tab key, the user can navigate through step elements but inactive steps can't be seen. In some themes, the browser may move the container to make focused elements in inactive steps visible. This can cause the theme to look and generally appear to be broken.

Solution 1

When an element receives focus, Sequence should determine which step it belongs to and navigate to it accordingly.

This may be costly on JS performance and generally not possible.

Solution 2

Prevent focus on elements in inactive steps using tabindex. The user can still navigate the entire application via pagination, prev/next controls and tabbing but elements within a step can only be focusable when the step becomes active.

See: Focusable Elements with tabindex

@IanLunn IanLunn added this to the 2.0.1 milestone Jun 12, 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