[wp-trac] [WordPress Trac] #24148: Add aria-labelledby attributes to comment form

[WordPress Trac]

#24148: Add aria-labelledby attributes to comment form
-------------------------+------------------------------
 Reporter:  joedolson    |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Comments     |     Version:  3.5
 Severity:  normal       |  Resolution:
 Keywords:  has-patch    |     Focuses:  accessibility
-------------------------+------------------------------

Comment (by GaryJ):

 How do user agents handle references to ID elements that don't exist (as
 in, what happens if `comment_notes_before` and `comment_notes_after` are
 filtered to be an empty string?

 ----

 Have you listened to what the comment field is now announced as? Listen to
 http://clyp.it/oilalv1h (also attached as an MP3 for future reference). As
 a non-AT user by default, that doesn't sound as helpful as it could be.

 Here's a transcription of the the start of what's read aloud by ChromeVox
 (spoken letters in capitals):

 > "comment you may use these HTML tags and attributes colon less than A
 HREF equal quote quote title equal quote quote greater than less than ABBR
 title equal quote quote greater than less than acronym title equal quote
 quote greater than less than B greater than less than..."

 Would it be any clearer for non-visual users to have something like:

 > ""comment you may use these HTML tags and attributes colon A with HREF
 and title attributes, ABBR with title attribute, acronym with title
 attribute, B, ..."

 ...read out instead?

 If so, then assuming #29699 goes in, we could check for screen-reader-text
 support and have a friendly version for screen readers which is referenced
 from comment field `aria-labelledby`, and hide the original visual markup
 with `aria-hidden`.

 Incidentally, ChromeVox consistently cut-off at the same place each time
 when reading out the visual markup, just after reading the "cite" tag. I
 don't know if this is a bug with ChromeVox, or my setup, or something
 about the length of the sentence or other issue that may affect other
 text-to-speech implementations.

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