🎨 Palette: Improve keyboard and screen reader accessibility for modal triggers#78
Conversation
|
👋 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
role="button",aria-haspopup="dialog", and akeydownevent listener to handle theSpacebarkey for the "OSINT"<a href="#" id="sitrep-btn">anchor tags. Also explicitely added ane.preventDefault()inside the listener.🎯 Why: To ensure that assistive technologies like screen readers announce the anchor triggers as buttons instead of links, and to polyfill standard button behavior so that keyboard users can use the Spacebar to trigger the modal rather than relying solely on the Enter key.
📸 Before/After: Visual changes are not applicable as this was a semantic HTML markup and JavaScript logic improvement.
♿ Accessibility: Ensures that pseudo-buttons built with anchor tags meet the expectations of users relying on screen readers and keyboard navigation.
PR created automatically by Jules for task 12921593854475677702 started by @0m364