Skip to content

🎨 Palette: [Add keyboard accessibility to interactive cards]#24

Open
Dev22603 wants to merge 1 commit into
mainfrom
palette-a11y-keyboard-cards-6177593963734064475
Open

🎨 Palette: [Add keyboard accessibility to interactive cards]#24
Dev22603 wants to merge 1 commit into
mainfrom
palette-a11y-keyboard-cards-6177593963734064475

Conversation

@Dev22603

Copy link
Copy Markdown
Owner

What: Added keyboard accessibility attributes (role, tabIndex), keyboard event handlers, and focus-visible styling to the interactive ProjectCard and ExperienceCard components.
Why: Non-native interactive elements (like custom cards implemented as div or motion.div) lack built-in keyboard accessibility, preventing users navigating via keyboard from triggering them or seeing a focus state.
Before/After: Video attached with visual verification showing clear focus outlines on cards when navigating using the Tab key, and modals opening via the Enter key.
Accessibility: Improved keyboard navigability by ensuring interactive cards can be focused and activated via keyboard, fulfilling WCAG guidelines for keyboard accessibility.

(Also included fixes for lint/build errors that blocked deployment: vite.config.js __dirname fix, eslint motion variable ignore, and index.css @import ordering).


PR created automatically by Jules for task 6177593963734064475 started by @Dev22603

Added keyboard accessibility attributes to custom interactive card components to allow non-mouse users to access them.

* Added role="button" and tabIndex={0} to `ProjectCard` and `ExperienceCard`.
* Added onKeyDown handlers to support Enter and Space key activation.
* Added focus-visible styling for visual focus indicators.
* Fixed build errors regarding vite configuration __dirname, index.css @import rules, and eslint config for unused variables.
* Added a journal entry for the learning outcome in .Jules/palette.md.

Co-authored-by: Dev22603 <92785712+Dev22603@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.

@netlify

netlify Bot commented Jun 12, 2026

Copy link
Copy Markdown

Deploy Preview for dev-bachani ready!

Name Link
🔨 Latest commit a745945
🔍 Latest deploy log https://app.netlify.com/projects/dev-bachani/deploys/6a2c644879cb0c00081255c2
😎 Deploy Preview https://deploy-preview-24--dev-bachani.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

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