Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Extract mapping of RN Accessibility to UIA from DynamicAutomationPeer #3111

Closed
SavoySchuler opened this issue Sep 10, 2019 · 2 comments
Closed

Extract mapping of RN Accessibility to UIA from DynamicAutomationPeer #3111

SavoySchuler opened this issue Sep 10, 2019 · 2 comments
Labels
Area: Accessibility enhancement Needs WinUI 3 Indicates that feature can only be done in WinUI 3.0 or beyond. Recommend: Not Planned Recommend that issue should be given Not Planned milestone.
Projects
Accessibility API completion Accessibility: Ensure React Native on...
Milestone
Backlog

Comments

@SavoySchuler
Copy link
Member

SavoySchuler commented Sep 10, 2019 •
edited

Proposal: Extract mapping of RN Accessibility to UIA from DynamicAutomationPeer

Summary

Right now, DAP is the only control that reads out the RN accessibility properties we set and translates them into UIA properties. Views are the only things that use it. We would have to subclass all of our native controls to use DAP which is bad for perf.

Need to develop new story for custom automation peers for WinUI 3.0.
@ghost ghost added the Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) label Sep 10, 2019
@SavoySchuler SavoySchuler mentioned this issue Sep 10, 2019
Closed
@SavoySchuler SavoySchuler added this to the vNext Milestone 5 milestone Sep 10, 2019
@chrisglein chrisglein added Area: Accessibility and removed Needs: Triage 🔍 New issue that needs to be reviewed by the issue management team (label applied by bot) labels Sep 16, 2019
@chrisglein chrisglein mentioned this issue Nov 4, 2019
Closed
This was referenced Jan 11, 2020
Open
Closed
@chrisglein chrisglein removed the vnext label Mar 18, 2020
@chrisglein chrisglein modified the milestones: 0.63, Backlog Jul 13, 2020
@AgneLukoseviciute AgneLukoseviciute added the Needs WinUI 3 Indicates that feature can only be done in WinUI 3.0 or beyond. label Jul 13, 2021
@chrisglein
Copy link
Member

I believe this is the WinUI improvement that this is waiting on: microsoft/microsoft-ui-xaml#1349

@chrisglein chrisglein added the Recommend: Not Planned Recommend that issue should be given Not Planned milestone. label Aug 30, 2023
@chrisglein
Copy link
Member

Not something we plan to address on the Paper renderer as we move towards Fabric.
Fabric will not use XAML for the fundamentals of accessibility here, so this isn't applicable.

@chrisglein chrisglein closed this as not planned Won't fix, can't repro, duplicate, stale Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area: Accessibility enhancement Needs WinUI 3 Indicates that feature can only be done in WinUI 3.0 or beyond. Recommend: Not Planned Recommend that issue should be given Not Planned milestone.
Projects
No open projects
Accessibility API completion
  
To Do
Accessibility: Ensure React Native on...
  
Awaiting triage
Milestone
Backlog
Development

No branches or pull requests
3 participants
@SavoySchuler @chrisglein @AgneLukoseviciute