You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This, coupled with (imho) the fact that links are very faint (is that the font, or my eyes?) on a white bg (whether that be a card or the page) seems to render links in a way that I dont think is optimal
I'm in agreement about the link rendering. I think it's a compound issue of mainly colour and weight.
The colour contrast is fairly low (and putting it on F6F6F6 will make it worse). Note that the same font and colour is used for breadcrumbs and is fairly legible, but it's a heavier weight.
We're currently using a "light" weight for our body rendering and so I think increasing to normal would be good.
Font-weight 300 ("light"):
Font-weight 400 ("normal"):
So I think a small change to normal font weight and maybe exploring some alternative colours would help.
Thanks @chrisarridge - that seems practical and reasonable
re: The colour contrast is fairly low (and putting it on F6F6F6 will make it worse).
It would be useful if we consider this too, with #37 (although I understand this bg color would not be for body text...)
Aside from the weight , should we expect that such links have a state when visited, unvisited, or active? That's quite standard stuff, designed to help people, I think?
As we implement the design system more, the lack of any active / hover-over design (if I perceive this correctly: https://iati.github.io/design-system/?path=/story/core-typography--links) is apparent
This, coupled with (imho) the fact that links are very faint (is that the font, or my eyes?) on a white bg (whether that be a card or the page) seems to render links in a way that I dont think is optimal
I understand that @notshi has also experienced and voiced this via working on IATI/D-Portal#660
Please can we take a look at this @robredpath @tillywoodfield ? cc/ @IsabelBirds @Bjwebb @chrisarridge
The text was updated successfully, but these errors were encountered: