-
Notifications
You must be signed in to change notification settings - Fork 9
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
option to exclude tools that only check contrast #110
Comments
Does filtering on Accessibility Checks not achieve this? |
Given the already high number of filters and the chance that we will be removing the 'Accessibility Checks' I am not inclined to put this in without a strong body of supporting evidence. |
It is necessary to use a color contrast analiser tool to evaluate the SC 1.4.11. |
Right. The point is if there are lots and lots of tools that only check contrast, it adds unnecessary complexity for people to wade through if they want a tool that checks everything.
Thanks for the idea. I don't see any reason to exclude tools that require the user to provide colors codes. |
Summary:
Rationale:
There are so any tools that only do contrast, that it degrades the user experience. A quick skim of the current list finds ~20+ tools that are only contrast checkers or simulators. And, we continue to get more -- another 5+ that we haven't added.
(We expect the new list be shorter, since several tools are not longer active. If most of the contrast tools re-submit theirs, we could end up with contrast tools being ~20% of the whole list.)
We're forcing users who want a more robust tool to read through all those contrast checkers. (And, similarly, someone wanting only a contrast checker to wade through other tools.)
#101 questions the list of what things check, and we might even decide to get rid of that. If we do, we still might want to have a contrast option.
side note: We don't want to use "color contrast" alone. From Easy Checks, Contrast ratio ("color contrast")
The text was updated successfully, but these errors were encountered: