[wp-trac] [WordPress Trac] #21334: Accessibility of Quick Edit panel in Posts/Pages/etc
WordPress Trac
noreply at wordpress.org
Tue Feb 12 15:38:00 UTC 2013
#21334: Accessibility of Quick Edit panel in Posts/Pages/etc
-----------------------------------+--------------------
Reporter: grahamarmfield | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: 3.6
Component: Accessibility | Version: 3.4.1
Severity: normal | Resolution:
Keywords: 2nd-opinion has-patch |
-----------------------------------+--------------------
Comment (by adamsilverstein):
thanks for the info, i will banish 'tabindex' from all future code! i only
added them so i could tab into the link (for testing), but i think i can
fix that by using a table structure more carefully in the layout as you
suggested.
my 1st patch did closer to what you suggest (almost) by hiding/showing the
quicklinks when tabbing into the field above them; then ticket opener
@grahamarmfield suggested that a show quick links/hide quick links setup
would be more accessible, especially for screen readers, note the show and
hide links include the screen reader context info.
i really value your opinion here, can you help me decide the best
resolution, i see these options:
1. show quick links at all times, remove hover on/off code - i like this
the best personally
2. use current method - show/hide quicklinks (but with no tabindex and
more browser testing for tab layout); also keeps existing hover on/off
effect
3. method where links show when row or cell gains focus
not sure how to make cell focusable in version 3, or if it will fire even
when entered by tab on all browsers, or if will work at all on touch
devices. i think i tried this route originally and wasn't getting events i
expected when tabbing into the cell.
versions 1 & 2 seem to be the most accessible which is what we are trying
to address here. what do you think?
Replying to [comment:11 azaozz]:
> Tabindex is "evil" :)
>
> It breaks the natural flow of tabbing affecting negatively all users,
and behaves differently in different browsers when added to elements that
can be shown/hidden or are moved in the DOM.
>
> A better way to fix this may be to make the table cell (or row?)
"focusable" and show these links on focus. This should also be tested on
touch devices.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/21334#comment:12>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list