Skip to content

🎨 Palette: Add keyboard accessibility to clickable cards#10

Open
Dev22603 wants to merge 1 commit into
mainfrom
jules-ux-accessibility-1850231668775224118
Open

🎨 Palette: Add keyboard accessibility to clickable cards#10
Dev22603 wants to merge 1 commit into
mainfrom
jules-ux-accessibility-1850231668775224118

Conversation

@Dev22603
Copy link
Copy Markdown
Owner

This PR introduces a micro-UX enhancement by adding keyboard accessibility to the ProjectCard and ExperienceCard components.

  • 💡 What: Integrated role="button", tabIndex={0}, an onKeyDown handler, and Tailwind's focus-visible utility classes to the clickable <motion.div> elements in both components.
  • 🎯 Why: Previously, these custom clickable components could not be focused or interacted with using a keyboard, violating accessibility standards.
  • ♿ Accessibility: Keyboard users can now tab through the cards and open the respective modals or external links by pressing Enter or Space, with a clear visual focus ring indicating the currently focused card.

Additionally, minor fixes were applied to eslint.config.js, vite.config.js, and index.css to resolve linter errors and build warnings encountered during testing. The .Jules/palette.md journal has been updated with these learnings.


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

- 💡 What: Added `role="button"`, `tabIndex={0}`, keyboard event handlers, and `focus-visible` styles to `ProjectCard` and `ExperienceCard` components.
- 🎯 Why: Non-interactive elements (like `motion.div`) acting as clickable cards lacked native keyboard focusability and interaction, making them inaccessible for users navigating via keyboard.
- ♿ Accessibility: Improved keyboard navigation by allowing users to focus on cards and trigger their modals/actions using Enter or Space, with clear visual feedback from a focus ring.
- Fixed `__dirname` issue in `vite.config.js` and CSS import warning in `index.css` to ensure build checks pass.

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
Copy link
Copy Markdown

netlify Bot commented May 30, 2026

Deploy Preview for dev-bachani ready!

Name Link
🔨 Latest commit 84cba2c
🔍 Latest deploy log https://app.netlify.com/projects/dev-bachani/deploys/6a1b44603573d20008ceaacb
😎 Deploy Preview https://deploy-preview-10--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