-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add role to FocusZone in BasePickerListBelow #10867
Conversation
Asset size changes
Baseline commit: 58691b0adf66ee810bbc9b055c92b76706c67dc0 (build) |
Component Perf AnalysisNo significant results to display. All results
|
@mattlind Thanks for submitting this fix! It looks like it would break aria rules for users who don't have role="listitem" already on their selected items. I think that either adding |
I did it this way because that was how the other instance was doing the same thing above.
|
@mattlind That makes sense then. Approved to bring everything in line. |
🎉 Handy links: |
is it possible to cherry pick this change to version 6? |
* role * Change files
#### Pull request checklist - [ ] Addresses an existing issue: Fixes #0000 - [ ] Include a change request file using `$ yarn change` #### Description of changes We are having one accessibility work item (Bug 3797473) and to fix this we need to add a change in Fabric. But we noticed some one has already added a fix for this and released that In 7.55.3 (PR #10867). Since it may take some time to migrate to Fabric 7 this PR is cherrypicking/backporting this change to Fabric 6. #### Focus areas to test (optional) ###### Microsoft Reviewers: [Open in CodeFlow](http://wpcp.azurewebsites.net/CodeFlowProtocolProxy2.php?pullrequest=https://github.com/OfficeDev/office-ui-fabric-react/pull/11387)
🎉 Handy links: |
Pull request checklist
$ yarn change
Description of changes
Added role attribute to the FocusZone that contains the selected items for BasePickerListBelow. Previously there was no role set so adding a role like "list-item" to an item produced by the onRenderItem callback didn't read out in screen readers as item number n of m.
Focus areas to test
Microsoft Reviewers: Open in CodeFlow