[wp-trac] [WordPress Trac] #47118: Media Editor: Undo and Redo icons are not consistent throughout the interface
WordPress Trac
noreply at wordpress.org
Thu Jun 6 15:56:11 UTC 2019
#47118: Media Editor: Undo and Redo icons are not consistent throughout the
interface
---------------------------------------------+-----------------------------
Reporter: afercia | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 5.3
Component: Media | Version:
Severity: normal | Resolution:
Keywords: wpcampus-report has-screenshots | Focuses: ui,
| accessibility
---------------------------------------------+-----------------------------
Comment (by afercia):
Re: aria-label vs. screen-reader-text
In Gutenberg, the buttons use aria-label also because their tooltips use
the text from the aria-label. This allows to expose the buttons accessible
name visually, both on hover and on focus.
In the media editor the buttons use screen-reader-text just because of
historical reasons. The visually hidden text allows screen reader users to
understand what the buttons are about.
However, these media editor buttons don't expose their names visually.
This is a problem for sighted users who can only use the keyboard or a
technology that mimics the keyboard. For example: speech recognition
software (Dragon) users. They need to know what a UI control name is to be
able to voice a command like, for example: "Click flip vertically".
Not to mention cognitive impairments or simply different cultural
background or non-familiarity with icons. Controls that use only icons are
problematic for many users. This issue was discussed at length in the
Gutenberg project and still needs to be fully addressed.
Accessible tooltips would help but they still wouldn't solve the issue for
speech recognition software users. Worth also reminding that the
introduction of tooltips in core was discussed many years ago and there
was no consensus.
Gutenberg uses tooltips though, so I guess it's time to start some new
conversation to evaluate their introduction in core.
As said, they wouldn't be sufficient anyway: the UI should offer options
to reveal the controls name, see this related issue on the Gutenberg
GitHub: https://github.com/WordPress/gutenberg/issues/10524
--
Ticket URL: <https://core.trac.wordpress.org/ticket/47118#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list