Posted by falcon03 on October 29, 2012 at 8:14pm
15 followers
| Project: | Views |
| Version: | 7.x-3.x-dev |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
| Issue tags: | a11ySprint, accessibility, needs backport to D7 |
Issue Summary
When adding a view, a blind user can see "fields", "sort criteria", "filter criteria" and similar titles as headings. But, unfortunately, the related operations are shown before the headings, not after them. This is really confusing for new views user (it was one of my main issues with views) and increases very much the learning curve for new blind users.
Just to clarify, let me give an example of the structure that I would like to see (related to sort criteria):
- The "sort criteria" heading;
- The sort criteria that a view is currently using;
- The dropbutton to add a new sort criteria
Comments
#1
Correcting title.
#2
Compared to #1824634: [meta] Dropbutton accessibility issues this should be normal
#3
Isnt this like a novice task?
This one is borderline major, I actually did the whole NVDA thing with your eyes closed. And this one is really confusing.
#4
Straight forward re-ordering of markup, screenshots attached.


Before
After
#5
Looks good. Patch applied and screen read with VoiceOver.
#6
works ok in voiceover/chrome/osx now
#7
cross post
#8
Nice work!
#9
Committed and pushed to 8.x. Rock!
#10
Sorry, I haven't had time to test the patch these days, I've been able to test it only today.
Things are better now. But I think that things related to the dropbutton should be placed between the heading and the dropbutton itself.
For instance, for the "sort criteria" the structure should be the one described in the issue summary. Actually, instead, it is as follows:
I am re-opening this issue; I don't know if this should be a follow up.
#11
Hopefully we can sort through this in the issue and make a revision.
#12
Moved the $content above the $actions. Seems to work.
#13
This looks good from the code site, but i'm wondering whether the visual output changes with that change? Maybe someone
should just post a screenshot.
#14
From the accessibility point of view it's perfect now. RTBC for me, but I am not changing the status due to dawehner request.
BTW: With the two small fixes in this issue we made two very big improvements to views accessibility! The placement of operations was really difficult to understand for new views blind users...
#15
So there is no visual difference before and after this change, it looks perfect!
Before
After
#16
Thanks! Committed to 8.x.
#17
Let's backport that.
#18
patch for backport to D7
#19
oops, whitespace removed.
#20
Screenshot before patch applied:

Screenshot after patch applied:

Appears visually unaltered.
#21
That is looking great!
#22
Guys, I don't know what happened. We have a problem: I don't know the reason why, but the situation at this time is the same as in #10...
I am sorry this issue is becoming confused, but I thought I'd better report the problem here.
#23
Well i have no clue why, but the HTML is fine.
#24
#19: views-dropbutton-d7port-1826368-19.patch queued for re-testing.
#25
The last submitted patch, views-dropbutton-d7port-1826368-19.patch, failed testing.
#26
I looked for the file mentioned in #12, that it sounds like Dries committed in #16.
It looks like it should have been in this file core/modules/views/views_ui/theme/views-ui-display-tab-bucket.tpl.php.
but, there is no theme directory in views_ui.
Where is this file now?
#27
It was moved in #1805980: Rename /theme to /templates and theme.inc to views.theme.inc to core/modules/views/views_ui/templates/views-ui-display-tab-bucket.tpl.php
#28
@EllaTheHarpy are you able to reroll a new patch?
#29
I think the patch from #19 got it into core. From core/modules/views/views_ui/templates/views-ui-display-tab-bucket.tpl.php the HTML now looks like:
<div <?php print $attributes; ?>><?php if (!empty($title)) : ?>
<h3><?php print $title; ?></h3>
<?php endif; ?>
<?php print $content; ?>
<?php if (!empty($actions)) : ?>
<?php print $actions; ?>
<?php endif; ?>
</div>
Now whether it is working properly or not is another issue, but it should be in the right order now.
#30
So this should be marked as fixed?
#31
Yes, it seems to be. Attached a screenshot. HTML looks good. VoiceOver approaches this in the right order.
#32
The patch in #19 was a backport against Views-7.x-3.x. The patch in #12 was committed to core.
Changing the project and status in case backport is still needed/wanted.
#33
#19: views-dropbutton-d7port-1826368-19.patch queued for re-testing.