[6.x] Improve Stricter WCAG 2.2 Mode #13565
Merged
+20
−15
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Problem
Previously, we had implemented a Stricter WCAG 2.2 Mode.
This was sort of a work in progress in an early alpha and lots of things have changed since then.
This meant that only some form control borders had higher contrast.
What this PR Does
This PR updates many border contrasts to ensure the mode works as intended.
Form control borders everywhere in the CP now have a higher contrast
How to Reproduce
cp/preferences/editand turn on Stricter WCAG 2.2 Mode