Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Notices related to the publishing workflow should be announced to assistive technologies #3690

Closed
afercia opened this issue Nov 28, 2017 · 1 comment · Fixed by #4192
Closed

Notices related to the publishing workflow should be announced to assistive technologies #3690

afercia opened this issue Nov 28, 2017 · 1 comment · Fixed by #4192
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). Needs Design Feedback Needs general design feedback.

Comments

@afercia
Copy link
Contributor

afercia commented Nov 28, 2017

Any visual notice used in the editing workflow should be announced with an audible message to screen readers. For example, when publishing a post a notice appears:

screen shot 2017-11-28 at 13 16 48

Since there's no page reload any longer (the page reload was sort of reassuring feedback that something happened), screen reader users won't have a clue of what happened. Was the post published / updated successfully? Any errors? All they get is just silence.

All these kinds of visual messages should always be paired with an audible message to convey the same information to users.
@afercia afercia added the [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). label Nov 28, 2017
@mtias
Copy link
Member

mtias commented Nov 28, 2017

Also related to: #3496

I think this should all be done together, and using the speak accessibility utility makes a lot of sense to me.

@mtias mtias added the Needs Design Feedback Needs general design feedback. label Nov 28, 2017
@youknowriad youknowriad mentioned this issue Dec 28, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
[Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). Needs Design Feedback Needs general design feedback.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Accessibility: Announce notices to assertive technologies WordPress/gutenberg
2 participants
@mtias @afercia