🎨 Palette: Improve keyboard accessibility for scrollable table and interactive elements - #235
🎨 Palette: Improve keyboard accessibility for scrollable table and interactive elements#235n24q02m wants to merge 1 commit into
Conversation
…teractive elements Co-authored-by: n24q02m <135627235+n24q02m@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 a
tabindex="0",role="region", and anaria-labelto the table wrapper (.scroller) so that keyboard users can scroll and navigate it. I also updated the:focus-visiblepseudo-class for all interactive elements (nav a,.theme-toggle,.btn, and.scroller) to use a highly visibleoutlinewithoutline-offset, rather than relying solely on subtle brightness filters.🎯 Why:
Previously, the table container did not receive focus, preventing keyboard-only users from scrolling it if it overflowed horizontally on smaller screens. Additionally, the focus states on interactive elements were inadequate for visually identifying the active element, as a simple
brightnesschange does not meet WCAG contrast guidelines for focus indicators.📸 Before/After:
(Visual changes verified using Playwright screenshots, showing distinct outlines on focused elements).
♿ Accessibility:
PR created automatically by Jules for task 12286923531298649205 started by @n24q02m