News for hackers. Stuff that matters.
Re:The FFmpeg/Libav situation by NotA20YearOld on Saturday June 30, 2012 @09:14PM (#4183410)
For me the link is an unreadable low contrast website. Come on folks; make your websites accessible.
Re:The FFmpeg/Libav situation by wtallis on Saturday June 30, 2012 @09:36PM (#4183479)
While it certainly isn't a full-contrast color scheme, if you're having trouble reading it, you probably have a messed up color profile or gamma setting. I'm no big fan of low-contrast color schemes, and I'm partially color-blind, but I had no trouble with that site.
Re:The FFmpeg/Libav situation by shelf on Sunday July 01, 2012 @07:03AM (#4184398)
I'm not sure what your definition of contrast is, sir. That was a fairly bright grey on a fairly dark grey. Returning to HN from this article was an unpleasant retinal shock.

Confusing a bright, backlit monitor with a piece of paper is some pretty nasty 1990s logic.

Re:The FFmpeg/Libav situation by caladri on Sunday July 01, 2012 @11:47AM (#4185077)
Note the use of the word "accessible" in the original post. This is not a synonym for "pretty" or some way of demanding a particular aesthetic style for its own sake. The reality is that some degree visual impairment is not at all uncommon and that difficulty with contrast can result from any number of conditions.

I'm not sure about the original poster's statement that that site isn't accessible. I haven't tried applying a stylesheet from my browser to it, and I don't use anything to enhance contrast of text in web pages, as my vision is not impaired in that way. There's an argument to be made, though, that modern websites use coloring, layers, and a bunch of other things to achieve layouts, looks and feels to the extent that if you want to see content as it is presented, or to even find it readable or usable at all, you'll have a hard time with applying styles using your browser.

Believing that just because the web can be used differently to black-type-on-white-paper in a wide variety of ways means that every way of using it differently is virtuous is pretty mid-2000s web 2.0 logic. Contrast is useful, and its proven track record for rendering text is no mark of antediluvian shame, of irrelevance or datedness.

Re:The FFmpeg/Libav situation by shelf on Tuesday July 03, 2012 @11:36AM (#4194505)
Would you call that low-contrast, though? My comment suggests that both colors are quite some distance apart, so despite the inversion, the contrast is quite reasonable. It just has the added bonus of, you know, not burning the crap out of my eyes.

You seem to have read something in my comment that wasn't there.

Re:The FFmpeg/Libav situation by Nick_C on Sunday July 01, 2012 @02:29AM (#4184019)
Same for me, but I do have my screen's brightness turned down so that white backgrounds don't glare.

FWIW, I discovered the Firefox plug-in Tranquility recently. It is sort of a light-weight Readability. Although it has far fewer tweaks available, it compensates by using much less resources. Readability was pretty much unusable on my low-spec laptop.

Re:The FFmpeg/Libav situation by aw3c2 on Sunday July 01, 2012 @06:16AM (#4184348)
Give Opera a try. It has an inbuilt "accessibility layout". Black text on light green background, big font, fixed width.
Re:The FFmpeg/Libav situation by Brajeshwar on Sunday July 01, 2012 @04:45AM (#4184242)
https://chrome.google.com/webstore/detail/ppelffpjgkifjfgnba...

iReader for Chrome is a good Option. I tend to read most articles through it. Other browsers have their alternatives.

Re:The FFmpeg/Libav situation by kyberias on Sunday July 01, 2012 @04:37AM (#4184234)
It seems your comment's contrast is getting lower by the minute. I wonder why... :)
Re:The FFmpeg/Libav situation by ux on Sunday July 01, 2012 @06:19AM (#4184355)
Feel free to use plugins like Stylish :)

Do you have any suggestion for the CSS?