Infrastructure: Fix native accessibility-state projection gaps on macOS and Win32
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 30/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- react-native, typescript
- Domaine
- accessibility, mobile-dev, testing
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
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.
- Langage dominant
- TypeScript
- Étoiles
- 1.4k
- Forks
- 180
- Merge moyen
- 1 j 14 h
- PR mergées (30 j)
- 30
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de microsoft/fluentui-react-native
-
MenuList: FocusZone not wired for react-native-windows ('windows'), so menu items are Tab-only (no arrow-key roving focus)Peut-être pris @UditDewan l’a pris il y a 10 jours. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
microsoft/fluentui-react-native#4174 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 24/100
microsoft/fluentui-react-native#4384 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 32/100
microsoft/fluentui-react-native#4383 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 12/100
microsoft/fluentui-react-native#4380 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 18/100
microsoft/fluentui-react-native#4379 ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de microsoft/fluentui-react-native
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
cline/cline#15327 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
LogicLabs-OU/OpenArchiver#509 ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
bigcapitalhq/bigcapital#1545 · 1 commentaire ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 83/100
Les mainteneurs répondent en général sous 1 jour