Docs: warn about usability / accessibility issues of Toasts
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 175k
- Forks
- 78.6k
- Avg merge
- 7h 19m
- Merged PRs (30d)
- 35
Description
I was just reading GitHub's Primer Design system page on their decision to no longer uses Toasts (https://primer.style/accessibility/toasts/) and it's put me off from ever using them :-) . There are many accessibility and usability issues which I hadn't previously considered.
I know Bootstrap does a great job in making it's components as accessible as possible and provides helpful accessibility docs where necessary. I think it could be a good idea to highlight some of the shortcomings, perhaps more info in the Accessibility section or a warning/info callout at the top suggesting to consider using a different component/pattern?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Toasts Accessibility section linked in the issue and compare it with GitHub Primer's referenced guidance. Update the Toasts documentation to clearly explain the usability and accessibility concerns and point readers toward considering another component or pattern. Done means the page contains the requested warning or guidance; no tests are mentioned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bootstrap
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100