Closed
Bug 1783172
Opened 2 years ago
Closed 1 years ago
Too many tab stops on column headers from search input to results list in horizontal layout of address book
Categories
(Thunderbird :: Address Book, defect, P3)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1819281
People
(Reporter: thomas8, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: ux-efficiency)
The everyday scenario of keyboard-navigating from AB search input to results list in vertical layout now takes 6 or more tab stops as we're passing through each and every column header (we have 10 columns available and more to come) - that's way too many, and needs way too much focus (pun intended).
Accessibility is good. Too many tab stops for basic scenarios isn't.
Rule of thumb: Multiple adjacent elements of the same type should only have a single tab stop, reach the rest with arrow navigation. Which is good ARIA practice, too!
STR
Address book > List display options > Switch to horizontal layout
- Click in search field, do a random search
- Press
Tab
as often as required to focus the first contact item in the results list
Actual result
- 6 or more
tab
keypresses needed: each column header is a tab stop - navigation to the result list extremely inconvenient, plus the number of tabs may change depending on number of columns, so it needs more attention and it's hard to develop muscle memory
Expected
- Single tab stop at the column header which the table is currently sorted by (e.g. Name)
Column header tab stop should come after the results list, not before (to reduce the number of keystrokes from search field to results list)- Then any other column headers can be focused using
arrow-right/left
Windows Explorer certainly had a good reason for this design, try it there!
Updated•2 years ago
|
Blocks: tb102found
Reporter | ||
Updated•2 years ago
|
Updated•1 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•