-
Notifications
You must be signed in to change notification settings - Fork 791
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
aria-description: Newish attribute is not supported #3121
Comments
Thanks for the issue. Last we checked |
OK you might have a point about it maybe not working everywhere. But was copying what is used here http://whatsock.com/Templates/Comboboxes/Native%20Inputs,%20Editable%20and%20Readonly/index.htm and it seems to work well. How would i use axe.configure in the chrome extension? |
In the chrome extension you'll have to be logged into your deqeue account and then you'll get the functionality to configure axe. Otherwise you'd have to use axe-core directly (the JS code) to be able to do it. |
You should use the |
The title attribute is used for the tooltip. Im sort of trying to use multiple labels/attached information |
My current thinking is that developers should add We use the axe-core Chrome Extension and Apple's VoiceOver, which does read the aria-description. Wondering if there could be some sort of support matrix or configuration within the extension similar to caniuse |
I agree @neaumusic - it does work and it does solve our use case. So why not validate against it. Its not incorrect its just newer |
The main problem is that since not all browsers / assistive technologies support <input type="password" aria-label="password" aria-description="Password requirements: at least 8 characters"/>
This means that using IE11 and Safari, you'd miss the critical information provided by the description. Best we can do is mark it as Needs Review. Right now it looks like it's marked as a violation, so let me see if we have enough support to turn it on with Needs Review. |
The ARIA working group hasn't even put |
Safari TP 153 supports |
@woody-li Thanks for letting us know. We'll add this to the 4.6 milestone. |
I wrote a proposal on how to address both this, and the aria-braille* props here: The gist is, yeah we should add them, but we'll need a rule that ensures these aren't used on element without a role or accessible name. |
Product: axe-core
Expectation:
Using axe jest plugin and and axe scanner in chrome we found out that using
aria-description
is reported as invalid. But it is in fact a newish valid property.https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Annotations#aria_annotations_features
facebook/react#21035
Actual:
"Invalid ARIA attribute name: aria-description" is reported
Motivation:
Would like to use this new attribute.
The text was updated successfully, but these errors were encountered: