🎨 Palette: Improve landing page and project navigation accessibility - #45
🎨 Palette: Improve landing page and project navigation accessibility#45ISTEC-FOR340 wants to merge 1 commit into
Conversation
This commit enhances the user experience and accessibility by: 1. Converting non-semantic `div` cards into semantic `<a>` tags for native navigation and keyboard support. 2. Replacing nested `<button>` elements with `<span>` to maintain valid HTML within links. 3. Adding explicit `:focus-visible` styles with high-contrast focus rings for better keyboard navigation visibility. 4. Converting project "Back" buttons into semantic `<a>` tags. 5. Standardizing the `lang="es"` attribute across all HTML files for better screen reader support in the target language. 6. Removing redundant navigation logic from `script.js`. 7. Ensuring focus rings are not clipped by glassmorphism cards by updating `overflow` properties. Co-authored-by: ISTEC-FOR340 <269002038+ISTEC-FOR340@users.noreply.github.com>
|
👋 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
💡 What: Improved accessibility and semantic structure of the landing page and project navigation.
🎯 Why: The previous implementation used non-semantic
divelements withonclicklisteners for navigation, which made the site inaccessible to keyboard and screen reader users. Additionally, focus indicators were missing or clipped.♿ Accessibility Improvements:
<a>tags for all navigation.:focus-visibleindicators.lang="es"for Spanish-speaking audience.PR created automatically by Jules for task 13122572610622220354 started by @ISTEC-FOR340