🎨 Palette: Improve screen reader UX for dynamic game score - #258
Conversation
Co-authored-by: EiJackGH <172181576+EiJackGH@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: Extracted the static "Score: " text from the dynamic score value in the Mario game view and added
aria-live="polite"to the dynamic score container.🎯 Why: Dynamic text changes, like game scores increasing, are invisible to screen readers unless explicitly marked as a live region. Furthermore, keeping static text out of the live region ensures the screen reader only announces the new number rather than repeatedly saying "Score: [number]".
📸 Before/After: Visual presentation is identical. Screen reader experience is improved.
♿ Accessibility: Added
aria-live="polite"to dynamically changing text value to ensure updates are announced to screen reader users without being intrusive.PR created automatically by Jules for task 13331026816469925169 started by @EiJackGH