🎨 Palette: Improve Navbar keyboard and screen reader accessibility#111
🎨 Palette: Improve Navbar keyboard and screen reader accessibility#111belpythons wants to merge 1 commit into
Conversation
Co-authored-by: belpythons <187399139+belpythons@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
aria-expandedandaria-labelattributes to the mobile menu toggle and Forum dropdown toggle inNavbar.jsx. Also added consistentfocus-visible:outline-none focus-visible:ring-2 focus-visible:ring-accent-500classes to all interactive theme and menu toggle buttons.Why:
The mobile menu button was an icon-only button without an
aria-label, making it inaccessible to screen reader users. The interactive disclosure widgets (mobile menu and dropdowns) did not communicate their open/closed state (aria-expanded). Furthermore, interactive elements lacked explicit focus indicators, hindering keyboard navigation.Before/After:
aria-label. All toggles clearly display a focus ring when navigated via keyboard. Screen readers now announce whether the mobile menu or forum dropdown is expanded or collapsed.Accessibility:
aria-expanded.focus-visiblering utilities.PR created automatically by Jules for task 2168571040023479844 started by @belpythons