🎨 Palette: Enhance Mario Game UX and Accessibility#233
Conversation
…or score 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: Added explicit keyboard instructions, separated static "Score:" label from dynamic value, and added
aria-liveto the score value. Also addedpointer-events: noneto instructions overlay.🎯 Why: Users didn't know how to jump unless they looked at the source code. Screen readers would awkwardly read "Score: 1... Score: 2..." repeatedly. Now the score just announces the number politely, and the instructions are visible without blocking clicks.
♿ Accessibility: Separated static labels from dynamic values and applied
aria-live="polite"andaria-atomic="true"to the dynamic score value.📸 Tested via Playwright UI screenshot verification.
PR created automatically by Jules for task 3465017335443844792 started by @EiJackGH