-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
Bug: Improve lighthouse accessibility score. #87
Comments
I think the focus for this issue should be improving the accessibility score. If updating the links does not improve the score, we should avoid it. I am updating the title to reflect this. |
@EmmaDawsonDev, I think you can share some great insights on this. |
Definitely happy to take a look and do an accessibility audit. I'd prioritise fixing the links/buttons over raising the lighthouse score as that's something critical for keyboard users to access the site and not something lighthouse can pick up. But I'm sure there's a lot of small tweaks that can make a big difference |
.take |
Thanks for taking this on! If you have not already, join the conversation in our Discord |
Describe the bug
This was reported here.
Looks like there are few places where we are doing
Button
orLink
is rendering a<div href/>
. Opening this issue for tracking reasons.I have not yet triaged this myself, but we will want to make sure this site passes all accessibility tests now that it is live. This was an oversight on my part.
Steps to reproduce
Run the lighthouse on the site and report issues here. Depending on scope, we can open separate issues for fix in one PR.
Affected services
opensauced.pizza
Platforms
No response
Browsers
No response
Environment
No response
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: