🎨 Palette: [UX improvement] Improve Navbar Accessibility#113
Conversation
…vbar widgets 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-haspopupattributes, as well asfocus-visibleoutline styles, to the mobile menu and dropdown toggles in the Navbar. Also fixed an unused variable linting error.Why: To ensure that interactive disclosure widgets are fully accessible to screen reader users and can be easily navigated using a keyboard.
Before/After:
Accessibility: This directly addresses WCAG standards for Name, Role, Value (4.1.2) by providing state information (
aria-expanded) to assistive technologies and Focus Visible (2.4.7) by ensuring keyboard users can see which element has focus.PR created automatically by Jules for task 10066964687456004852 started by @belpythons