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

revisit accessibilityRole=button to button mapping #1944

Conversation

intergalacticspacehighway
Copy link
Contributor

@intergalacticspacehighway intergalacticspacehighway commented Mar 17, 2021

Issue link

  • Tested example and updated test cases.
  • Verified reset styles, tabIndex, and disabled props.

@jerrywithaz
Copy link

@necolas @louis-burrows if the merge conflicts in this get fixed, would you all accept this pr? It would great if buttons were actually rendered instead of div's

@s77rt
Copy link
Contributor

s77rt commented Jan 11, 2023

This may not work as you'd expect, in our case we had <div>s rendered inside <button> which is semantically incorrect.

@necolas necolas closed this in e8a0cbc Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
has: pr Subject of a pull request project:react-native-web Issue associated with react-native-web
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants