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

UI: Extremely poor contrast #420

Open
avivace opened this issue Aug 17, 2022 · 4 comments
Open

UI: Extremely poor contrast #420

avivace opened this issue Aug 17, 2022 · 4 comments

Comments

@avivace
Copy link

avivace commented Aug 17, 2022

The current color palette (e.g. the white text on bright pink gradient background) exhibits an extremely low score of color contrast

image

See a tester: https://coolors.co/contrast-checker/fffefe-ff8aa1

We should try to make the website more accessible and readable by choosing more sensible color combinations.. see: https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines

Other examples of combinations with very poor contrast (score ~2/10):

image

image

@avivace avivace changed the title Extremely poor contrast UI: Extremely poor contrast Aug 17, 2022
@ThiefMaster
Copy link
Member

Are there any CSS media queries indicating the client wants high contrast? The last time I checked there was only a Edge-only one which we of course don't want to use. Otherwise that'd be ideal, because:

  • The footer text is meant to be inconspicuous so I'd say the "poor" contrast is intentional...
  • For the second one, using black text there looks worse IMHO

A11y is important, but should it make the UI look worse (or make "clutter" more visible) for others by doing so? I'd say not if it can be avoided!

@ThiefMaster
Copy link
Member

Oh, there's actually this one: https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-contrast

Maybe we could switch to higher contrast colors using that query...

@avivace
Copy link
Author

avivace commented Nov 2, 2022

Are there any CSS media queries indicating the client wants high contrast? The last time I checked there was only a Edge-only one which we of course don't want to use. Otherwise that'd be ideal, because:

* The footer text is meant to be inconspicuous so I'd say the "poor" contrast is intentional...

* For the second one, using black text there looks worse IMHO

A11y is important, but should it make the UI look worse (or make "clutter" more visible) for others by doing so? I'd say not if it can be avoided!

@ThiefMaster Sorry for my super delayed replies... The idea here is not to provide an "high contrast" mode (which can be useful and I agree too, as separate issue), but at least to reach acceptable values of contrast in the standard theme.

The W3C’s Web Accessibility Initiative provides a standard, which in the last version WCAG 2.1 has 4.5:1 as contrast in the "Success Criterion 1.4.3 Contrast".

Just for reference, for an actual "High Contrast" accessibility (which could be a theme triggered with the query you mentioned) the values are 7:1 for normal text and 4.5:1 for large one.

Newdle is currently getting less than 2.13:1 in various UI elements, including the footer and the header text (Login):

image

and less than 2.06:1 in the flashy-bright pink text over white (or the inverse). For large text the required ratio is 3:1.

I'm happy to try and iterate on some theme changes (while trying to keep the current "accents"), what are your opinions here?

@ThiefMaster
Copy link
Member

I'm happy to try and iterate on some theme changes (while trying to keep the current "accents"), what are your opinions here?

Sure, that sounds good!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants