π¨ Palette: Use semantic time elements for clocks to prevent screen reader interruption#86
π¨ Palette: Use semantic time elements for clocks to prevent screen reader interruption#86schmug wants to merge 1 commit into
Conversation
β¦ader interruption Co-authored-by: schmug <38227427+schmug@users.noreply.github.com>
|
π Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a π emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
π‘ What: Replaced
<span aria-live="polite">with semantic<time dateTime={now.toISOString()}>for the clock components in the Desktop Taskbar and Mobile StatusBar.π― Why: Elements with
aria-live="polite"cause screen readers to announce changes every time the content updates. For continuously updating clocks, this causes a frustrating and disruptive experience by interrupting the user every minute. Using semantic<time>elements provides accessible structure without forcing repetitive announcements.βΏ Accessibility: Eliminates a major source of screen reader interruption while preserving semantic time representation for assistive technologies.
PR created automatically by Jules for task 2251755531838652623 started by @schmug