Fix redundant screen reader announcements for expander buttons #813
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Description
This PR fixes redundant screen reader announcements for the collapsible category buttons in the left navigation drawer.
Why
When using Windows Narrator with the app, expanding/collapsing a category in the navigation drawer caused the expanded/collapsed state to be announced twice. For example: "Basic Input, collapsed, button, collapsed, 1 of 11" - the "collapsed" state is announced twice.
This happened because:
accessibilityLabelprop contained the state text (e.g., "Basic Input, collapsed")accessibilityState={{expanded: isExpanded}}prop also communicated the state to the screen readerWhat
accessibilityLabelprop, keeping only the category label. TheaccessibilityStateprop already handles communicating the expanded state to screen readers.accessibilityState={{expanded: isExpanded}}to ensure the state is properly communicated (this file was missing the accessibility state prop).Screenshots
N/A - Accessibility fix, no visual changes
Testing
Microsoft Reviewers: Open in CodeFlow