Skip to content

🎨 Palette: Improve keyboard accessibility and focus states - #219

Open
n24q02m wants to merge 1 commit into
mainfrom
palette/fix-focus-states-16294318137641775467
Open

🎨 Palette: Improve keyboard accessibility and focus states#219
n24q02m wants to merge 1 commit into
mainfrom
palette/fix-focus-states-16294318137641775467

Conversation

@n24q02m

@n24q02m n24q02m commented Sep 4, 2026

Copy link
Copy Markdown
Owner

💡 What: Added tabindex="0", role="region", and aria-label to the table's .scroller container. Added clear, distinct :focus-visible outlines to all major interactive elements.
🎯 Why: Without these changes, keyboard-only users could not scroll the data table horizontally if it overflowed on smaller screens, and the default focus indicators were too subtle or missing on interactive buttons/links.
📸 Before/After: Focus states now display a solid 2px accent outline with an offset, improving visibility over standard browser defaults.
♿ Accessibility: Addresses WCAG Success Criteria 2.1.1 (Keyboard) and 2.4.7 (Focus Visible) by making overflow regions keyboard-navigable and ensuring clear visual focus rings.


PR created automatically by Jules for task 16294318137641775467 started by @n24q02m

Added explicit tab indexing, ARIA labels, and `role="region"` to the scrollable data table container, ensuring keyboard users can scroll it independently. Also added enhanced visible focus rings to interactive elements (`.nav a`, `.btn`, `.theme-toggle`, and `.scroller`) for clearer keyboard navigation indicators.

Co-authored-by: n24q02m <135627235+n24q02m@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant