Skip to content

🎨 Palette: Add keyboard accessibility to interactive cards#27

Open
Dev22603 wants to merge 1 commit into
mainfrom
palette-interactive-cards-a11y-10952231728591113856
Open

🎨 Palette: Add keyboard accessibility to interactive cards#27
Dev22603 wants to merge 1 commit into
mainfrom
palette-interactive-cards-a11y-10952231728591113856

Conversation

@Dev22603

Copy link
Copy Markdown
Owner

💡 What:

Added keyboard accessibility support to interactive cards (ExperienceCard and ProjectCard) by implementing role, tabIndex, keydown handlers (for Enter and Space keys), and clear focus-visible styles using the primary color ring.

🎯 Why:

The application uses motion.div elements as clickable interactive cards for the Experience and Project sections. While mouse users could click them, these elements were invisible to keyboard navigation, making it impossible for users relying on keyboard navigation or screen readers to trigger their actions (opening modals, external links, etc.).

📸 Before/After:

Before: Pressing the Tab key skipped over the interactive cards.
After: Pressing the Tab key properly focuses the cards, adding a clear var(--color-primary) focus ring around them, and pressing Enter or Space activates their onClick handlers. Verification screenshot has been captured via Playwright demonstrating this visual state.

♿ Accessibility:

  • Added role="button" and tabIndex={0} to ensure semantic meaning and focusability.
  • Added onKeyDown handlers mapping the Enter and Space keys to their respective click actions, complete with e.preventDefault() to prevent the viewport from scrolling when the Space key is pressed.
  • Added focus-visible:ring-2 focus-visible:ring-[var(--color-primary)] styles to ensure focus states meet contrast requirements against the dark background.

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

Added `role="button"`, `tabIndex={0}`, `onKeyDown` handlers, and `focus-visible` classes to `ExperienceCard` and `ProjectCard` to ensure users relying on keyboards can focus and interact with these elements. Also fixed minor linting and build issues in configuration files to ensure the pipeline runs cleanly.

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

Copy link
Copy Markdown

Deploy Preview for dev-bachani ready!

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