π¨ Palette: Semantic and accessible navigation - #48
Conversation
- Convert landing page cards from `div` to `<a>` tags. - Convert subproject "Back" buttons from `button` to `<a>` tags. - Remove redundant navigation logic in `script.js`. - Add `:focus-visible` styles for better keyboard accessibility. - Set consistent `lang="es"` for ISTEC educational context. 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. |
π¨ Palette: Semantic and accessible navigation
π‘ What
Refactored the project's navigation system to use semantic HTML
<a>tags instead of JavaScriptonclickhandlers ondivandbuttonelements.π― Why
The previous implementation was inaccessible to keyboard users and screen readers, and it broke standard browser features like "Open in new tab". By using semantic links, we improve accessibility, SEO, and the overall robustness of the application.
βΏ Accessibility
<a>tags for all navigation elements.:focus-visiblerings to cards and buttons to ensure clear visual feedback during keyboard navigation.lang="es"is set across all pages for consistency with the ISTEC educational target audience.β Verification
script.jsas it is no longer required for navigation.PR created automatically by Jules for task 4085075305909633334 started by @ISTEC-FOR340