Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I did some testing of Drupal 7 with a Dragon Naturally Speaking (DNS) user today. One of the tasks that the user attempted to complete was rearranging blocks on the Blocks configuration page.
The user had a difficult time reordering blocks within a region. DNS does have a mark and drag command, which is labor intensive to use) and which not all users will have the skill to use properly. The user was unaware that a mechanism existed to 'Show row weights', as the link to expose the row weights is only visible on focus, and DNS users do not typically tab through a page. DNS offers more convenient and efficient methods of navigating a page than tabbing.
I cautiously open up this contentious issue, however it would appear that DNS, and other voice command, users will have an unreasonable degree of difficulty using tabledrag in D7 without the 'Show row weights' link exposed.
| Comment | File | Size | Author |
|---|---|---|---|
| #23 | Larger-Show-Weights-Link-925844-23.patch | 403 bytes | mgifford |
| #14 | Larger-Show-Weights-Link-925844-14.patch | 408 bytes | mgifford |
| #14 | drupal8-tabledrag-0.9em.png | 147.71 KB | mgifford |
| #14 | drupal8-tabledrag-1.0em.png | 145.87 KB | mgifford |
Comments
Comment #1
Everett Zufelt CreditAttribution: Everett Zufelt commentedtagging
Comment #2
Jeff Burnz CreditAttribution: Jeff Burnz commentedNot sure I fully understand this issue - the "Show row weights" link is exposed by default, for all tables that have drag and drop. In seven the link is very small.
Comment #3
catchSince there's already an accessible option (in fact both ways are accessible but one is more than the other), but it's hard to find, I'm downgrading this to 'normal' - something being hard to find isn't enough to block a release - compared to the overlay issue where it could be completely unusable with no way to get out of it.
Also drag and drop has been in Drupal pretty much unchanged since D6, so there is no newly introduced bug here.
Comment #4
Everett Zufelt CreditAttribution: Everett Zufelt commented@Jeff
I was under the impression that we ended up decided upon hiding the 'Show row weights' control. The user I was testing with definitely was unable to find it.
Can you please tell me where it is displayed relative to the table so that I can provide further assistance?
Comment #5
Jeff Burnz CreditAttribution: Jeff Burnz commentedThe "Show row weights" link is above the table, to the right. If you are on the blocks page is right after the "Add block" link (which is on the left). The very next "tab" after the "Show row weights" will land you in the table.
I think the link is hard to see, its quite small and you don't notice it immediately in Seven. In Bartik its a bit bigger and more obvious.
Comment #6
Everett Zufelt CreditAttribution: Everett Zufelt commented@Jeff
Thanks, the user wasn't able to find it without disabling styles in the browser. Perhaps we can make this larger in Seven?
Comment #7
Everett Zufelt CreditAttribution: Everett Zufelt commentedComment #8
Everett Zufelt CreditAttribution: Everett Zufelt commentedSince the problem has only shown up once, with the only user known to test the UI with this technology, I will bump to D8 to see if we can find a better solution for tabledrag / making the show row weights more visible without diminishing from the UI.
Comment #9
Jeff Burnz CreditAttribution: Jeff Burnz commentedI think its a good move to bump this off to D8, we're really in the home-strait now for D7 UI and it would be another bike shed to change this now, thanks Everett.
Comment #10
mgiffordAnother adjustment for the http://drupal.org/project/accessible to take care of?
Comment #11
bowersox CreditAttribution: bowersox commentedsub
Comment #12
mgiffordEchoing Everett, can find a better solution for tabledrag to make the show row weights more visible without diminishing from the UI.
Comment #13
mgiffordFrom discussion at A11ySprint.
Comment #14
mgiffordHere's the difference of 0.1em's on this text.
Comment #15
nod_See #1719640: Use 'button' element instead of empty links as well.
Comment #16
mgifford@nod_ ultimately there's not much similar between the two issues that I can see. Maybe I'm missing something though.
Comment #17
mgifford#14: Larger-Show-Weights-Link-925844-14.patch queued for re-testing.
Comment #18
mgifford#14: Larger-Show-Weights-Link-925844-14.patch queued for re-testing.
Comment #19
mgifford#14: Larger-Show-Weights-Link-925844-14.patch queued for re-testing.
Comment #20
mgifford#14: Larger-Show-Weights-Link-925844-14.patch queued for re-testing.
Comment #21
echoz CreditAttribution: echoz commentedFor the size, just removing font-size: 0.9em; will result in the default 1em, no need to declare font-size: 1em;
Secondly, #15 implies this should use the button element.
Comment #22
echoz CreditAttribution: echoz commentedComment #23
mgiffordNo problem re-doing things when/if #15 gets into core. However, just fixing this up for now.
Comment #24
mgiffordgo bot.
Comment #26
echoz CreditAttribution: echoz commented#23: Larger-Show-Weights-Link-925844-23.patch queued for re-testing.
Comment #27
mgifford#23: Larger-Show-Weights-Link-925844-23.patch queued for re-testing.
Comment #28
echoz CreditAttribution: echoz commentedApplies cleanly and for just making this link the default site size, the fix is correct.
Comment #29
alexpottCommitted 8b0ea75 and pushed to 8.x. Thanks!