Conversation
- Add tabIndex={0}, role="button", and aria-disabled="true" to disabled menu items
- Ensure tooltips appear on keyboard focus
- Add aria-label for screen reader support
- Add visible focus ring
- Create .Jules/palette.md for UX learnings
Co-authored-by: isaidj <44456363+isaidj@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. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
💡 What: Improved accessibility for disabled menu items in
DataMenu.tsx.🎯 Why: Disabled items were not keyboard focusable, making the 'Coming Soon' tooltip inaccessible to keyboard users and screen readers.
📸 Before/After: Added
tabIndex={0},role="button", and focus styles. Tooltips now appear on focus.♿ Accessibility:
tabIndex={0}to allow keyboard focus.role="button"andaria-disabled="true".aria-labelwith item name and status.group-focus).PR created automatically by Jules for task 3042339214050906164 started by @isaidj