171–180 of 250 posts
Earlier quoted context omitted.
Hard to read downvoted comments is a feature not a usability bug. Down voted comments are supposed to be hard for everyone to read.
I don't think a screen reader would pick up the down-voted comments as different from other comments. So, it's still broken from an accessibility standpoint.
Earlier quoted context omitted.
I've seen multiple bicyclists almost hit by in-controls cars because they couldn't ride safely on the sidewalks without those ramps. (Yes, riding on sidewalks is technically illegal. There are many places where it's much much safer and there are no pedestrians to bother.)
Just take a lane already, and be where you're supposed to be.
It's far, far safer to be on the sidewalk where I live.
Speaking as a colour-blind person (protanopia) I welcome this kind of thoughts with open arms. There's actually not much you have to do in order to make a website at least readable if you just have some basic concepts in mind when designing. The latest fad with soft pink and grey is really bad, almost unreadable for me. Luckily, I can usually just select the text and get blue/white contrast, which makes it more reada…
This makes it a marketing problem as well.
I find this font ridiculously hard to read. I clicked the back button after the first paragraph. It's also hard to take the author's opinion on web-design seriously when they make such decisions for their own site.
It's a personal blog, it's not comic sans, so how bad can it be?
I agree with the OP that the reason most developers don't build accessible sites is because they don't use the accessibility tools and hence have no understanding of how they actually work and the experience they provide for their users. Reading the List Apart article I linked to was rather eye-opening to me (no pun intended) because I didn't realize that I could just use a Chrome plugin or my iPhone's voice-over as a screen reader to actually experience it myself. I am now wishing I could go back and change a lot of html structure on sites I've built in the past to make it easier to navigate via screenreaders!
I have poor vision. This website uses a herd-to-read font and disables pinch-to-zoom (an essential feature) on my iPad.
Earlier quoted context omitted.
Just take a lane already, and be where you're supposed to be.
No way. Drivers where I live are terrible. Three friends of mine were hit while road cycling in a span of 4 months. It's far, far safer to be on the sidewalk where I live.
Earlier quoted context omitted.
Isn't the cost essentially zero if you just install them when you're doing other work?
Depends on the price of the rubber bits or the moulds for the concrete ones.
Earlier quoted context omitted.
Claudius is being sarcastic. http://kb.mozillazine.org/index.php?title=UserContent.css
Sarcastic, yes, but mostly relating to Opera 12.x’s UserCSS features; I didn’t actually know about userContent.css. Thanks for the pointer, although it seems to be impossible to only apply it to certain sites?
I have poor vision. This website uses a herd-to-read font and disables pinch-to-zoom (an essential feature) on my iPad.
Not just that but it's abusing statistics. StatCounter attempts to measure browsing volume, not people using a particular browser. Net Applications attempts to measure people using a browser, so IE9's reported share is three times higher, around 9%. As an analogy, take the toothpaste market with only two players. Lets say 30% of people use Colgate and 70% use Crest. But for some reason the first group uses more tooth…
Suppose that there was no technology to help blind people use computers. Then blind people would have 0% of browsing, but they're not 0% of the population -- should we create technology to help them even though they do no browsing? (Yes.)