🎨 Palette: Add keyboard focus visible states and fix CSS-only dropdown accessibility#40
Conversation
…nteractive buttons - Adjusted `:focus-within` to apply to `.gzen-nav-dropdown` so that the hidden `.gzen-nav-dropdown-menu` is visible when the trigger button receives focus via keyboard tabbing. - Added explicit `:focus-visible` outline styles with `var(--gzen-saffron)` across global interactive elements (`a`, `button`, `input`, `select`, `textarea`, `[role="button"]`) to provide clear visual feedback to keyboard users. - Appended specific Tailwind `focus-visible` classes to Lunar Hero interactive buttons (`#lunar-prev`, `#lunar-today`, `#lunar-next`) for consistent ring visibility. - Created `palette.md` to journal the learning concerning CSS-only accessible dropdowns. - Fixed minor markdownlint error in Yin-Yang articles. 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. |
Deploying gzen with
|
| Latest commit: |
a6a4220
|
| Status: | 🚫 Build failed. |
…nteractive buttons - Adjusted `:focus-within` to apply to `.gzen-nav-dropdown` so that the hidden `.gzen-nav-dropdown-menu` is visible when the trigger button receives focus via keyboard tabbing. - Added explicit `:focus-visible` outline styles with `var(--gzen-saffron)` across global interactive elements (`a`, `button`, `input`, `select`, `textarea`, `[role="button"]`) to provide clear visual feedback to keyboard users. - Appended specific Tailwind `focus-visible` classes to Lunar Hero interactive buttons (`#lunar-prev`, `#lunar-today`, `#lunar-next`) for consistent ring visibility. - Created `palette.md` to journal the learning concerning CSS-only accessible dropdowns. - Fixed minor markdownlint error in Yin-Yang articles. Co-authored-by: divineforge <1146195+divineforge@users.noreply.github.com>
1 participant
💡 What:
:focus-visibleoutlines for interactive elements globally using the brand's saffron accent color.🎯 Why:
Previously, users navigating with a keyboard could tab to the ecosystem dropdown, but its menu remained hidden because it was relying solely on the hover state or a structurally flawed
:focus-withinon the invisible menu itself. Adding a global:focus-visiblestate across standard interactive elements and specific buttons improves navigation feedback. Good UX is invisible—but accessibility must be apparent.♿ Accessibility:
🎨 Palette was here.
PR created automatically by Jules for task 6164125043173758410 started by @divineforge