🎨 Palette: Improve accessibility of Drilldown Navigation component#201
🎨 Palette: Improve accessibility of Drilldown Navigation component#201aarjava wants to merge 2 commits into
Conversation
- Changed wrapper to `<nav aria-label="Breadcrumb">` - Added `aria-current="step"` to the active level button - Added `aria-live="polite"` to the dynamic progress counter - Ensured `focus-visible` styling is applied for keyboard navigation - Hid decorative chevron icons from screen readers with `aria-hidden="true"` Co-authored-by: aarjava <218419324+aarjava@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. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Changed wrapper to `<nav aria-label="Breadcrumb">` - Added `aria-current="step"` to the active level button - Added `aria-live="polite"` to the dynamic progress counter - Ensured `focus-visible` styling is applied for keyboard navigation - Hid decorative chevron icons from screen readers with `aria-hidden="true"` Co-authored-by: aarjava <218419324+aarjava@users.noreply.github.com>
1 participant
🎨 Palette: Improve accessibility of Drilldown Navigation component
💡 What:
divto a semantic<nav aria-label="Breadcrumb">.aria-current="step"to the currently active navigation level button.aria-live="polite"to the "Level X of Y" counter text so screen readers announce it when the level changes.focus-visiblestyling (focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-neutral-400) to all buttons for explicit keyboard navigation visibility.aria-hidden="true".🎯 Why:
Custom drilldown/tap-through patterns often lack the inherent semantic structure of standard HTML elements. While visually functional, this component was difficult to navigate with a screen reader because the active step wasn't announced, the step counter changes were silent, and there were no explicit focus rings for keyboard users.
📸 Before/After: No major visual layout changes, but keyboard navigation now clearly highlights the focused button with a neutral ring outline.
♿ Accessibility: This directly improves WCAG compliance for Focus Visible (2.4.7), Name/Role/Value (4.1.2), and Status Messages (4.1.3).
PR created automatically by Jules for task 9004429973398249309 started by @aarjava