-
Notifications
You must be signed in to change notification settings - Fork 124
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
Request for Clarification on aria-owns Usage in ARIA 1.2 Specification #2124
Comments
From a quick look,
I do not see any restriction for aria-owns in the html-aria spec. Could you point to a reference?
Do you happen to have a test that is exhibiting a problem? E.g., image and textbox roles require name-from-author. I don't immediately see how modifying the accessibility tree via aria-owns would matter here. |
The HTML Living Standard and ARIA in HTML do not specify restrictions on aria-owns for elements like img and input, which cannot have child elements. This omission leads to confusion among developers and auditors, which I have seen in conducting accessibility audits. The response from developers when this is pointed out is always "it does not say that in the spec". This is the reason I propose adding clarifications to the ARIA specifications. These should explicitly outline the use cases and limitations of aria-owns, especially for elements that cannot host children. Clear guidance will align development practices with accessibility standards. Let the ARIA documentation take the lead, just because it is not mentioned in other specifications and standards is not a reason not to address this gap.
The following Codepen example demonstrates that for input and role textbox the aria-owns is ignored in the accessibility tree when tested in both NVDA and JAWS in Chrome and Firefox. I included a valid use case example of an HTML list that is exposed in the accessibility tree. The accessibility tree is already providing the correct behaviour for aria-owns. It is the documentation that does not align to the behaviour.
JAWS output from the Codepen example The list is nested in HTML input and ARIA role textbox. This is not rendered in the accessibility tree.
However, the aria-owns is rendered in the accessibility tree as a nested list. list of 5 items Incorrect implementation of aria-owns, stemming from gaps in guidelines, negatively affects screen reader user experience. Research references
|
Thanks for the codepen example.
Personally, I feel like it isn't but I agree with you that the spec needs to clarify things. To explain: from my reading of the specs, I'd have expected the accessibility tree to make the lists children of the inputs - and thus largely ignored because a label is provided; the result would leave the actual lists fairly inaccessible. But user agents seem to agree on how they treat this situation: aria-owns appears to be ignored and the lists left where they are. I suspect the spec(s) should reflect this kind of agreement. |
related w3c/html-aria#385 |
Describe your concern
I would like to request clarification regarding the aria-owns property as described in the ARIA 1.2 Specification, specifically within the Characteristics table under the "Used in Roles" row, which states the value as "All elements of the base markup."
Upon reviewing the specification, I encountered two primary concerns:
Given these points, I seek clarification on the following:
Link to the version of the specification or documentation you were looking at at.
Does the issue exists in the editors draft (the editors draft is the most recent draft of the specification)?
The text was updated successfully, but these errors were encountered: