-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
netlify-cms doesn't pass @netlify/plugin-a11y test #6061
Comments
Thanks for putting this together @jsjoeio! Do you mind adding this to #1333 so we can have a centralized place to handle accessibility related issues? The CMS is a community project, so it would be great to see some contributions around this. Also I think 8a14937fcc7167ae5a7960a692e8054c/packages/netlify-cms-ui-default/src/AuthenticationPage.js#L94 it is a good place to start |
Sure, I'll do that now!
Ah, for some reason, I assumed since it's under the |
Closing in favor of #1333 (comment) |
We (Netlify) have dedicated resources for it (I'm one of those resources, 👋) which are targeted to support contributions. |
Ah, I misunderstood. I thought you were a person from the community volunteering to run the project in your free time on behalf of Netlify 😅 Thanks for clarifying! Another question came to mind. How do we (the community) know what issues you (the maintainers) are prioritizing? I peeked in the milestones and projects but don't see those being used. Just curious in case I run into other issues. |
Hi @jsjoeio, any active work is done by external contributors, either by picking good first issues, or by looking at most upvoted issues. As maintainers we focus on reviewing PRs that come in and guiding people in resolving issues. |
Describe the bug
The "Login with Netlify" button does not have sufficient contrast.
To Reproduce
package = "@netlify/plugin-a11y"
tonelify.toml
Expected behavior
netlify-cms
should pass@netlify/plugin-a11y
test 😅Screenshots
Applicable Versions:
CMS configuration
N/A
Additional context
Possible duplicate of #1333
The text was updated successfully, but these errors were encountered: