-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Accessibility md-select aria-owns #7023
Comments
It does make sense to clear the attribute when the panel is hidden, however it looks like it causes a regression in the user experience. Previously NVDA would read out something like "{{option label}}, selected" when selecting, but it doesn't do it anymore if the attribute is cleared. Also looking at the documentation, it seems like pointing to unexisting elements isn't disallowed explicitly. |
Hmm yes reading the spec theres no specific mention of not allowing it. But if you read this part it implies it.
It says "one or more elements IN the document by ID. I'm ok with leaving it if thats what you think though. Let me know what you think, I'll create a PR if you think we should implement |
Removes the select's `aria-owns` attribute when the options aren't in the DOM, in order to avoid pointing non-existing elements. Fixes angular#7023.
Removes the select's `aria-owns` attribute when the options aren't in the DOM, in order to avoid pointing non-existing elements. Fixes angular#7023.
Removes the select's `aria-owns` attribute when the options aren't in the DOM, in order to avoid pointing non-existing elements. Fixes #7023.
…#9091) Removes the select's `aria-owns` attribute when the options aren't in the DOM, in order to avoid pointing non-existing elements. Fixes angular#7023.
…#9091) Removes the select's `aria-owns` attribute when the options aren't in the DOM, in order to avoid pointing non-existing elements. Fixes angular#7023.
Removes the select's `aria-owns` attribute when the options aren't in the DOM, in order to avoid pointing non-existing elements. Fixes #7023.
Removes the select's `aria-owns` attribute when the options aren't in the DOM, in order to avoid pointing non-existing elements. Fixes #7023.
This causes issues with axe-core when testing for aria roles and required children (listbox requires options). If the aria-owns tag is removed when the listbox is closed, the test fails even though the tags are added when the listbox is opened. |
This is also an issue when using the Chrome accessibility tools |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug:
aria-owns in the DOM even though the elements it points to are not
What is the expected behavior?
aria-owns should not point to elements not in the DOM, if the elements are not in the DOM then aria-owns should be removed as well
What is the current behavior?
aria-owns shows up in the DOM when those elements are not in the DOM
What are the steps to reproduce?
http://embed.plnkr.co/cLXRzvn2uWQ5y5YmiU8L/
inspect select, notice non-empty
aria-owns
What is the use-case or motivation for changing an existing behavior?
Currently throws accessibility issues
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
"@angular/material": "2.0.0-beta.8"
Is there anything else we should know?
The text was updated successfully, but these errors were encountered: