🎨 Palette: Make OSINT anchor buttons accessible#116
Conversation
💡 What: Added `role="button"`, `aria-haspopup="dialog"`, and explicit Space/Spacebar keydown handling (via JS) to `#sitrep-btn` anchors across HTML files. 🎯 Why: Native anchors with `href="#"` used to open modals do not inherently support the Space key for activation, and screen readers read them merely as links. This makes them fully accessible buttons. 📸 Before/After: Visuals didn't change, but semantics and keyboard UX are now robust. ♿ Accessibility: Improved screen reader announcements and corrected keyboard interaction handling for the `Space` key.
|
👋 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",aria-haspopup="dialog", and explicit Space/Spacebar keydown handling (via JS) to#sitrep-btnanchors across HTML files.🎯 Why: Native anchors with
href="#"used to open modals do not inherently support the Space key for activation, and screen readers read them merely as links. This makes them fully accessible buttons.📸 Before/After: Visuals didn't change, but semantics and keyboard UX are now robust.
♿ Accessibility: Improved screen reader announcements and corrected keyboard interaction handling for the
Spacekey.PR created automatically by Jules for task 965712203566196730 started by @0m364