aio-notification close button needs a more specific accessible label
See original GitHub issueThe close button for <aio-notification>
only reads “Close” without additional context. For assistive technology users, it’s not clear what is being closed. While adding some additional label content would help this, it would probably also help to make the whole component something like role="group"
to communicate the whole notification is one “thing”.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Close button should be <button>, have accessible text. #260
At present, the close button is just a <span> , so it can't have focus and therefore can't be navigated to with a...
Read more >Labeling Controls | Web Accessibility Initiative (WAI) - W3C
Overview. Provide labels to identify all form controls, including text fields, checkboxes, radio buttons, and drop-down menus. In most cases ...
Read more >Change message notifications on iPhone - Apple Support (AE)
Go to Settings > Notifications > Messages. Choose options, including the following: Turn Allow Notifications and immediate delivery for Time Sensitive ...
Read more >Notification close button does not have meaningful label
Notification close button does not have meaningful label. Status: Assignee: Priority: Resolution: Closed. Jun Pataleta. Major. Fixed. More ...
Read more >FAQs on Synchrony Credit Cards, Apps, and More
Have a question about your account? See our FAQ section for quick answers. Call the card-specific toll-free number on your statement or the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@noobyogi0010 two things:
role="group"
and see how it impacts the experience with a screen readerThis issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.