[wp-trac] [WordPress Trac] #30333: Media filtering behavior should be the same in list and grid mode displays
WordPress Trac
noreply at wordpress.org
Fri Feb 27 23:22:30 UTC 2015
#30333: Media filtering behavior should be the same in list and grid mode displays
-------------------------+-------------------------------------------------
Reporter: Fab1en | Owner: wonderboymusic
Type: enhancement | Status: reopened
Priority: normal | Milestone: 4.2
Component: Media | Version: 4.0
Severity: normal | Resolution:
Keywords: has-patch | Focuses: ui, accessibility, javascript,
| administration
-------------------------+-------------------------------------------------
Comment (by afercia):
> I think there is a need to make this more homogeneous :
I agree, but should be the opposite :) Every kind of "automatically"
triggered action is always very problematic for keyboard users and screen
reader users and, generally, should be avoided.
We could try and test the proposed solution, it tries to address the
change of context issue. Whatever the final solution, I see here the need
to give feedback to screen reader users about what's happening in the page
and the results set change.
By the way I'd like to point out that for keyboard users the only way to
explore the content of a select is using the arrow keys. When they get the
options available, they move out of the select with their tab key and...
boom: the media grid will update its content even if that wasn't the
user's real intention.
Worth nothing also that browsers fire the change event in different ways,
e.g.:
- Firefox gets the specs right and fires the event '''only if the value
was changed and only after the select loses focus (tabbing away from the
select)'''
- Chrome instead '''fires the event immediately after the select value
gets changed, when it's still focused''' (and that's really, really, bad).
The only way to avoid this is to actually "open" the select (Alt+Down-
arrow).
Do you really want Chrome users trigger a media library update each time
they press the down-arrow key?
This Chrome bug would be a good enough reason for me to just stick with
standards and use a nice, reassuring, button to trigger the update. Just
use controls for what they're supposed to be used.
There's a whole literature on this subject. Years and years of debates and
discussions about web standards and accessibility, and this issue rises up
again :)
(Ensure) "changes of context are initiated only by user request or a
mechanism is available to turn off such changes." Reference:
http://www.w3.org/TR/WCAG20/#consistent-behavior
> does nothing until I click on the "Filter" button. That makes me think
the functionality was broken
I agree "Filter" doesn't mean so much for the average users. Maybe
"update" better reflects what's really happening on the page?
Thanks very much Helen for bringing this to the accessibility team
attention.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/30333#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list