🎨 Palette: Keyboard Accessible Dropdown#34
Conversation
- Added `aria-controls` to the trigger button and `id` to the dropdown menu to link them for screen readers. - Added `aria-hidden="true"` to the decorative dropdown arrow. - Modified `assets/css/custom.css` to add `focus-visible` and `focus-within` visibility rules so that the dropdown natively works for keyboard users. - Added UX journal entry for the CSS-only keyboard accessibility pattern. Co-authored-by: divineforge <1146195+divineforge@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 keyboard accessibility to the ecosystem dropdown menu using purely CSS techniques, without requiring JavaScript. Added a journal entry to document the pattern.
🎯 Why: Keyboard users cannot open dropdown menus triggered purely by
:hover. This prevents them from accessing the internal ecosystem navigation links.♿ Accessibility: Users navigating with the "Tab" key can now open the dropdown menu natively since the menu visibility includes
:focus-visibleon the button and:focus-withinon the dropdown itself. Also linked elements witharia-controlsfor screen reader semantic pairing.PR created automatically by Jules for task 14063233658637650817 started by @divineforge