-
-
Notifications
You must be signed in to change notification settings - Fork 340
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
bugfix: fix a11y warning in Ratings component #1739
bugfix: fix a11y warning in Ratings component #1739
Conversation
🦋 Changeset detectedLatest commit: f5b63c9 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Before this fix, the following warning occurred: A11y: <svelte:element> with click handler must have an ARIA role This was an issue because the `on:click` binding was always applied, even when the element would be not interactive (a `span`).
97266a6
to
f5b63c9
Compare
@Gerschtli we have an open ticket regarding this: We announced this during the last release that we will be investigating each of these to determine how we wish to handle these (bottom of the page): But we typically like to keep these kind of sweeping changes uniform - so I'll consider your PR, but cannot promise we'll move forward with it if we decide to go another way. This is especially critical when it affects a11y. There are certain rules and considerations that need to be adhered when touching anything related to accessibility to ensure we get this right. Thanks for your patience in the meantime. Also make sure you read our contribution guidelines - we typically ask for folks to volunteer rather than surprise us with PRs. We've ran into several instances of duplicate effort in the past, and we're doing our best to try and avoid that: |
I searched for issues like that, must have slipped through.. No worries, I just saw the warning and it wasn't that complicated to fix. Take your time and feel free to close my PR, if you want to go another route :) Thank you for building and maintaining this awesome project! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Gerschtli Thanks for the PR! These changes are excellent and are exactly what I had planned to do anyway 😄.
It's not as DRY, but I think given the simplicity of the component this will suffice for now. Merging now and this will be a part of next week's release. Thanks for your contribution! |
Description
Before this fix, the following warning occurred:
This was an issue because the
on:click
binding was always applied, even when the element would be not interactive (aspan
).Checklist
Please read and apply all contribution requirements.
dev
branch (NEVERmaster
)docs/
,feat/
,chore/
,bugfix/
pnpm check
pnpm format
pnpm test