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

Implications of incorrect tab order #15

Open
markfinst opened this issue Nov 22, 2018 · 1 comment
Open

Implications of incorrect tab order #15

markfinst opened this issue Nov 22, 2018 · 1 comment

Comments

@markfinst
Copy link

When using tab key user navigates to the next image in column, rather than to the next image of initial order. For example, with layout:

1 2 3
4 5 6
7 8 9

tab order is: 1, 4, 7, 2, 5 ....

Possible solutions:

  • Catch tab key via JS and set focus manually.
  • Set tabindex on each item.

This issue is more a discussion if this is a problem at all.

  • Should we do something about it or this problem is irrelevant for most popular use-case - grid of photos?
  • Are there any assistive technologies that work incorrectly because of this order?
@desandro
Copy link
Owner

Breaking horizontal order is sort of the point of Masonry-like plugins.

Masonry has a horizontalOrder option that tries to address this concern.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants