Re:An easy to follow design course for programmers
by eranation on Friday January 11, 2013 @07:39PM
(#5045924)
There is a site dedicated to the topic actually:
http://contrastrebellion.com/
I think there is a difference between "looks good aesthetically" and "readable" and sometimes making it more readable doesn't overlap with pure artistic choices, so sometimes it's the best designers that fall into this trap.
Edit: see previous discussion on this here: http://news.ycombinator.com/item?id=2807047
Re:An easy to follow design course for programmers
by Cyranix on Friday January 11, 2013 @07:52PM
(#5045968)
I might cut them a bit more slack if the image to the CTA wasn't for "Typography Crash Course"!
Thanks for the reminder on Constrast Rebellion.
Re:An easy to follow design course for programmers
by hdra on Saturday January 12, 2013 @02:03AM
(#5046815)
I am not sure which part you are referring to, but here i see mostly black text on white background.
but that is the landing page, the email itself is indeed hard to read (all the problems you mentioned).. I waited several seconds after opening the email because I thought the CSS haven't finished rendering.
Re:An easy to follow design course for programmers
by hkmurakami on Saturday January 12, 2013 @02:07AM
(#5046821)
I see black text on white background as well, but since multiple people are mentioning this problem, I'm suspecting that the landing page is being A/B tested as we speak.
Re:An easy to follow design course for programmers
by Cyranix on Saturday January 12, 2013 @02:43AM
(#5046889)
UPDATE: Either the maintainers are responding to feedback or, as speculated downthread, some A/B testing is going on. If the latter is the case, pick B, for the love of all that is holy!
Re:An easy to follow design course for programmers
by wells-riley on Saturday January 12, 2013 @02:59AM
(#5046919)
Responding to feedback because I love you and you were right.
EDIT: Pull up your favorite color contrast analyzer and run this site through it. Using AccessColor, the results are ~4% failure and ~75% warning for WCAG 1.0 standards.