[wp-trac] [WordPress Trac] #27553: Make WP editor toggle focusable

WordPress Trac noreply at wordpress.org
Tue Sep 30 13:09:44 UTC 2014


#27553: Make WP editor toggle focusable
--------------------------+-----------------------------
 Reporter:  joedolson     |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Editor        |     Version:  3.3
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:  accessibility
--------------------------+-----------------------------

Comment (by sharonaustin):

 Replying to [comment:23 joedolson]:

 Definitely appreciate the feedback, Joe! Especially knowing how busy you
 are....Thank you so much.

 1. Regarding this:
  > Regarding DOM objects -- all elements on any page are DOM objects. The
 DOM is the model of objects in a document; nothing can be on the page and
 not be part of the DOM.
 >
 I worded my earlier statement about DOM objects poorly in the context of
 this ticket; I understand that all elements on a page are DOM objects but
 --and I am making this next statement in all uncertainty--I don't think
 screen readers access all the DOM elements in all modes.  Take the example
 of a "div"--aren't they "blind" to screen readers unless they receive
 special handling?  (By all means, please feel free to correct me on that,
 sir). A specific example I have in mind is the current fad of styling divs
 to look like buttons, turning these false buttons into an accessibility
 barrier (if the div doesn't get states for focus, etc. ).

 Another example. Yesterday, before I read this response, I had been
 testing with NVDA on the first two patches, yours and avyrl's, in one of
 my test sites.  It turns out NVDA would read out loud the text that was
 already in place in the "Visual" Editor screen, but not the "Text" editor
 screen, of the TinyMCE.  I have to assume at some level that the text in
 the "Text Editor" is a DOM element, but NVDA was blind to text already in
 the "Text Editor" screen.  I don't know why.

 At any rate, I definitely appreciate the feedback, but as I think you said
 before, this conversation is for another ticket, and I think me going off
 on tangents is problematic here, so no more testing from me unless
 requested.  I'll watch with very great interest any further developments
 on this particular ticket.  Let me know what I can do.

 Take care, Joe, and thanks for everything you do.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/27553#comment:25>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list