-
Notifications
You must be signed in to change notification settings - Fork 403
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
Allow aria-invalid on any element? #252
Comments
Yes, I agree. The script element type check should be only when considering the element's |
How would you check if it supports I am happy to work on this! |
The part that checks what
Go for it! And thanks! Thanks a lot. |
@BurntCaramel Did you have a chance to work on it? If you are a bit busy now I can take it, I've just come up with a possible solution. |
🎉 This issue has been resolved in version 5.10.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Currently the
toBeValid
matcher whitelists what elements are allowed:jest-dom/src/to-be-invalid.js
Line 4 in 5c9e8e5
However, AFAIK the ARIA specification allows it on any element:
https://www.w3.org/TR/html-aria/#IDL-ValidityState
I propose removing the element tag check and allowing it on any element.
My specific issue is with a
ol
with roleradiogroup
that I am settingaria-invalid
on.The text was updated successfully, but these errors were encountered: