Repository navigation
🎨 Palette: Improve screen reader a11y for custom buttons - #14
LeanBitLab wants to merge 1 commit into
Conversation
- Add `role = Role.Button` to `Modifier.clickable` across custom UI buttons in `VideoPage.kt` to ensure screen readers identify them as interactive elements. - Set `contentDescription = null` for the ExpandLess/ExpandMore icon where it sits next to descriptive text, avoiding duplicate screen reader announcements.
|
👋 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. |
💡 What: Added explicit
Role.Buttonsemantic roles to customclickableCompose components inVideoPage.kt, and removed a redundantcontentDescriptionon the expand icon.🎯 Why: Screen readers would previously read custom buttons simply as text or generic clickable zones. The expand icon also duplicated the "Show more"/"Show less" text right next to it, making navigation tedious.
📸 Before/After: N/A (Visual UI remains unchanged)
♿ Accessibility: Ensures correct interactive component announcements by TalkBack/VoiceOver and removes confusing redundant announcements.
PR created automatically by Jules for task 6178877680850775327 started by @LeanBitLab