microsoft / microsoft/react-native-windows
Office API Needs for Accessibility on Fabric
Open
@vineethkuttan is already working on this.
Since Dec 9, 2025.
API: Completion
Area: Accessibility
Area: Fabric
enhancement
New Architecture
Workstream: Accessibility
Workstream: Component Parity
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
For full parity with the current implementations of accessibility in Windows and Office, some props may need to be added that extend the set of functionalities in react-native core. Below are the patterns and props required to get to parity beyond what is spelled out above. Where Office has extended View props for its scenarios, we could consider alignment with the new (and preferred?) aria naming conventions introduced with 0.71.
| Task | Description | Status |
|---|---|---|
| AccessibilityInfo | Add support for AccessibilityInfo Native Module | Not Started, Est. 1-2 weeks |
| accessibilityControls / aria-controls (Office) | Add support for accessibilityControls prop |
Not Started, Est. 1-2 weeks |
| accessibilityItemType (Office) | Add support for accessibilityItemType prop |
Completed |
| accessibilityLevel / aria-level (Office) | Add support for accessibilityLevel prop |
Completed. |
| accessibilityDescription / aria-description (Office) | Add support for accessibilityDescription prop |
Not Started, Est. 1-2 weeks |
| [tasklist] |
Tasks
- Add support for AccessibilityInfo Native Module
- Add support for accessibilityControls prop
- #14657
- https://github.com/microsoft/react-native-windows/issues/14578
- #14531
- #14550
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.