[wp-meta] [Making WordPress.org] #149: Forums should expose accesskeys

Making WordPress.org noreply at wordpress.org
Wed Sep 18 11:43:44 UTC 2013


#149: Forums should expose accesskeys
-----------------------+----------------------------
  Reporter:  Daedalon  |      Owner:
      Type:  task      |     Status:  new
  Priority:  lowest    |  Component:  Support Forums
Resolution:            |   Keywords:
-----------------------+----------------------------

Comment (by accessiblejoe):

 Replying to [ticket:149 Daedalon]:
 > Migrated, but modified from #wp23072.
 >
 > The forums have various accesskeys available, but they aren't exposed in
 any way. Proposed in #wp23072 is adding information on accesskeys to the
 title tag. We agreed that wouldn't be ideal, but not sure what would be.
 We could use feedback from the a11y team.

 TL;DR = don't use accesskeys.

 It is commonly thought that accesskeys conflict with screen reader
 functions, they do not, screen reader key combinations take precedence,
 negating accesskeys. WindowEyes disallows numerical accesskeys. There are
 conflicts with some user agents, IE implements them differently.
 Naturally. Opera requires an additional key combination, etc.

 The more interesting question is how to inform the user that accesskeys
 are in effect. There is some benefit for users who need them but even if
 they've figured out they exist they still have to be savvy enough to
 invoke workaround key combinations, partially negating the benefit.

 See also #24766 Title attributes galore. They serve no useful purpose.
 http://core.trac.wordpress.org/ticket/24766

--
Ticket URL: <http://meta.trac.wordpress.org/ticket/149#comment:2>
Making WordPress.org <http://meta.trac.wordpress.org/>
WordPress blogging software


More information about the wp-meta mailing list