-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
fix: turn section into live region #306 #436
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
As a proposal, we could have a way to deprecate the |
Hm, I might need to update from main before it can be merged. I'll take care of that. |
Is there any update on this PR? I could do with it as we have automated accessibility tests which it fails for... And for users 🙂 |
I kept merging main into this, but I don't think it'll ever actually get merged, so I gave up :( |
@tricinel Why do you think it will not be merged? |
There are plenty of PRs unmerged 🤷 |
Thanks, merged. My guess is that not a lot of people use |
Issue: Older screen readers don't announce individual toasts
li
elements are not allowed to have therole="status"
tag as per MDN.Fixes #306
What has been done:
aria-live
,aria-atomic
androle
tags from the<li>
element (the Toast)aria-live
,aria-relevant
andaria-atomic
to the containing<section>
elementimportant
key from theToastT
typeScreenshots/Videos:
Screen.Recording.2024-03-20.at.09.24.41.mov
Visually, not changed. Tests all pass. Build passes.
Notes
This is be a breaking change because we remove the
important
key from theToastT
type, meaning that consumers will get a type error if they've been using the key so far. Happy to discuss another solution to this, if any.