Separately from my comments on #348, the styling makes the Getting Started page really hard to read for me. The thick colour bands are attractive as a marketing thing, or showing off individual features that aren't strongly connected, but I find them extremely disruptive when I'm trying to do a more careful read.
Additionally, there's no syntax highlighting on the code, which really hurts especially given that it's the first code I see coming through the site.
Seconded - I don't see any syntax highlighting in the other sections either, and I think that could help with readability.
I would like to help with this if there isn't somebody already working on it
Posting some samples here (please ignore the margin issues for now):
What do you think about the background/highlight ratio?
On the left is the original non highlight version, on the right is the new highlight version.





Oh that's hard. I guess the black background version has the best contrast (also mind WCAG), but it looks a little too strong compared to the red background. Could not you maybe try another syntax highlighting style (i.e. foreground/text color set)?
Or maybe let the light white background of the original be there…
Yeah, I think it is a good idea to keep the original background. I will try to find a better highlight to match the white background.
For now only this version passes the Accessibility Audit (using Chrome Lighthouse). What do you think?
I tried to keep the original white background but I couldn't match a highlight colour which passes the Audit.

The best/most-likely-to-work thing here is going to be a white background, possibly with the Tomorrow theme. We're using white throughout the site, so it shouldn't look weird, and Tomorrow is the current theme used for API docs is either Tomorrow or something very close to it.
I have found a light theme which passes the audit: https://github.com/ericwbailey/a11y-syntax-highlighting
Thoughts?

Looks good, IMHO. :smile:
Awesome ! I will prepare a PR then.
With the risk of affecting the general theme, I think that all <code> blocks should be moved to the new theme. This way the accessibility support will be improved on the whole website.
An example of plain text with and without the theme:

Here's another idea: Give <code> and <pre> a black, transparent background:

This works very well with the design of the website. However, a dark theme might not look as good in the white sections. I have a few ideas for this:
filter: invert(1) hue-rotate(180deg); this, however, is not supported in IEAs someone who is red-green color blind the a11y-syntax-highlighting theme is really hard on my eyes when combined with the background in these examples, the difference to @Aloso's version is night and day.
@Aloso @sondr3 some great feedback ! Thank you !
@Aloso
- Use a different, light theme for white sections
Right now only the a11y themes seem to be passing the accessibility audit. I couldn't find other themes which performed the same. I don't know exactly how I can mix and match or find another compatible syntax theme.
@sondr3 would the dark theme be more suitable?

I like the dark one better but am normally a bigger fan of light background. It looks fine in the README, I think you should just be careful not to combine the light theme with a red background.
moving the discussion tot the PR #606
This has now been implemented and deployed to rust-lang.org
Most helpful comment
Here's another idea: Give
<code>and<pre>a black, transparent background:This works very well with the design of the website. However, a dark theme might not look as good in the white sections. I have a few ideas for this:
filter: invert(1) hue-rotate(180deg); this, however, is not supported in IE