Skip to content

🎨 Palette: Add keyboard accessibility to interactive cards#33

Open
Dev22603 wants to merge 1 commit into
mainfrom
palette/keyboard-accessibility-cards-9696534159621962946
Open

🎨 Palette: Add keyboard accessibility to interactive cards#33
Dev22603 wants to merge 1 commit into
mainfrom
palette/keyboard-accessibility-cards-9696534159621962946

Conversation

@Dev22603

Copy link
Copy Markdown
Owner

💡 What:
Added keyboard support to the non-native interactive components ProjectCard and ExperienceCard.

🎯 Why:
These components act as buttons to open modals or follow external links, but because they are constructed with motion.div rather than native <button> or <a> elements, they couldn't be focused via the 'Tab' key or activated via 'Enter' or 'Space'. This change enables users relying on keyboards and screen readers to interact with these elements smoothly.

📸 Before/After:

  • Before: Users pressing the 'Tab' key would skip entirely over ProjectCard and ExperienceCard elements. No focus ring was visible.
  • After: Users can 'Tab' to these cards. Focused cards now display an elegant var(--color-primary) glowing ring using Tailwind's focus-visible pseudo-class (preventing the ring from showing during normal mouse clicks).

♿ Accessibility:

  • role="button" added to give screen readers proper semantics.
  • tabIndex={0} added to include the cards in the document tab order.
  • onKeyDown added to simulate a click when 'Enter' or 'Space' is pressed (including e.preventDefault() on 'Space' to prevent unwanted page scrolling).
  • focus-visible styling added to maintain visual hierarchy when navigating via keyboard.

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

Added `role="button"`, `tabIndex={0}`, keyboard event handlers, and `focus-visible` states to `ProjectCard` and `ExperienceCard` components to enable keyboard navigation. Fixed linting errors related to framer-motion and resolved Vite build configuration issues.

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 21, 2026

Copy link
Copy Markdown

Deploy Preview for dev-bachani ready!

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