[wp-trac] [WordPress Trac] #32600: wp.a11y.speak improvements

[WordPress Trac]

#32600: wp.a11y.speak improvements
----------------------------------+----------------------------------------
 Reporter:  afercia               |       Owner:
     Type:  defect (bug)          |      Status:  new
 Priority:  normal                |   Milestone:  Awaiting Review
Component:  General               |     Version:  4.2
 Severity:  normal                |  Resolution:
 Keywords:  has-patch dev-        |     Focuses:  accessibility, javascript
  feedback                        |
----------------------------------+----------------------------------------
Description changed by afercia:

Old description:

> Now that `wp.a11y.speak()` is in core and we have some weeks of real
> usage experience, we'd like to propose a first round of possible
> improvements. We have a couple of things for now:
>
> 1.
> Noticed [https://github.com/voldemortensen/menu-customizer/issues/77
> during the Menu Customizer development and testing], looks like sometimes
> the previous message gets announced before the current message.
> We couldn't consistently reproduce this so, technically, it's not a bug
> but [https://wordpress.slack.com/archives/accessibility/p1433787966000781
> we agreed in the last accessibility team meeting] to change the aria-
> relevant value from "all" to the default "additions text".
> Basically there's no point in getting also the "removals", at least in
> this WordPress implementation. Also, see for reference:
> http://www.w3.org/TR/wai-aria/states_and_properties#aria-relevant
> > Note: aria-relevant values of removals or all are to be used sparingly.
> Assistive technologies only need to be informed of content removal when
> its removal represents an important change, such as a buddy leaving a
> chat room.
>
> 2.
> Add the ability to specify the politeness level of the live region. Looks
> like there's some interest in this feature initially reported by @drew
> and it would be a nice to have, also making `wp.a11y.speak()` a bit more
> flexible.
> For reference: http://www.w3.org/TR/wai-aria/states_and_properties#aria-
> live
>
> Also, any improvements proposal and feedback would be very welcome and
> appreciated.

New description:

 Now that `wp.a11y.speak()` is in core and we have some weeks of real usage
 experience, we'd like to propose a first round of possible improvements.
 We have a couple of things for now:

 1.
 Noticed [https://github.com/voldemortensen/menu-customizer/issues/77
 during the Menu Customizer development and testing], looks like sometimes
 the previous message gets announced before the current message.
 ~~We couldn't consistently reproduce this so, technically, it's not a bug
 but~~ (see comment 1)
 [https://wordpress.slack.com/archives/accessibility/p1433787966000781 we
 agreed in the last accessibility team meeting] to change the aria-relevant
 value from "all" to the default "additions text".
 Basically there's no point in getting also the "removals", at least in
 this WordPress implementation. Also, see for reference:
 http://www.w3.org/TR/wai-aria/states_and_properties#aria-relevant
 > Note: aria-relevant values of removals or all are to be used sparingly.
 Assistive technologies only need to be informed of content removal when
 its removal represents an important change, such as a buddy leaving a chat
 room.

 2.
 Add the ability to specify the politeness level of the live region. Looks
 like there's some interest in this feature initially reported by @drew and
 it would be a nice to have, also making `wp.a11y.speak()` a bit more
 flexible.
 For reference: http://www.w3.org/TR/wai-aria/states_and_properties#aria-
 live

 Also, any improvements proposal and feedback would be very welcome and
 appreciated.

--

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