Skip to content

🎨 Palette: Improve Accordion Accessibility#229

Open
mknoufi wants to merge 1 commit into
mainfrom
palette/accordion-a11y-9388956399870153837
Open

🎨 Palette: Improve Accordion Accessibility#229
mknoufi wants to merge 1 commit into
mainfrom
palette/accordion-a11y-9388956399870153837

Conversation

@mknoufi

@mknoufi mknoufi commented Jul 9, 2026

Copy link
Copy Markdown
Owner

User description

💡 What: Added accessibilityRole="button", accessibilityState={{ expanded: isExpanded }}, accessibilityLabel={item.title}, and accessibilityHint to the TouchableOpacity in AccordionItemComponent.

🎯 Why: Custom Touchable components acting as accordion headers do not automatically announce their toggleable nature or their expanded/collapsed state to screen reader users, making them unintuitive or impossible to use properly via assistive tech. This change explicitly links the visual state to the accessibility tree.

📸 Before/After: No visual change. Purely an accessibility and screen reader improvement.

Accessibility:

  • Added accessibilityRole="button" so the element is announced correctly.
  • Added accessibilityState={{ expanded: isExpanded }} to convey the interactive state.
  • Added accessibilityLabel using the item's title for direct context.
  • Added accessibilityHint to clarify the action.

PR created automatically by Jules for task 9388956399870153837 started by @mknoufi


CodeAnt-AI Description

Make accordion headers easier to use with screen readers

What Changed

  • Accordion headers now announce themselves as buttons and expose whether the section is expanded or collapsed
  • Each header now includes the item title and a clear hint about what tapping it will do
  • The accordion’s open/close animation and visible behavior stay the same

Impact

✅ Clearer accordion navigation with screen readers
✅ Fewer confusing toggle controls
✅ Better access to expanded and collapsed state

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Co-authored-by: mknoufi <209227354+mknoufi@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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 @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@codeant-ai

codeant-ai Bot commented Jul 9, 2026

Copy link
Copy Markdown

CodeAnt AI is reviewing your PR.

@codeant-ai

codeant-ai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@codeant-ai codeant-ai Bot added the size:S This PR changes 10-29 lines, ignoring generated files label Jul 9, 2026
@sonarqubecloud

sonarqubecloud Bot commented Jul 9, 2026

Copy link
Copy Markdown

@codeant-ai

codeant-ai Bot commented Jul 9, 2026

Copy link
Copy Markdown

CodeAnt AI finished reviewing your PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:S This PR changes 10-29 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant