Skip to content

Implications of incorrect tab order #15

@markfinst

Description

@markfinst

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions