We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
role
Current Behavior
For Hibana only, <UnstyledLink role="button"/> does not successfully render to the DOM as <a role="button"/>.
<UnstyledLink role="button"/>
<a role="button"/>
Desired Behavior
I should be able to modify the role of a link while using Matchbox.
Suggested Solution
Pass on the value of the role prop to the rendered anchor tag.
Who does this impact? Who is this for?
This largely helps screen reader users when links open modals instead of navigating to new pages.
The text was updated successfully, but these errors were encountered:
Are you using a wrapper component by any chance? We pass through role but only if it (1) does not have a wrapper and (2) does not have an onClick.
onClick
See: https://github.com/SparkPost/matchbox/blob/main/packages/matchbox/src/components/UnstyledLink/UnstyledLink.js#L12
Sorry, something went wrong.
Resolves #540 - Pass through role to UnstyledLinks with wrappers or t…
3646391
…o links (#542) * Pass through role to UnstyledLinks with wrapper components * Pass through role to all UnstyledLinks * Fix a typo
jonambas
Successfully merging a pull request may close this issue.
🚀 Feature request
Current Behavior
For Hibana only,
<UnstyledLink role="button"/>
does not successfully render to the DOM as<a role="button"/>
.Desired Behavior
I should be able to modify the
role
of a link while using Matchbox.Suggested Solution
Pass on the value of the
role
prop to the rendered anchor tag.Who does this impact? Who is this for?
This largely helps screen reader users when links open modals instead of navigating to new pages.
The text was updated successfully, but these errors were encountered: