You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there, greetings from nextcloud-libraries/nextcloud-dialogs#255
We are in the process of doing an A11y validation and one of the remarks was that or errors and messages (which are using toastify) are not read by screen readers.
This can be easily achieved by setting aria-live="polite" on the HTMLElement.
For errors and important information it is even recommended to use aria-live="assertive", however this interrupts whatever is currently being read out by the screenreader, so it should be "opt in" so it can be used for errors and similar stuff, but is not forced for "Your message was posted" kind of messages.
Hi there, greetings from nextcloud-libraries/nextcloud-dialogs#255
We are in the process of doing an A11y validation and one of the remarks was that or errors and messages (which are using toastify) are not read by screen readers.
This can be easily achieved by setting
aria-live="polite"
on the HTMLElement.For errors and important information it is even recommended to use
aria-live="assertive"
, however this interrupts whatever is currently being read out by the screenreader, so it should be "opt in" so it can be used for errors and similar stuff, but is not forced for "Your message was posted" kind of messages.Currently I implemented a PR in our lib which just manipulates the HTMLElement afterwards:
https://github.com/nextcloud/nextcloud-dialogs/pull/622/files
But of course it would be better if the library would allow this directly, so all users of the lib benefit from it.
Are you interested in fixing this and would accept a pull request + publish a new version afterwards?
The text was updated successfully, but these errors were encountered: