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
font-family:
Some custom fonts don't render so well on a PC. Also, browsers use poorer rendering engines than Adobe products. Therefore you should do a test in HTML and view in IE and FF on PC. Squint and see if it looks alright.
The text was updated successfully, but these errors were encountered:
Note that we also want to limit the download size of every font we’re using. So normal, italic, bold and bold italic might be all we need. I think we don’t need to use thin (≤300) font weights.
WCAG 2.0 has no provision on less than normal text, so one could argue we can’t use it. (I don’t.) Or we need to have a larger color contrast to meet WCAG 2.0.
Font with less weight will be ok on higher resolution (Retina) displays but can be harder to read on non-retina screens. We might be able to send the thinner font only to retina screens.
Best is to come up with a prototype and just test.
Some custom fonts don't render so well on a PC. Also, browsers use poorer rendering engines than Adobe products. Therefore you should do a test in HTML and view in IE and FF on PC. Squint and see if it looks alright.
The text was updated successfully, but these errors were encountered: