Infrastructure: Fix native accessibility-state projection gaps on macOS and Win32
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- react-native, typescript
- Domain
- accessibility, mobile-dev, testing
Research direction
Start with the Button and TabList native-state cases in button.stories.tsx and tablist.stories.tsx, then review the merged focus plan and PR #4314 evidence. Reproduce the AX/UIA tree attributes on supported macOS Fabric and Win32 Paper runtimes before identifying the owning component or renderer. Done means native state and updates match the public contract, with truthful driver normalization, passing native assertions, a Win32 Input regression, and updated evidence; link any upstream blocker.
Written by the indexing model from the issue text.
Description
Goal
Resolve the native accessibility-state projection gaps documented by the delivered assertion/focus work, rather than treating behavior tests as native state conformance. Parent: #4275. Bug follow-up to #4255 and PR #4314.
Observed state - 2026-10-01
Current story callbacks explicitly skip two macOS native-state assertions:
- Button disabled state: the source records that RNmacOS 0.81.9 Fabric does not project
accessibilityState.disabledto AXEnabled. - TabList selected/disabled state: the source records missing AXSelected/AXEnabled projection.
The merged focus plan separately records Win32 TextInput announcing UIA IsEnabled=true when configured noneditable, nonfocusable, and accessibility-disabled.
These are native observation gaps, distinct from the verified focus exclusion, callback/selection ownership, and activation guards. This audit verified the retained skip/source evidence; it did not requalify those observations against a newer native runtime.
Reproduction
On the current supported native runtimes, inspect the real AX/UIA tree for the Button/TabList focus fixtures and disabled Input fixture, then compare enabled/selected state before and after prop/state changes. Record resolved fork versions, native tree attributes, helper identity, and actual application behavior.
Use the isolated Button and TabList native-state WDIO cases; their current macOS skip text is evidence to replace, not permission to fake the expected attributes in JavaScript.
Acceptance criteria
- Reproduce or disprove each documented gap on current macOS Fabric/Win32 Paper, with explicit native attribute and runtime evidence.
- Identify the owning component/renderer/upstream transport and implement or consume the correct native fix; preserve the intended distinction between editability, focusability, and disabled semantics.
- Native AXEnabled/AXSelected/UIA state reflects the declared public contract, including updates and selected-to-unselected transitions.
- Driver normalization remains truthful: unsupported native state is explicit, never synthesized from component-owned status text or defaulted to
false. - Remove the two macOS skips only after their real native assertions pass, and add an enabled-state regression for the affected Win32 Input contract.
- Physical activation, UIA Toggle/SelectionItem.Select, AX custom-action dispatch, and screen-reader behavior remain separately identified; state reads do not claim those actions were qualified.
- Update the focus/accessibility evidence and relevant tests/docs/changesets. If an upstream fix is required, link its issue/change and keep the blocked coverage explicit.
Evidence
- Button native disabled-state case
- TabList native selected/disabled-state case
- Executed evidence and remaining renderer limits
- Coordinate #4343/#4349 and #4214, without closing native-state coverage using React prop tests.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 30
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from microsoft/fluentui-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/fluentui-react-native#4174 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/fluentui-react-native#4343 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/fluentui-react-native#4344 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/fluentui-react-native#4345 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/fluentui-react-native#4347 ·
Maintainers usually reply within 1 day
All issues in microsoft/fluentui-react-native
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
solana-foundation/solana-com#2245 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
`document.cookie` with `max-age=0` does not delete the cookiePossibly taken @BartInTheField claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
capricorn86/happy-dom#2460 ·
Maintainers usually reply within 2 days