I was developing a Liferay portal for a client which needed (in my idea) complete accessibility. I used my iPad to move in the page and was a big experience, most of my initial design was not tested over visual appearance but semantic accessibility.
If you own an iOS device do activate VoiceOver and try to surf YOUR applications (and more important, your WEB applications). Even better, let someone else do it for you.
You'll discover how hard and difficult can be to READ a page not designed to be read but scanned with eyes.
Please, do it. Blind people have the same right to access your content and features.
I recognize that you're posing a (presumably rhetorical) philosophical question, but it seems worth pointing out that there are certain contexts where accessibility is a matter of law.
If your content is intended for use or distribution by a US federal agency, or was created using federal dollars or as part of a federal contract, you are responsible for ensuring that it is compliant with section 508 of the Rehabilitation Act of 1973, which specifies that your content be accessible to individuals with disabilities.
Leaving aside for a moment the larger question of whether specific blind and/or deaf individuals consider their sight/hearing status to be a disability or not, section 508 is generally interpreted to mean that your content needs to be as accessible as you can make it. That means (among other things) working to make sure that screen readers and other such software are able to make full use of your site's functionality.
In my experience, the process of getting a project compliant with section 508 is generally very valuable- it makes you think a lot about how your content is organized, and rewards use of semantic markup. It can be frustrating at times, but the end result is definitely worth it for a wide range of reasons.
Here are a couple of places to get started learning about 508 issues:
I see what you're getting at, but I think you're being a bit douchey about it.
Of course blind people do not have a "right" to access his content. Neither does anyone else. There is no law anywhere that says "X person or group has an inalienable right to view Google". That doesn't mean we shouldn't be considerate of disabilities.
ADD: He says blind people have "the same right" and not "a right", the implication here being that they have "the same right" as any sighted person.
Not a reply to azelfrath, sorry. chadmalik, if by chance you see this, your posts have been getting auto-killed since the "Why vertical farms are a crock" discussion.
For those without showdead on, here's the comment, which I thought was worth reprinting:
"I'd like to add another way of thinking of it. Several years ago I was part of a group working on a project that was composed of people from various companies. One of the attendees was blind. It became clear VERY quickly that our blind friend was light years above everyone else technically and in terms of thinking about process. He'd sit there, listen to people go back and forth on this or that issue, then come in with an incredibly intelligent and appropriate solution, time after time. He was using an audio browser to go over the project materials when we weren't working. If you don't make your services accessible to the blind, YOU might be the one missing the benefit of this type of person's input."
So, you're being sarcastic, but aside from the fact that you're scorning blind people for crying out loud, there are laws that might well apply to you.
Do you do any work building government websites or sites that serve other large public services? Do you sell services to schools or universities? Do you run a site that people might be obligated to use for some reason (i.e., website for a utility)?
Think of it like this: "I know it's kind of a shitty thing to block disabled folks from my site -- but given that I'm an X (offering X, hosting X, etc.), is it ILLEGAL for Xs to discriminate against disabled people?"
Laws are progressively covering more ground as time goes on, so while I doubt there will ever be much enforcement for teensy hobby sites (like the guy at the side of the highway selling strawberries probably won't be building any handicapped ramps), it's pretty reasonable to expect gradually more requirements from all serious sites. In the UK (for example) the Equality Act 2010 gets a bit more explicit that all sites should at least makes reasonable efforts for accessibility:
http://www.shoosmiths.co.uk/news/3441.asp
(Caveat: I'm not an accessibility legal expert by any means, but have been doing a bit of reading on the subject over the past year, as I'm developing a site we intend to be fully accessible).
Probably my use of "right" in that context could be not correct.
I think it's our duty to be as inclusive as possible when talking about the target audience of our applications/content.
Even more if you're designing an infrastructure used by someone else (or more the one) to build their communication channels.
And talking about a specific law and legal rights for accessibility, here in Italy every public/governative web-site/application MUST meet the required standards for accessibility. Less or more a triple A (and more given the additional strictness of our local law).
If you own an iOS device do activate VoiceOver and try to surf YOUR applications (and more important, your WEB applications). Even better, let someone else do it for you.
You'll discover how hard and difficult can be to READ a page not designed to be read but scanned with eyes.
Please, do it. Blind people have the same right to access your content and features.