🎨 Palette: Make OSINT modal buttons keyboard and screen reader accessible#107
Conversation
…ible Added `role="button"` and `aria-haspopup="dialog"` to the `#sitrep-btn` modal trigger links across `concepts.html`, `products.html`, and `contact.html`. Furthermore, added a keyboard listener for the `Spacebar` key in `modal.js` to ensure the anchor tags completely emulate native `<button>` accessibility and interactions for screen readers and keyboard users. Added a learning about this to the Palette journal.
|
👋 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. |
1 participant
💡 What: Added
role="button"andaria-haspopup="dialog"to theid="sitrep-btn"links and bound a Spacebar key listener.🎯 Why: To ensure that keyboard and screen reader users can interact with the OSINT modal button the same way they would with a native
<button>, as native anchor tags are only activated by theEnterkey.📸 Before/After: The changes are purely structural semantic and behavioral; there is no visual change.
♿ Accessibility: Screen readers will now announce these links as buttons that trigger a dialog, and keyboard users can now activate them using the Spacebar.
PR created automatically by Jules for task 8847636437962877575 started by @0m364