Demo: replaces brand colours with accessible alternatives #7
Conversation
This file contains 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.
DON'T MERGE THIS PR. This PR is to demonstrate how an engineer would change the brand colours on the blog, such as to replace them with alternative colours with adequate colour contrast. Changing the brand colours, however, is more than a technical problem, and should at a minimum involve the input of the Marketing team.
This PR is referenced by the Blog Accessibility Investigation's issues and recommendations doc. Since the time of writing, it may have been referenced in other documents. If you close this PR, those links may break. Otherwise, there's no reason why you couldn't close this PR if it's getting in the way.