adjust brightness threshold

[LitoMore]

![](https://img.shields.io/badge/Construct%203-00FFDA?logo=construct3)
![](https://img.shields.io/badge/Construct%203-123-00FFDA?logo=construct3)

The current threshold does not look good for some colors. The brightness value of #00FFDA is 0.68. I adjusted the threshold value to 0.65 for better visuals.

I didn't change the threshold values in logos.js because they are different. We can consider refactoring more code for logos in a separate PR.

[github-actions]

	Messages
📖	✨ Thanks for your contribution to Shields, @LitoMore!

Generated by 🚫 dangerJS against 30a3355

[github-actions]

🚀 Updated review app: https://pr-10796-badges-shields.fly.dev

[chris48s]

This isn't a yes or a no to this, but for context..

I think one of the reasons we picked the value 0.69 was that it left all of the standard palette named colours with white text.

Going to 0.65 pushes yellow over to black text, so all the named standard palette colours still get white text, except for yellow which goes to

[LitoMore]

I just checked the brightness of yellow is 0.68. The yellow one is fine since it's not that dark for black (#333) text; it still has good visual accessibility. What do you think?

Here is a glance of some colors:

The Airbrake has a similar color to the yellow one, and their brightness is the same.

[github-actions]

🚀 Updated review app: https://pr-10796-badges-shields.fly.dev

[chris48s]

I think if we're going to change the brightness threshold down to 0.65, I'd prefer to also darken the standard yellow to #d2a816 so all the standard palette colours get the same text colour.

[LitoMore]

There are still some colors that do not look that good, for example the Alamy. We can consider implementing the WCAG relative luminance. The related npm package can be found at https://npmjs.com/get-relative-luminance in case you want to try it out.

The below is luminance < 0.4 ? '#fff' : '#333':

It looks more accurate for measuring brightness.

What do you think?