In the proposed designs for the new admi ui the row height for tables has been increased. An increased row height will display fewer items per screen and require more scrolling, creating a greater cognitive load for some users.
In comment #20 in the basic table theming issue, @modulist suggested to provide an affordance to choose alternative settings for table cell padding to vary the row height, like Gmail's Comfortable/Cozy/Compact settings.
Provide an affordance to choose alternative settings for table cell padding to vary the row height
It will affect all tables in Drupal core, and will need to be integrated with other features in tables like draggable tables.
Comments
Comment #3
ckrinaComment #4
lauriiiIs this a blocker or nice to have feature?
Comment #5
ckrinaI'd say a (really good) nice to have because we don't have it right now, so maybe not to block an stable release? But the last call should be by someone with more a11y experience. :)
Comment #6
modulist commented(clears throat and affects authoritative voice)
This is not a critical accessibility issue that prevents certain users from being able to use the Drupal authoring platform entirely. Therefore it should not block a stable release.
Comment #7
saschaeggi@modulist @ckrina as I also think this shouldn't block a release as the goal is to change as little as possible. I change this ticket to "postponed" for now. But we'll keep an eye on this one for sure!
Comment #8
nod_I can help navigate the code if someone is up for it.
Comment #9
andrewmacpherson commentedI like this proposal a lot. It could be a simple button/select at the top of the table. (Is there a "small button" style proposed?).
In Seven these currently use a show-weight button (styled to look like a link, meh) just before the start of the table. It doesn't seem like a big stretch to put a pair of (small) buttons at the start of the table like this.
It could go a little bit further with a grouping container style for these "table preferences controls".
For draggable tables, there is a secondary benefit to letting users adjust the table row size: it affects the target size of the drag operation. It will be great if the larger version rows are at least 44px in height, to address WCAG 2.5.5 Target Size (this is level AAA, nice to have, but not an a11y gate blocker). So now you have some meaningful choices for the user: small rows, to view more at once, or drag across a lot of rows at once, vs. large rows which can be easier to read and helpful for users who are less confident with the pointer. And row weights still replace drag entirely for users who need/prefer that.
Comment #10
mgiffordFixing the accessibility tag.
Comment #11
ckrinaSince there have been several request to add customizable settings, we've opened a first issue to figure out how to start this and discussing things like who should be able to customize what things and where (user vs site-builder). Please feel free to add any thoughts in there: #3067273: Provide form for customizable settings.
Comment #12
huzooka