[wp-trac] [WordPress Trac] #50512: Improve accessibility of the Plugin & Themes Auto-Updates feature

[WordPress Trac]

#50512: Improve accessibility of the Plugin & Themes Auto-Updates feature
--------------------------+------------------------------------------------
 Reporter:  ryokuhi       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  high          |   Milestone:  5.5
Component:                |     Version:  trunk
  Upgrade/Install         |
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  ui, accessibility, administration
--------------------------+------------------------------------------------

Comment (by afercia):

 == Double checking 4) Inline notifications:

 I see the pattern where a notice with an empty paragraph is printed out
 and hidden until it receives some text is already used in a few places,
 for example:
 - the posts/terms quick edit/bulk edit
 - `wp_comment_reply()`

 We should check all those instances. For what concerns the specific
 instances used for the auto-updates, I see that whenever there's an error,
 the notice gets revealed to display an error message ''and'' the same
 message is sent to the polite ARIA live region via `wp.a11y.speak()` 👍

 The only thing I'd change is the politeness level of the ARIA live
 messages. Since these notices are errors, I'd use `assertive` so that the
 audible messages are equivalent to alerts and assistive technologies will
 immediately notify the user interrupting the current announcement.

 Quick patch incoming.

 == Re: 3) Button text change:
 I think this should be postponed to the next release cycle. Will wait for
 the next accessibility team meeting on Friday to make a final decision. To
 summarize what was discussed so far:
 - the auto-updates links are more an on/off toggle
 - the more appropriate ''native'' element for that would be a checkbox
 - concerns were expressed for the presence of too many checkboxes in the
 plugins and (network) themes tables
 - we'd need to evaluate some other kind of "toggle" control
 - for example a toggle button with normal and "pressed" state, or a switch
 toggle
 - the goal for this change is, as usual:
   - a control's text should not change dynamically to represent its state
   - the state should be conveyed separately
   - the control should only communicate the underlying action and maybe
 have a visual hint for its state (like the checkmark for native
 checkboxes) but it should never change its text

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