Open
Bug 1375290
Opened 8 years ago
Updated 1 year ago
Additional handling of aria-errormessage in conjunction with missing aria-invalid is needed
Categories
(Core :: Disability Access APIs, enhancement, P3)
Core
Disability Access APIs
Tracking
()
NEW
People
(Reporter: jdiggs, Unassigned)
References
Details
(Spun off from bug 1374697)
Some issues:
1. Authors MUST use aria-invalid in conjunction with aria-errormessage, but we're not checking for the presence of a non-false value of aria-invalid.
2. As best as I can tell, there is no spec stating that failed user-agent validation of an input should be treated the same as or mapped to, aria-invalid="true". I've asked about that in https://github.com/w3c/html-aam/issues/47#issuecomment-310221640.
Plus Alex indicated in bug 1374697 that the commit history would be more readable if the ATK mapping and sanity checking were two separate bugs.
Comment 1•7 years ago
|
||
This is something we should triage and fix but isn't among our most urgent bugs.(Contributions welcome as always!)
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•