Conversation
revu-bot
left a comment
There was a problem hiding this comment.
Review Summary
This PR implements a workaround for screen reader vocalization of toast notifications by creating a separate live region. While the approach addresses the immediate accessibility issue, there are several CRITICAL and IMPORTANT concerns that need attention:
| Severity | Issue | Impact |
|---|---|---|
| CRITICAL | Missing Vue imports | Code will fail at runtime |
| IMPORTANT | Race condition with nested timeouts | Unreliable screen reader announcements |
| IMPORTANT | Toast removal not handled | Memory leak and stale announcements |
| MINOR | Magic numbers without explanation | Reduced maintainability |
The core strategy (separate live region + aria-live="off" on alerts) is sound, but the implementation needs refinement for production reliability.
| <div | ||
| v-if="liveMessage" | ||
| role="status" | ||
| aria-live="polite" |
There was a problem hiding this comment.
rendre dynamique l'aria-live, sinon on perd la logique alert -> aria-live=assertive et polite -> aria-live=polite
035c839 to
36f3e7d
Compare
|
|
🎉 Deployment for commit 36f3e7d : Ingresses
Docker images
|



Ticket(s) lié(s)
https://jira-mcas.atlassian.net/jira/software/c/projects/VAO/boards/336?selectedIssue=VAO-1233
Description
Force la restitution des toasts
Screenshot / liens loom
Check-list
console.log<script lang="ts">Testing instructions