Skip to content

🎨 Palette: Add keyboard navigation accessibility improvements#1

Open
Divyansh3105 wants to merge 1 commit into
mainfrom
feat/a11y-keyboard-nav-14067703200257891692
Open

🎨 Palette: Add keyboard navigation accessibility improvements#1
Divyansh3105 wants to merge 1 commit into
mainfrom
feat/a11y-keyboard-nav-14067703200257891692

Conversation

@Divyansh3105
Copy link
Copy Markdown
Owner

🎨 Palette: Keyboard Navigation Enhancements

💡 What:

  • Added a "Skip to content" link that allows keyboard users to bypass the navigation and jump straight to the main content.
  • Added a global :focus-visible outline so that all interactive elements (like buttons and links) have clear visual feedback when focused via keyboard.

🎯 Why:

  • Basic keyboard accessibility is a fundamental requirement. Without a skip link, keyboard users have to manually tab through the entire navigation on every page load.
  • Many interactive elements (like .btn which had outline: none) lacked visible focus indicators, making it nearly impossible to track focus via keyboard.

📸 Before/After:
(Verified via Playwright verification screenshots during implementation)

Accessibility:

  • Greatly improved keyboard navigation and screen reader support.
  • Follows WCAG guidelines for focus visibility and bypass blocks.

PR created automatically by Jules for task 14067703200257891692 started by @Divyansh3105

- Added a hidden-by-default 'Skip to content' link at the top of the App, which becomes visible upon keyboard focus to assist screen reader and keyboard users.
- Introduced a global `:focus-visible` outline for interactive elements (using design tokens) to ensure proper visual feedback during keyboard navigation.
- Created a UX journal entry documenting these fundamental accessibility learnings.

Co-authored-by: Divyansh3105 <161134521+Divyansh3105@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 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 10, 2026

Deploy Preview for divyanshgarg3105 ready!

Name Link
🔨 Latest commit 6b0d2c3
🔍 Latest deploy log https://app.netlify.com/projects/divyanshgarg3105/deploys/6a00e8093899ad0008dbbb23
😎 Deploy Preview https://deploy-preview-1--divyanshgarg3105.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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