Skip to content

🎨 Palette: Keyboard Accessibility for Interactive Cards#40

Open
Dev22603 wants to merge 1 commit into
mainfrom
feature/palette-keyboard-a11y-2673098536693846777
Open

🎨 Palette: Keyboard Accessibility for Interactive Cards#40
Dev22603 wants to merge 1 commit into
mainfrom
feature/palette-keyboard-a11y-2673098536693846777

Conversation

@Dev22603

Copy link
Copy Markdown
Owner

💡 What

Added full keyboard accessibility to the ExperienceCard and ProjectCard components, transforming them from non-interactive div elements into fully functional, accessible button-like interactions.

🎯 Why

Previously, these card components were implemented using motion.div with an onClick handler. This rendered them inaccessible to keyboard users and screen readers, as they couldn't be navigated to via the Tab key or activated using Enter or Space. This change ensures everyone can access the detailed views for experiences and projects.

📸 Before/After

Screenshot captured in Playwright showing the new focus-visible ring on the Experience card.
Focus Ring

♿ Accessibility

  • Added role="button" and tabIndex={0} to enable focus and denote functionality.
  • Implemented onKeyDown to allow interaction via Enter and Space keys (with proper event handling to prevent page scroll on Space).
  • Carefully designed the ProjectCard keydown handler to ignore events originating from nested anchor tags to prevent unintentional double-triggering.
  • Added descriptive aria-labels to give screen reader users context about the action.
  • Added focus-visible utility classes to provide a clear, high-contrast focus ring that adheres to the site's primary color theme.

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

- Added `role="button"` and `tabIndex={0}` to `ExperienceCard` and `ProjectCard` div elements.
- Implemented `onKeyDown` handlers to support 'Enter' and 'Space' activation.
- Prevented default scrolling behavior on 'Space' keypress.
- Ensured nested interactive elements (e.g. links in ProjectCard) do not double-trigger card activation by checking `e.target` in the keydown handler.
- Added `focus-visible` styling for visible keyboard focus indication.
- Included descriptive `aria-label` attributes.
- Fixed an existing ESLint config issue triggering false-positive 'motion' unused variables.
- Fixed an existing index.css CSS import order warning.

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

Copy link
Copy Markdown

Deploy Preview for dev-bachani ready!

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