馃帹 Palette: Add Skip to Content Link for Improved Accessibility - #56
Conversation
- Added a "Skip to content" link in `RootLayout` for keyboard accessibility.
- Moved `Intro` component inside `<main>` tag in `Home` page.
- Added `id="main-content"` and `tabIndex={-1}` to `<main>` for reliable skip-link targeting.
- Documented learning in `.Jules/palette.md`.
|
馃憢 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
1 participant
This PR adds a "Skip to content" link to the portfolio website, which is a standard accessibility best practice for single-page applications with many navigation items.
Key Changes:
Intro(hero) component inside the<main>tag insrc/app/page.tsx. This ensures that skipping to content actually takes the user to the start of the meaningful content on the page.id="main-content"andtabIndex={-1}to the<main>element to ensure that focus is correctly moved and handled when the skip link is used..Jules/palette.mdreflecting on the importance of skip links in SPAs.Verification:
#main-contentarea.pnpm lintandpnpm buildto ensure no regressions.PR created automatically by Jules for task 10977605348866409429 started by @amrabed