-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Editions Table Style Touchup #9853
Comments
Howdy @schu96 ! Thanks for compiling this list! 😊 For 1, try to match (or potentially reuse if possible) the styling of our normal pagination widget, eg from search page: For 2, please feel free to propose some designs! For 3, good catch, fixes welcome! Likely setting tabindex=0 from the "^V" buttons and from the book cover might be the best bet For 4, designs welcome! For 5, this one will be a bit tough, since it might require some clever hooking into the way the editions table plugin works, but fix very much welcome! Overall, I think you can:
To answer your question about the files:
Let us know if you have any further questions! |
Description
Within the editions table that is found within a work, I noticed some potential visual and accessibility changes that can make it easier for users to navigate through this table. However these proposed changes are not completely straightforward to make since there are two distinct editions table files: the Featured Editions table (FE) and the All Editions table (AE).
Relevant Designs
1. The pagination buttons at the bottom of the table do not make it entirely clear which page the user is currently viewing.3. Keyboard navigation within the edition/availability row has redundant behavior. Pressing Tab from the search bar moves focus into theth
containing the edition. Pressing Tab again will move focus into thea
element containing the word edition.Feedback Questions
Most of the changes I'd like to make to the AE table are within
js/editions-table/index.js
andlegacy-datatables.less
, but I noticed that a separate HTML and CSS template was made ineditions_datatable.html
andeditions.less
.Is there a preference for keeping the two sets of editions table, or to reuse the FE table template?
Decisions
Stakeholders
The text was updated successfully, but these errors were encountered: