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.

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

[MSFT ask] Add Support for onAccessibilityAction to Return Accessibility Data #843

Open
chiaramooney opened this issue Dec 11, 2024 · 0 comments

Comments

@chiaramooney
Copy link

chiaramooney commented Dec 11, 2024

Introduction

Add Support for onAccessibilityAction to Return Accessibility Data. NEEDED FOR WINDOWS

Details

The onAccessibilityAction prop helps developers to be able to add correct accessibility to custom components. The current onAccessibilityAction/accessibility action API pair allows developers to define actions like "select" and then created a callback function to be called when a native accessibility 'select' event occurs. Currently the callback functions are not able to have parameters. This is okay for actions like Select and Toggle where the user does not need data back from accessibility, but for accessibility actions like setting a numerical value, there is a functionality gap. If the developer wanted to track a SetValue accessibility event, they would know the event occurred but have no way of knowing what value the user set.

Could we add the feature to the onAccessibilityAction prop where it can return accessibility event data, so input values/other data passed into assistive technology could be passed to the JS?

Discussion points

  1. Discuss proposal to adjust onAccessibilityAction prop to allow callback functions to have a parameter which will capture event data from the accessbilityEvent where applicable.
@chiaramooney chiaramooney changed the title Add Support for onAccessibilityAction to Return Accessibility Data [MSFT ask] Add Support for onAccessibilityAction to Return Accessibility Data Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant