[wp-trac] [WordPress Trac] #21312: How to log out of WordPress without a mouse?

WordPress Trac noreply at wordpress.org
Fri Nov 16 19:46:08 UTC 2012


#21312: How to log out of WordPress without a mouse?
----------------------------+---------------------
 Reporter:  grahamarmfield  |       Owner:
     Type:  defect (bug)    |      Status:  closed
 Priority:  normal          |   Milestone:  3.5
Component:  Accessibility   |     Version:  3.4.1
 Severity:  normal          |  Resolution:  fixed
 Keywords:  has-patch       |
----------------------------+---------------------

Comment (by grahamarmfield):

 Replying to [comment:24 DrewAPicture]:
 > Replying to [comment:23 grahamarmfield]:
 > Please excuse my naiveté on this subject, but what are the options for
 creating a target-able link for software like Dragon, JAWS, etc.? From
 your description of Twitter's process, you said "Click settings" + "Click
 Sign Out" worked, so maybe it's worth investigating why it works on
 Twitter but not, say, on Facebook, then apply that logic to the floating
 'Log out' link for !WordPress or even the link in the dropdown. Thoughts?
 >
 It is a good question. On the face of it the Twitter link which is a plain
 text link of 'Settings and help' is moved off the screen in the same way
 as the 'Log Out' link just after the WordPress admin toolbar. There is a
 difference though in that the WP link has width and height both set to 1px
 and overflow:hidden, whereas the Twitter link has a width of 98px, a
 height of 12px and no overflow property set.

 So maybe that's it? It is evident that Dragon does pay some heed to what
 is in a stylesheet - in common with screen readers and other AT - so could
 it be that Dragon interprets the small width, height and the
 overflow:hidden as exposing none of the text?

 I'm not really in a position to test this, but since the WP 'Log out' link
 is moved so far off to the left, is it really necessary to constrain the
 width and height, and to ensure overflow is hidden? I can see the styles
 in question govern any .screen-reader-text items in the #wpadminbar so
 there could be other implications for changing those properties. But it
 might be worth a try?

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/21312#comment:25>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list