microsoft / microsoft/react-native-windows
Advanced Screen Reader Readability on Fabric
Open
Nobody has claimed this yet.
Area: Accessibility
Area: Fabric
enhancement
New Architecture
Workstream: Accessibility
- Dominant language
- C++
- Stars
- 17.3k
- Forks
- 1.2k
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 33
Description
Add support for additional react-native props that provide additional, richer information to ATs about the focused control in specific scenarios.
React Native Core Accessibility Props
| Task | Description | Status |
|---|---|---|
| accessibilityState | Add support for the accessibilityState prop on Fabric |
Completed |
| accessibilityActions | Add support for accessibiliyActions. |
Completed |
| accessibilityRole/role | Add support for accessibilityRole/role. |
Completed #11876 |
| accessibilityPosInSet [Windows Only] | Add support for accessibilityPosInSet prop. |
Completed |
| accessibilitySetSize [Windows Only] | Add support for accessibilitySetSize prop. |
Completed |
| accessibilityLabeledBy (Android-only in core) | Add support for accessibilityLabeledBy prop. |
|
| nativeId (for use with LabeledBy) | Add support for nativeId prop. |
|
| accessibilityHint | Add support for accessibilityHint prop. |
https://github.com/microsoft/react-native-windows/pull/12036 |
| accessibilityValue | Add support for accessibilityValue prop. |
Completed |
| accessibilityLiveRegion / aria-live | Add support for accessibilityLiveRegion/aria-live prop. |
#13596 |
| importantForAccessibility | Add support for importantForAccessibility |
Not Started, Est. 2+ weeks |
UIA Properties
Note there are many other UIA types captured in this list. We will grow the list as we learn which additional data types we need to support for our controls.
| Task | Description | Status |
|---|---|---|
| Name | UIA should have Name data for every component. |
https://github.com/microsoft/react-native-windows/issues/12030 (partial), https://github.com/microsoft/react-native-windows/pull/12186 |
| ControlType | UIA should have ControlType data for every component. |
https://github.com/microsoft/react-native-windows/pull/11876 |
| LocalizedControlType | UIA should have LocalizedControlType data for every component. |
Completed |
| IsKeyboardFocusable | UIA should have IsKeyboardFocusable data for every component. |
https://github.com/microsoft/react-native-windows/pull/11674 |
| BoundingRectangle | UIA should have BoundingRectangle data for every component. |
https://github.com/microsoft/react-native-windows/pull/11508 |
| AccessKey | UIA can have AccessKey for a component. |
|
| AcceleratorKey | UIA should have AcceleratorKey data for every component. |
|
| HelpText | UIA should have HelpText data for every component. |
https://github.com/microsoft/react-native-windows/pull/12186 |
| PositionInSet | UIA should have PositionInSet data for components that are a part of a set. Tracking issue for accessibilityPosInSet |
Completed |
| SizeOfSet | UIA should have SizeOfSet data for components that are a part of a set. Tracking issue for accessibilitySetSize |
Completed |
Tasks
- https://github.com/microsoft/react-native-windows/issues/13327
- https://github.com/microsoft/react-native-windows/issues/13316
- https://github.com/microsoft/react-native-windows/issues/12511
- https://github.com/microsoft/react-native-windows/issues/12512
- https://github.com/microsoft/react-native-windows/issues/12513
- https://github.com/microsoft/react-native-windows/issues/12514
- #12036
- https://github.com/microsoft/react-native-windows/issues/12510
- https://github.com/microsoft/react-native-windows/issues/12515
- Name
- https://github.com/microsoft/react-native-windows/pull/11508 BoundingRectangle
- https://github.com/microsoft/react-native-windows/issues/13348
- https://github.com/microsoft/react-native-windows/issues/12518
- HelpText
- Add support for LocalizedControlType
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.
Research direction
This issue is a tracking list for React Native Core accessibility props and UIA properties on Fabric, with no specific file or test named. Start by reviewing the unchecked tasks linked as issues 12513, 12514, and 12518, plus the not-started importantForAccessibility item. Done requires implementing a defined accessibility property and updating its status here.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, react-native
- Domain
- accessibility
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100