Skip to content
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

[Bug] Trademark Policy uses term "contrast ratio" without defining it #1217

Open
1 task
SamB opened this issue Aug 8, 2021 · 2 comments
Open
1 task

[Bug] Trademark Policy uses term "contrast ratio" without defining it #1217

SamB opened this issue Aug 8, 2021 · 2 comments
Assignees
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work
Projects

Comments

@SamB
Copy link

SamB commented Aug 8, 2021

Description

The Trademark Policy says:

You are not authorized to use any modified versions of our trademarks, except that you may use a different color for the CC logo and its background so long as the two colors chosen have a contrast ratio of at least 3:1.

But what ratio do you mean? For web use, do we …

  1. … just add up the 8-bit RGB components of each color and then divide?
  2. … realize that the amount of illumination corresponding to those RGB components isn't actually linear, but something much closer to sRGB, so convert to CIEXYZ color space?
  3. … remember that human perception isn't linear, so convert to e.g. CIELAB color space instead?

… and what about viewing conditions?

I suppose we could try to use the definition at https://www.w3.org/TR/WCAG21/#dfn-contrast-ratio, but see w3c/wcag#695 for why that might not be the best plan.

And what about usage in print?

In conclusion: (╯°□°)╯︵ ┻━┻. It might be better to forget about defining things for now, and just say something like "but please choose colors with plenty of contrast".

Resolution

  • I would be interested in resolving this bug.
@SamB SamB added 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents labels Aug 8, 2021
@cc-open-source-bot cc-open-source-bot added this to Ready for Development in Active Sprint Aug 8, 2021
@cc-open-source-bot cc-open-source-bot removed this from Ready for Development in Active Sprint Aug 8, 2021
@cc-open-source-bot cc-open-source-bot added this to Pending Review in Backlog Aug 8, 2021
@TimidRobot TimidRobot moved this from Pending Review to Non-Engineering in Backlog Apr 25, 2022
@TimidRobot TimidRobot self-assigned this Apr 26, 2022
@Natchaphonwongplianphan

This comment was marked as spam.

@Natchaphonwongplianphan

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work
Projects
Backlog
  
Non-Engineering
Development

No branches or pull requests

4 participants
@SamB @TimidRobot @Natchaphonwongplianphan and others