-
-
Notifications
You must be signed in to change notification settings - Fork 177
Use aria-live
for Panel notifications and form controls
#6819
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.
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
Comments
I'm honest, I have no idea if this is a god solution from an a11y standpoint. Do you have more information about it? Does the changed title actually help? |
Was wondering this myself or if there is rather a solution with aria live attributes. |
<title>
if the current page is locked
<title>
if the current page is lockedaria-live
for Panel notifications and form controls
I have rephrased the title. After reading a bit, I don't think changing the However, we should make use more of I have made a first experiment, but ran into the wall that after typing in a field, VoiceOver would start to announce my |
Description
When a page is locked (or not yet saved), sighted people can see an orange button that’s always on the screen as a reminder to save the page. Due to how vocalization works, it’s harder for screenreader users to notice that the page still needs to be saved, and they have to be extra careful not to lock the page for other users.
Expected behavior
One solution, proposed by one of our team members who is blind, would be to add an indication in the
<title>
of the page. Many apps and some CMSs use an asterisk at the start of the page title as a subtle but effective way to remind the author (sighted or blind) that something is up with the page, like the need for changes to be saved.Screenshots
Additional context
I filed this as a bug, because it concerns accessibility. For blind people who rely on screen readers, a crucial element of the panel interface is (not altogether missing, but) very hard to be aware of.
Thanks in advance!
The text was updated successfully, but these errors were encountered: