Skip to content

🎨 Palette: [Project Card Accessibility] Make clickable cards accessible to keyboard users#23

Open
Dev22603 wants to merge 1 commit into
mainfrom
ux-project-card-accessibility-13653455256335645682
Open

🎨 Palette: [Project Card Accessibility] Make clickable cards accessible to keyboard users#23
Dev22603 wants to merge 1 commit into
mainfrom
ux-project-card-accessibility-13653455256335645682

Conversation

@Dev22603

Copy link
Copy Markdown
Owner

💡 What

Improved the accessibility of the ProjectCard component by adding proper keyboard interaction and screen reader support to the clickable motion.div.

🎯 Why

The ProjectCard elements were entirely inaccessible to keyboard-only and screen reader users. They were acting as buttons but lacked the correct semantic HTML roles, could not be focused via Tab, and did not respond to Enter or Space key presses. Making them accessible ensures a far better, inclusive UX.

📸 Before/After

Before: The project cards could only be opened via mouse click. They were skipped in the keyboard navigation tab order.
After: The project cards can be focused using Tab with a visible indigo ring (focus-visible), and activated via the Enter or Space keys. Visual verification completed using Playwright tests showing proper focus outlines.

♿ Accessibility

  • Added role="button" and tabIndex={0}.
  • Added onKeyDown listener.
  • Added aria-label pointing to the project name.
  • Added visible focus rings.

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

- Added `role="button"` and `tabIndex={0}` to the interactive `motion.div` in `ProjectCard.jsx`.
- Added an `onKeyDown` handler to allow triggering the card using Enter or Space keys.
- Added `aria-label` providing screen readers with the context of opening the project details.
- Added `focus-visible:ring-2 focus-visible:ring-indigo-500` for keyboard-only navigation visibility.

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

Copy link
Copy Markdown

Deploy Preview for dev-bachani ready!

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