Documentation pages not colorblind friendly

[C-Compton]

Is your feature request related to a problem? Please describe.
This is not a major issue, but it is something that is often overlooked in UX design.

I was reading through documentation on Tribuo when I noticed an issue regarding the color palette of hyperlinks and keywords. I'm colorblind (red/green), and they (links and keywords) appear to me as the same or very similar colors. Because of this, I was attempting to click on keywords for more information only to find that they were not links.

Describe alternatives you've considered

There are a couple of possible solutions. Hyperlinks could have some visual indicator such as being underlined. Fonts of keywords or links (or both) could be chosen so that they are immediately identifiable as being different. Lastly, the color palettes chosen for them could be made more distinct. An option could even be created for visitors of the page to enable a colorblind friendly palette so as not to upset the UX design of the site.

[Craigacp]

Ok, that's definitely something we should fix. Do you have recommendations for syntax highlighting colour schemes which work better for people who are colourblind? I think the only presence of green in our docs is in the code snippets and in the jupyter notebook exported tutorials, however the links & class names are in very similar shades of red and I'm not sure if that is also a problem. We should be able to easily fix the code snippets & red shades in the docs. The jupyter notebook syntax highlighting might be harder as we use their standard exporter and I'm not sure what control it provides over that.

The non-colour modifications such as underlining & fonts should be fairly easy, we'll have a look at a few options.

[C-Compton]

The similar shades of red were the issue I was trying to point out specifically.

There are different types of color blindness so I can't say that I can recommend a single color scheme that would work for everyone outside of using very high contrasting colors, which may effect your UX design, but also won't be a cure-all. A typical cure-all solution is to try and pick the best possible color palette and have some visual, non-color related indicator that they're different, such as different fonts or underlined links.

There are many references out there that talk about picking colorblind friendly palette.
Here are a couple I found with a quick search. There may be better references than these with a deeper search.

https://www.tableau.com/about/blog/examining-data-viz-rules-dont-use-red-green-together
https://davidmathlogic.com/colorblind/#%23D81B60-%231E88E5-%23FFC107-%23004D40

[Craigacp]

Ok thanks for the information. I think currently every link underlines when you mouse-over it (and the ones in the exported tutorial notebooks are always underlined), but that's obviously not so useful at a glance. It would be better if we consistently linked the class names to the javadoc as then they would all be links all the time, but I agree the colours would still need fixing to differentiate keywords and plain links.

We'll take a look at the colour palette and find something with a bit more diversity.

[Craigacp]

We're modifying the stylesheet on the website (oracle/tribuo-site#10) to make code tags bolded and links always underlined. The colour palette hasn't changed much, but if it's still tricky to differentiate things then we can move to a more diverse one. We did a few checks using tooling which simulates red/green colourblindness and the formatting changes seemed sufficient to make the different elements distinct, but let us know if it's not and we'll sort it.

[jhalexand]

Due to my not paying enough attention, those changes only went live this morning, rather than on Friday. But they are live now.