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

Accessibility Issue: Elements must only use allowed ARIA attributes #193

Open
ccalvarez opened this issue Oct 14, 2021 · 6 comments
Open

Accessibility Issue: Elements must only use allowed ARIA attributes #193

ccalvarez opened this issue Oct 14, 2021 · 6 comments
Labels
bug Something isn't working enhancement New feature or request

Comments

@ccalvarez
Copy link

ccalvarez commented Oct 14, 2021 •
edited
Loading

Hi.

I am using the axe DevTools Web Accessibility Testing extension, and it reports this issue on the react dropdown select controls:

Elements must only use allowed ARIA attributes

More details about the issue: https://dequeuniversity.com/rules/axe/4.3/aria-allowed-attr?application=AxeChrome

You can scan the Examples page:

image
@ccalvarez ccalvarez changed the title a11y issue: Elements must only use allowed ARIA attributes Accessibility Issue: Elements must only use allowed ARIA attributes Oct 14, 2021
@sanusart sanusart added bug Something isn't working enhancement New feature or request labels Oct 14, 2021
@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale issue with no response or lack of info label Apr 16, 2022
@stale stale bot closed this as completed Apr 25, 2022
@sanusart sanusart reopened this Apr 25, 2022
@stale stale bot removed the stale Stale issue with no response or lack of info label Apr 25, 2022
@stale
Copy link

stale bot commented Jul 31, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale issue with no response or lack of info label Jul 31, 2022
@sanusart sanusart removed the stale Stale issue with no response or lack of info label Jul 31, 2022
@stale
Copy link

stale bot commented Oct 30, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Stale issue with no response or lack of info label Oct 30, 2022
@stale stale bot closed this as completed Nov 12, 2022
@sanusart sanusart removed the stale Stale issue with no response or lack of info label Nov 12, 2022
@sanusart sanusart reopened this Nov 12, 2022
@stale
Copy link

stale bot commented May 22, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@jeebon
Copy link

jeebon commented Oct 3, 2023

Any update regarding the issue described?

@sanusart
Copy link
Owner

sanusart commented Oct 3, 2023

Not ATM. But any PRs or further investigations are welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sanusart @ccalvarez @jeebon