🎨 Palette: [UX improvement] Add keyboard accessibility to welcome action cards#70
Conversation
Co-authored-by: thirdeyenation <133812267+thirdeyenation@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
role="button",tabindex="0", and keyboard event handlers (@keydown.enterand@keydown.space.prevent) to the custom.welcome-action-carddivs on the welcome screen. Updated CSS to include.welcome-action-card:focus-visiblestyling alongside the existing:hoverstyles.🎯 Why: To make the main navigation cards on the welcome screen fully accessible and navigable using the keyboard, improving the experience for users relying on keyboard navigation and screen readers.
📸 Before/After: The action cards now receive a clear focus outline (reusing the hover state border and background) when navigating via the
Tabkey, and can be activated usingEnterorSpace.♿ Accessibility: Fixes a critical keyboard accessibility issue by transforming non-semantic
divclick handlers into proper button-like interactions.PR created automatically by Jules for task 8073468358740675883 started by @thirdeyenation