Open ralfhandl opened 3 weeks ago
Just wanted to throw in some general comments.
@ralfhandl Amazing work using lighthouse and going through.
Agree that the bright green headlines are problematic. Your style guide is also problematic in the way it specs out colors. It is in CMYK - so the colors you are picking from don't even really match. I played with correct conversions here. https://codepen.io/stringtheory/pen/VwJYjWP I am glad to provide a couple of alternative colors that meet the current spec and also future-proof you to the new spec.
I went up the chain a bit with the Accessibility Spec people - since there is less of a definitive answer on the color formatting for syntax highlighting // and am awaiting to hear back.
For distinguishable links - a very common way to handle them is with an underline. You will have bold for other things in the spec so you don't want to add confusion.
I am swamped until late this week - but glad to go into more detail and help further then - if you don't mind waiting.
Your style guide is also problematic in the way it specs out colors. It is in CMYK - so the colors you are picking from don't even really match. I played with correct conversions here. https://codepen.io/stringtheory/pen/VwJYjWP
Thanks, I wondered how the Pantone colors 7737 C, 574 C, and 375 C mentioned in the OpenAPI Style Guide are correctly translated to hex colors.
Trying four different "Pantone to hex" converters on the web I ended up with three different sets of hex colors 😁. The two that agreed are slightly different from your conversion:
Pantone | Hex |
---|---|
7737 C | ![]() |
574 C | ![]() |
375 C | ![]() |
So which ones are correct? I don't want to create a user for accessing https://www.pantone.com/color-finder ☹️
Recommendation by @stringtheory
Findings
Additional findings (not strictly accessibility)
Current preview: https://ralfhandl.github.io/OpenAPI-Specification/oas/latest-a11y.html