🎨 Palette: Fix Dropdown Keyboard Accessibility#37
Conversation
…rience - Update CSS for dropdown menu to ensure `:focus-within` targets the visible `.gzen-nav-dropdown` parent so keyboard users can navigate into the hidden menu. - Add `aria-hidden="true"` to the decorative dropdown arrow in the header so it is ignored by screen readers. - Create a journal entry documenting the learning about `visibility: hidden` and focus states. 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. |
🎨 Palette: Fix Dropdown Keyboard Accessibility
💡 What:
.gzen-nav-dropdown-menu:focus-within) to targeting the parent container (.gzen-nav-dropdown:focus-within .gzen-nav-dropdown-menu).aria-hidden="true"to the decorative dropdown arrow (▾) in the header.visibility: hiddenelements.🎯 Why:
visibility: hidden, it and its children are completely removed from the tab order. Keyboard users could not tab into the dropdown menu to trigger its:focus-withinstate, making the ecosystem links inaccessible. By applying the:focus-withinto the parent.gzen-nav-dropdown, tabbing to the visible trigger button now correctly reveals the menu, allowing users to tab through its items.♿ Accessibility:
PR created automatically by Jules for task 770036250948059044 started by @divineforge