-
Notifications
You must be signed in to change notification settings - Fork 10.5k
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
Implement axe
accessibility suggestions
#2087
Labels
Comments
Hi! Could I try and take this on? |
Sure. To help you implement this, I'd recommend installing axe and running it locally. You can do the same steps we do in the axe workflow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I implemented support for axe accessibility tests in #2080. I decided by default to let this be run only manually, since fixing some of the issues is not straightforward. I ran it once on the main page (about page) of the template and also in the blog main page, and here are the issues.
For the about page:
For the blog main page:
The text was updated successfully, but these errors were encountered: