-
Notifications
You must be signed in to change notification settings - Fork 44
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
Adding aria-describedby attribute to target? #37
Comments
I realize that ember-tooltips does this, but my first instinct is that we should not follow suite. I'm wary of adding an implicit side-effect that modifies something outside of our component. Seems like we should avoid touching things outside the Very open to discussion on this; I fully admit to not knowing too many details about aria support. |
Only an hour in and I've changed my mind on this. Seems like it is standard behavior across tooltip libs to modify the target. I think we should add |
@kybishop perhaps we should have two separate components for popover and tooltip, so we could exclude it by default? ember-tooltips has two components, so might not be terrible. Could also add classes by default then of |
@rwwagner90 that sounds reasonable. We could make a mixin that does basically everything, then have a few additional functionalities in the specific components. |
Just adding a bit more info, https://www.w3.org/TR/wai-aria-practices/#tooltip also mentions using |
I have a gameplan for this, will hopefully have a custom tooltip component in the next few days. |
Should the
aria-describedby
attribute beember-attacher
's responsibility to add to the target?The text was updated successfully, but these errors were encountered: