-
Notifications
You must be signed in to change notification settings - Fork 49
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
Should meter element allow all aria-* attributes allowed on meter role? #517
Comments
thanks @straker. this is a miss and should be similar to the progress role. i'll make a quick PR to fix this |
scottaohara
added a commit
that referenced
this issue
Apr 30, 2024
closes #517 adds missing allowance for any aria-* attributes applicable to the meter role.
scottaohara
added a commit
that referenced
this issue
Apr 30, 2024
* Correction: add missing allowance for aria-* on meter element closes #517 adds missing allowance for any aria-* attributes applicable to the meter role.
straker
added a commit
to dequelabs/axe-core
that referenced
this issue
May 1, 2024
… meter element (#4435) Turns out we didn't list the `meter` element's implicit role. Ref: w3c/html-aria#517 QA notes: verify a `meter` element allows non-global aria attributes from the [`meter` role](https://www.w3.org/TR/wai-aria-1.2/#meter).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the meter element is listed as only allowing global aria-* attributes, but does not allow any of the aria-* attributes allowed on the
meter
role (though does make note to not usearia-valuemax
oraria-valuemin
). Is this indeed correct or does the meter element allow using allowed aria-* attributes of themeter
role, such asaria-valuetext
?Other elements that are restricted to a single allowed role (but also not recommend to use that role), such as input[type=url], are documented as allowing aira-* attributes allowed on the implicit role with the text "any aria-* attributes applicable to the allowed role."
The text was updated successfully, but these errors were encountered: