nextcloud-libraries / nextcloud-libraries/nextcloud-dialogs
Improve toast accessibility
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 8
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 37
Description
Some suggestions:
1. State the type of message
Announcing the type first (like "Error: [message]"), this is generally a good practice:
- It immediately communicates the severity to screen reader users
- It helps users mentally prepare for the information
- It provides context similar to how visual users get from the colors/icons
<div aria-live="assertive" aria-atomic="true">
<span class="visually-hidden">Error:</span>
<p>Your form submission failed. Please try again.</p>
</div>
2. Use role="alert"
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/alert_role
For stronger levels like error or warning, I think this fits the use case
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
No file, test, or entry point is named. Start by locating the toast implementation and its existing accessibility behavior, then determine which message types need announcements and whether the proposed alert semantics apply. Done means the agreed toast type is conveyed to screen reader users and the relevant accessibility behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100