Website Accessibility a Legal Issue?
geekwithsoul asks: "Target is being sued because its website is not usable by the sight-impaired. While this story from the San Francisco Chronicle is from February, I've seen surprising little coverage of it in either mainstream or tech-focused media. Is the threat of legal action the only really effective way to get companies to create accessible (and thus standard-compliant) websites?"
"From the article:
'Advocates for the blind said the lawsuit is a shot across the bow for retailers, newspapers and others who have Web sites the blind cannot use. They chose Target because of its popularity and because of a large number of complaints by blind patrons.'Considering how much accessibility and standards support is available in modern web browsers (well, except for that one we all know), and a rising probability of legal exposure for sites not meeting these needs, is there really any excuse for online retailers and others to not make their websites accessible to all?"
In a world where executives are liable for actions that adversely affect the bottom line it certainly is required. Accesiblity for the blind likely costs more than it generates in revenue.
A major problem in the accessibility of the World Wide Web lately is CAPTCHA systems that distinguish sighted humans on the one hand from bots and blind humans on the other. For instance, Slashdot itself uses a CAPTCHA. Has anybody had success in getting a Slashdot account created through the e-mail method specified in the Slashdot CAPTCHA's alt text?
Don't forget that too many websites are driven by marketoids whose world revolves around bullshit. Bullshit being the absence of substance, it is clear that those bullshitter will try to hide their absence of content behind smokescreens made out of Javascript and flash.
And marketoids consider themselves artists, and there are no people more willing to shove useless crap down people's throats than artists.
It's that simple. They are under no legal obligation to do so. If you read the article, this isn't specificly about Target, this group is trying to make some broader point and is using the legal system to do so and they picked Target because of it's popularity. There are better ways to go about this than a nusaince lawsuit.
Sometimes, it's just not possible at all. My boss, for example, asks - rather, demands - that our organization's website be accessible to them in Dreamweaver. The problem is this: My pages are WAI A compliant and written in XHTML 1.0 Strict, XHTML 1.1, and CSS 2.1. The moment they hit "save" with Dreamweaver, it rewrites half the damn code in the page, changing indentations, switching out tags, and often changing things that weren't really any of its concern in the first place, adding CSS classes with names like "L1" instead of "bluebox" and inserting p tags everywhere. I'm left with a Microsoft-as-Borg kind of choice: assimilate and use Dreamweaver, or be defeated.
I try to create standards compliant, accessible websites, but the boss is worried about any emergencies that might pop up and require their immediate attention. Without being able to pull away from programs that change the pages around and aren't really aware of standards, I may not be able to do it at all.
(Side note: if anyone knows how to force the 'Reaver to leave my code alone, could you reply, please?)
ACs are modded -6. I don't read you, I don't mod you, I don't see you. Don't like it? Don't be a coward.
Hate to say it, but all of this politically correct stuff gets into freedom of association problems:
Considering how much accessibility and standards support is available in modern web browsers (well, except for that one we all know), and a rising probability of legal exposure for sites not meeting these needs, is there really any excuse for online retailers and others to not make their websites accessible to all?"
How about "We reserve the right not to do business with those we choose not to do business with without explaination?" This is about a lot more than just website accessibility- it speaks to (but probably won't come up) the constitutionality of the ADA itself.
SJW: a person who perceives an injustice, and while correcting it, commits a greater injustice.
How do you really convert a website for the visually impared? every time a picture is replaced, then its gonna make the site 1000 words longer (conservative estimate). I always do my best to include proper tags and the like, but i don't see how, for example, a graphic design company could apprioriately convey a subtle use of colour in an alt tag? or even if it would have any value.
And where does it end? do all bilboards have to be in braile?
What about a site which contains questionable material? should whitehouse.com come with proper descriptions?
--AlexC
Just because I dont agree with climate change doesnt make me a troll
The best way to ensure accessibility is to simply use XHTML 1.0 Strict and CSS. Too often these are seen as overly-complicated technologies, but how hard is it to close a tag once you open it, and why doesn't the ability to describe visual styling in one central location instead of thousands of files seem like a hassle instead of a blessing? Get O'Reilly's HTML & XHTML: The Definitive Guide and just see how much sense the elegant order and semantic meaningfulness of XHTML makes over prior markup solutions. Once you have a site up in XHTML 1.0 Strict, just make sure it validates with the W3C validator, and chances are, it'll already comply with Section 508.
UK and Australia have a much smaller sense of humor about non-accessible websites. Here, the only organizations with a legal obligation are state and federal ones (I know, I design websites for one).
To stay accessible, you need to ditch table-based HTML filled with JavaScript widgets and unnecessary Flash navigation. Consequently you need to explore CSS, and guess what hamstrings adoption of CSS's more advanced features?
The other issue is the crap-awful screen reader market. JAWS ignores code designed to separate out screen readers from visual browsers, Apple's technology works only with Safari, and none of these companies have been sued for not doing their job either.
"Made up/misattributed quote that makes me look smart. I am on
You have sources? /."
Not that I don't believe you, I just need places to cite other than "that guy on
Unfortunately, there's a lot of ignorance to fight. The average PHB assumes that creating a website that the blind can use is an arduous task, but this is not the case. If you build your website correctly the first time around, you essentially get accessibility for free.
If, on the other hand, your website was built by the average clueless Dreamweaver jockey, then you'll probably have to spend money retrofitting your website. But that's the clueless web developer's fault for doing it wrong in the first place. Sadly, it's in their best interests to tell the PHBs how hard it is, and the PHB's aren't qualified to know when they are being told a pack of lies.
It's only in unusual circumstances that accessibility is difficult when you include it as a requirement from the start of the project. However, typical managers go on what they've been told, and what they are told leads them to avoid accessibility unless they really need to address it. Lawsuits are a good way of getting them to address it.
Don't assume that accessibility and standards-compliance are the same thing. They are not. You can create accessible sites that don't conform to the specifications, and you can create inaccessible sites that do conform to the standards.
It's also worth pointing out that avoiding being sued isn't the sole reason to make your website accessible. It can often improve various semi-related features of your website, such as search engine rankings and usability. According to PAS 78, the accessibility guidelines published by the UK's Disability Rights Commission, Tesco and Legal & General got great returns on their investments into accessible websites.
There's more information about that last bit on Bruce Lawson's weblog. Highlight:
Bogtha Bogtha Bogtha
Smithsonian sued because they won't let blind people touch the paintings.
I Am My Own Worst Enemy
Does this mean that Dmitri Sklyarov did a favour for adobe?
Am I open minded towards open source, or closed minded towards closed source?
Ok, what kind of technology is out there for the visually-impaired to browse the web? I'm from a very rural southern town, and I've never heard of such a thing. What can Target do to remedy this?
Earn a % of cash back from Newegg, Tiger Direct, Walmart.com, and more: http://www.mrrebates.com?refid=458505
Why are they suing Target (other than the fact that Target has the cash)? Shouldn't they be suing the screen reader companies who make such poor products that they are unable to do a passable job on complex websites? This seems like a problem that could very easily be solved by one perfect piece of screen reading software. I guess the issue is always money....if there was a huge market for screen readers, i'm sure IBM would have big R&D dollars pushing the technology. But as it is, crap readers suprisingly produce crap results. altimage
I disagree. I know for a fact that government websites are covered under the ADA, and I suspect that if the website provides a service, like, say, on-line shopping, then it would be required to provide accomedations, as well. And, honestly, it's not like they are asking for anything unreasonable.
And while we're at it, I think you're wrong about the courts, too. The legal system is often critical for proving points. A lot of disabilities don't get accomedated until the courts rule one way or the other on it. Plus, I can think of a couple times (e.g. Brown vs Board of Education) where the lawsuits were instrumental in enforcing civil rights.
This isn't some guy suing McDonalds for not putting "HOT!" on his coffee. These are people with real disabilities who just want equal access that is (in my opinion) provided to them under law.
Wouldn't it just be common sense?
This is kind of like sueing The greatful dead for not providing deaf people access?
The web is textual.
For those of us that use alternative browsers (because IE don't run natively on Linux, of course), can we sue companies whose sites dont show properly or are unusable in them?
In Ontario (Canada), it's legally required that web sites for government agencies, and government funded organizations follow the W3C's Accessibility Guidelines according to the Ontarians with Disibilities Act. If you're making a website for anyone in Ontario who gets funded in whole or in part by the government, and you don't follow those guidelines, you can face massive fines.
You make it sound as though accessibility for the blind is a bad thing.
Consider what websites or programs need to do in order to be usable by a blind person. First of all, they can't have clutter. They need to obey standards. (eg. W3C, for websites) They need to have a good, well-designed user interface, in general.
Notice how all of those things have very positive results for regular users, too? Blind people probably see websites much as a regular user would see them through a text-only browser like lynx. If there are problems parsing the website, that could lead to other major problems in comprehending it.
Accessibility is a good thing for all users. If a blind person can easily use a website, a person who can see can also use it easily. There are too many cluttered, difficult-to-use websites around. Accessibility is an important goal.
And after I post it, I find that they moved the link... the Disabilities Act is actually at http://www.cou.on.ca/content/objects/DisabilitiesA ctGuidelines.pdf. They want the people to make their sites accessible, but the government sites about those requirements are full of out-dated, broken links. Figures.
Just as when you get a grant from the NIH or NIA, you have to make sure it's accessible, if you want to do work, and sell commercial products over the Internets, especially Wood, you need to make sure it's ADA-compliant.
... um, sorry, don't know many places that don't have similar rules in the First World.
Heck, that's why the Library four blocks from my house built a twisty ramp in the single lot Park next door that occupied half the space - so people in wheelchairs could use the park.
Which means they had to get rid of all the grass on the hill.
If you don't like it, move to
-- Tigger warning: This post may contain tiggers! --
I stand by my statement; the ADA does not apply to websites and videogames. Government agencies are different, as all of their services must be accessable, which makes it their responsibility only by proxy. There is absolutely nothing in the ADA about electronic access as it would apply here. I was involved in a battle over video game accessability, and the ADA does not cover electronic accessability in any way, shape, or form when it comes to things like this. For instance, someone who only has the use of one hand cannot sue Sony, Microsoft, and Nintendo because it is impossible to use one of their controllers without the use of both hands, therefore blocking you from using their product. It's the same here, and the simple fact is the ADA doesn't apply.
Exactly. It's the charge of the companies that make the devices to access, not the websites themselves. To further your analogy, this is like some company selling you a hearing aid, you take it to a Greatful Dead concert, but you still can't make out the words clearly...so you sue the band instead of the people who made the poorly performing product.
I shall paraphrase the question:
Hey guys, I noticed that most people can't design or implement for shit. Do we all agree? Don't other people suck? Shouldn't the answer to this be evident?
Designing things with standards in mind is a better idea than not doing so. Any Web Developer worth the capitals (and I'm not talkin about your grandma and her website, or that high school kid that someone paid $50 to do their mom & pop store website, or anything done with Front Page or Macromedia) knows that standards-based is the way to go. The culture of ineptitude around the web is what is really holding us back from having a fully accessible virtual world for everybo...
Waitaminnit, I got sucked in and started complaining about the web! What an insidious Ask Slashdot!
The only substantive change that will come out of this lawsuit is going to be to the lawyers' wallets. The lawyers will get a whole bunch richer, Target will get a tiny bit poorer, and the blind will still have to have people read the web to them.
This sig, aah-ah, is comin' like a ghost-sig...
In a country that has braille on drive-up ATMs, I can't say I'm surprised. Can I now sue crutchfield because the catalog I get in the mail isn't available in braille (as far as I can tell from the website)?
While I find using flash unnecessary, I certainly don't want to see using flash or any similar tool made illegal in some instances. Legislating the web in that fashion can be dangerous, and what's next? Can you get sued for missing an alt tag?
If sites had to be standards compliant, MS better get rolling on IE. Most browsers can't pass an ACID2, but there's been countless times where I've had to hack around IE quirks to get a page looking right.
To further your analogy, this is like some company selling you a hearing aid, you take it to a Greatful Dead concert, but you still can't make out the words clearly...so you sue the band instead of the people who made the poorly performing product.
:-)
No no no, you don't understand.
This is America. You sue the band for making you need the hearing aid in the first place AND sue the hearing aid company for a poorly performing product. If you're good, you also sue the venue and the band's promoter. If you're real good, sue the city who gave them a permit to perform in the first place! After all, their loud music damages hearing (see case #1 for the precident) and thus is a known dangerous product.
Learning HOW to think is more important than learning WHAT to think.
...then we can surely do what it takes to make them work for people,
/. article, developers just need to start
who happen to need a bit of accommodation.
As suggested in a recent
communicating with Folks with Disabilities (FWD's, a.k.a. PWD's)
It's just that easy. And... from experience... I can tell you:
It can really make you appreciate what you take for granted, ie,
finding out how life can be without sight or the ability to walk.
Mind-expanding... a bit like emerging from one of those "gotta
crawl on your belly" caves, on a spelunking trip...
Both are better than drugs, I'd suggest...
I roommate of mine a few years back was working for a major bureaucracy in the public transportation sector (please forgive my being coy. Normally I'd just blurt out the name, but in this case it's not my story.) She built a web page highlighting the specific work she was doing that was part of the larger corporate website. On her own initiative, she made her site compliant to the standards that blind computer users needed. Instead of being thanked for her efforts, she was ordered by her superiors to take down her page. They feared that her compliance would highlight the non-accessibility of the rest of the web site of the organization, and they were covering their asses.
San Francisco Photographers
Yes, but there are programs that read websites aloud, allowing blind people to access them. So it's more like banning deaf people from a Greatful Dead concert, even if they have hearing aids that would allow them to enjoy the show.
It is not hard to write webpages that can be read by these programs. Web standards were specifically designed to allow for it, so all you have to do is write standards compliant XHTML, which you should be doing anyways. It falls upon the creators of the web site to ensure that their page is at least usable by these sorts of programs. This is not hard or complicated, people.
"The other issue is the crap-awful screen reader market. JAWS ignores code designed to separate out screen readers from visual browsers, Apple's technology works only with Safari, and none of these companies have been sued for not doing their job either."
And yet FOSS is found lacking. Looks like you all may want to remove that splinter from your eyes before criticizing the plank in others.*
*No FOSS JAWS even.
SOCOG was successfully sued by the Australian Human Rights and Equal Opportunities Commission (on behalf of a blind complainant). There was coverage in Slashdot. The ruling can be read here.
In my experience (working for a large Australian telco) this has left other businesses wary, but not entirely proactive in addressing accessibility issues. I think (and hope) more successful suits are the only way to get companies to be good citizens (website accessibility-wise). I do know that all Government sites address accessibility seriously, thanks to mandates and directives from the top.
My experience is that web sites end up inaccessible because the people who create them simply don't think about the problem. As the developer on my team who actually thinks about such things, I have to remind other people why we can't have information only available coded with red vs green images in a table, why we shouldn't use JavaScript for navigational links unless we need to, why we shouldn't have organization structure only available as a big GIF org chart, and so on.
A multi-million dollar judgement against Target would get attention, and ensure that more web developers paid attention.
GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
Stupid question, but how does not being able to walk change your ability to use the internet?
I did some quick research (read:Google search) and found this quote from a DoJ letter, circa 1996:
More recently, the DoJ filed this brief which asserts the ADA covers even buisinesses that soley exist online. Websites, particuliarly websites offering goods and services, should offer accessibility options, and it's not unreasonable to ask for them. It's not like there aren't websites out there to help you out.
So, even though videogames are not covered (an assertion I agree with), websites most certainly are.
Suing != Asking the court for money. Suing == Asking the court for something that is rightfully yours, such as basic civil rights (or, in some cases, money).
It doesn't seem likely that Target is being sued for damages. More likely, they are being sued to comply with the law. So the end result would be that the courts force Target to change their website.
XHTML and CSS have nothing to do with accessibility. HTML specifies that IMG tags must have an ALT tag -- but that doesn't mean that it's an accurate replacement for the ALT tag -- lots of people used to use them for tooltips. There's nothing in the HTML specifications against having your site being a giant blinking image -- there are in 508.
... specifically for web developers, the WCAG.
I recommend against using XHTML -- too many problems w/ Internet Explorer (and even Safari will render some things slightly off what you're used to, even when it's complaint XHTML)
The best place for accessibility guidelines is W3C's WAI
Build it, and they will come^Hplain.
I know a blind guy going into computer science who thinks any blind person who doesn't have a friend who will get em past a CAPTCHA doesn't belong on said website.
Unless the blind person lives alone and the site needs a CAPTCHA for every transaction. For instance, as of the beginning of 2006, Blogger required this for every post. Some sort of landmark case of the form American Foundation for the Blind v. (some major site) might have repercussions in the field of spam prevention.
Looking at the captcha right now, it doesn't look that hard to defeat to me.
True, there is PWNtcha, but one who relies on PWNtcha might get sued under the DMCA for circumventing the CAPTCHA.
It seems to me that if it's a graphic element with no need for an alt attribute it should be fine to leave the alt attribute off and save a few bytes of download. Is there a logical reason behind this?
Yes. Requiring the alt attribute encourages web developers to think before they leave out the alt attribute. And even for spacers and other graphic elements where you have thought about it and decided that a lack of text should replace the image, once you use gzip compression, a tag that uses <img alt="" src= isn't significantly bigger than one that uses <img src=.
Use standards compliant XHTML and CSS.
I agree about the use of standards, but "the nice thing about standards is that there are so many to choose from" (Andrew S. Tanenbaum). What is the advantage of XHTML 1.0 over HTML 4.01 or HTML 5.0 if you have customers who use Microsoft Internet Explorer 6.0 SP2 or earlier? XHTML 1.0 served as text/html is treated as tag soup, and XHTML 1.0 served as application/xhtml+xml to IE is a parse tree.
My point is really that the internet is a multimedia info source
No. The Internet is a network, and accessibility is serious business. Gopher and World Wide Web are an information source period. They need not use multimedia.
The best way to ensure accessibility is to simply use XHTML 1.0 Strict and CSS.
Given IE's inability to display documents sent as application/xhtml+xml, what is the advantage of XHTML 1.0 over HTML 4.01? And given the mistaken deprecation of the value attribute of the li element in HTML 4.01 (and the subsequent removal from Strict), what is the advantage of Strict over Transitional if you abstain from all deprecated elements and attributes with the exception of li value?
make sure it validates with the W3C validator, and chances are, it'll already comply with Section 508.
Any page that uses a visual CAPTCHA with alt="security image; blind user access prohibited" will conform to XHTML but not the WAI guidelines. And if all images must have a reasonable replacement in the alt attribute, you can't do a visual CAPTCHA, so how do you distinguish between blind human beings and spambots?
Target is a private company
What is NYSE:TGT, then? Target is not privately held.
why yes...follow the case, and when the blind guy wins, which he will, it's a slam dunk despite the illogical naysayers on this thread, throw the news in your bosses face and tell them he will get sued and lose if he keeps using dreamweaver that creates illegal code, which is what it will be if you are selling stuff in a US based website and it isn't accessible. If it makes inacccesible, it is bad. Stockholders won't like that "bad" stuff.
In the meantime, just knock out some blank templates (using your own good code) for them, tell them all they have to do is fill in the blanks in an "emergency" then.
she made her site compliant to the standards that blind computer users needed. Instead of being thanked for her efforts, she was ordered by her superiors to take down her page. They feared that her compliance would highlight the non-accessibility of the rest of the web site of the organization
The penalties for crimes are different depending on whether the crime was committed knowingly or not.
Therefore, your friend's website, while being done in best intentions brought into focus the fact that the rest of that company's web site *MIGHT NOT* be compliant (and should be).
I'm guessing that courts would look at the issue of people knowingly keeping a website inaccessible different than someone accused of having an inaccessible website.
In the United States, ADA website compliance means Section 508.
n /moveitdmz_generalinformation_federalregs_ada.htm
See:
http://www.access-board.gov/sec508/guide/
How do I know? Before the U.S. Post Office looked at our web-based secure file transfer and messaging product (MOVEit DMZ), they required us to pass this requirement.
You can see a short version of our "yes, we comply" statement online here:
https://support.standardnetworks.com/moveit/doc/e
Among the interesting bits: to meet full compliance we added an option that allows our administrators to add a "skip repetative navigation" link to the top of the page; this specifically allows audio readers to skip directly to the unique content on the page.
Target engages in interstate commerce and thus can be regulated by the Congress.
See the e-mail method available on this very site's user registration system for a CAPTCHA method that respects accessiblity.
See the e-mail method available on this very site's user registration system for a CAPTCHA method that respects accessiblity.
What prevents a bot from using this method or just from DOSsing the address with a spam flood?
Alright, you sign up for a new account with that system, and see how long it takes for someone to get back to you. If ever.
Tluin natha Linux xxizzuss uriu olt bwael mon'tun.
Rights got to be balanced. It is what makes real life so difficult. How do you balance the right of target to make its website the way they like it with some peoples rights to live a normal live despite a physical disability.
My freedom to form a club of people I like is offset by the rights of other people to join clubs they wish. So whites only golf clubs are a no-no.
It all depends what you consider more important. The freedom of people with bad eye sight or the freedom of website designers.
Off course as a programmer I personnally think that designers should have NO rights but that is just me.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
I pretty much doubt the blind would even care very much about the kind of pictures that speak a thousand words. I at least haven't seen lenghty and detailed descriptions of famous works of art in museums so blind people can enjoy them.
So your image gallery of ehm nature shots is save. No need to describe each nudy shot in details in the alt attribute.
However for most of the images on a normal site this does not apply. Take for instance images serving as navigation links. The oh so cool animatited letter leading to the email link could easily have an alt value of "email" and then it would be clear to all.
Same with menu links. Just have the alt say what ever you have rendered in the image.
Yes there are going to be difficulties like what the hell do you do with product images. How exactly do you describe a piece of clothing. Or worse a motherboard. Well, you don't need to. If your normal product description is good enough then all you need to put in the alt value is that this is an image of the product.
Sure many motherboard descriptions are so fucking poor you need to study the image to learn what exactly is on the board but is that a problem just for the blind?
Frankly it isn't so hard to make a website that the blind can use. This complaint is about navigation only. Not that target doesn't properly describe its furniture.
The only problem in doing proper navigation is that you first got to shoot the managers and the designers. Management just seems to insist on using pointless flash for essential site elements.
The designers should be shot just because. Why the fuck does CSS not have constants forcing me to do the search and replace for minute color changes because designers don't understand complex functions like that?
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
Any private organization should be able to whatever they want, or not do whatever they want, as far as accessibility to customers go. As for government, they have to be accessible to all and by all.
Choosing the lesser of two evils is a choice for evil.
I bet most lawyer's websites are not designed for the blind either...
And by doing so, the blind are not able to access legal info/services at the same level as those with sight... Thus, they are being disadvantaged because the lawyer was negligent in hiring a good webmaster. It would be like a law office without a wheelchair ramp for the handicapped....
The ADA applies to physical premises only. Web sites which need to comply with section 508 are government sites *only*. No law mandates that private entities, such as Target, needs to provide blind people with access to its web sites. This lawsuit is a civil suit - the same type which would be filed if someone didn't want Target using the color red in its logo.
"Covered entities that use the Internet for communications regarding their programs, goods, or services must be prepared to offer those communications through accessible means as well."
... accessible means such as a storefront with wheelchair ramps, or a telephone number to call, or an address to write to for a printed catalog. Just because they have to offer "accessible means" doesn't mean they have to magically allow everyone to use the same venue.
> should whitehouse.com come with proper descriptions?
/me ducks
I think you might have made a typo here! Shouldn't that be whitehouse.gov??
People Without Arms Sue Entire Computer Industry.
To err is human. To forgive is not company policy.
Wouldn't it just be common sense?
This is kind of like sueing The greatful dead for not providing deaf people access?
The web is textual.
That's really a dumb thing to say. The web consists of mark-up and content. That content is typically text-encoded, because that's the way we humans like to do things. But, that should have no bearing on how someone wants to browse that content.
This thread reflects really poorly on the Slashdot community. You folks can't lift your techno-Libertarian heads out of your cubicles long enough to see that the Web is too valuable a resource to be restricted to the sighted.
I refuse to justify this absurd behavior with an actual response beyond, "Get a fucking life you sue-happy son of a bitch."
-=[ Who Is John Galt? ]=-
I wonder how this case is going to deal with existing ruling by U.S. District Judge Patricia Seitz in the 2002 case Access Now and Robert Gumson v. Southwest Airlines Co. (pdf) stating that Southwest did not have to redesign its website to be more accessible to the blind.
The 11 Circuit Court of Appeals upheld the ruling in 2004.
I have to say that I'm very much against these rulings. Making websites accessible to the blind is trivial if the website is designed properly in the first place. It's only difficult if you mash the damn thing up with bad flash and poorly coded javascript.
I never said code for a specific browser -- I said don't use XHTML. I'm a supporter of valid code, and the Any Browser Campaign, but I don't currently support XHTML, because there is better cross platform support for HTML4 than there is for XHTML 1, because XHTML is not directly compatable with HTML
You can write pages that will degrade gracefully under both XHTML and HTML -- but you can't write a valid XHTML page that will parse cleanly in IE, XHTML is not backwards compatable with HTML, due to the need of an XML declaration before the HTML doctype.
To get XHTML to work in browsers that don't directly support XHTML, you'll have to serve it as text/html, which can then cause problems which correctly support XHTML. more details at wikipedia.
You get better overall support in browsers by coding to HTML4.01 -- there are few advantages to the user to using XHTML 1.0 (it's easier on the browser code, that's about it). That's not true with XHTML 2, which offers better alternative text for images and objects, as well as more easily arranged sections and dramatically updated Web Forms, but I have no idea when we'll get browser support for it. (hell, we don't even have good support for CSS2, much less CSS3 in most browsers)
Build it, and they will come^Hplain.
CAPTCHA is easy to get through - just have a friend read it to you
So for a web site that requires a CAPTCHA for every transaction, how do you plan to compensate the friend for his or her time and travel expenses to and from your residence?
[I claim that] accessible means such as a storefront with wheelchair ramps, or a telephone number to call, or an address to write to for a printed catalog [are an acceptable substitute for an inaccessible web site.]
What about some click-and-mortar businesses that offer Internet-only products or Internet-only discounts?
If I'm producing markup which validates to a recognised, non-obsolete standard
For one thing, http://www.target.com/ most emphatically does not validate as HTML, with an error count well into three figures. For another, if your markup follows the recognized, non-obsolete Web Content Accessibility Guidelines published by the Web Accessibility Initiative division of W3C, then conforming aural browsers will have little or no problem with it. (Unfortunately, unlike the HTML 4 specification, WCAG cannot be completely boiled down to a DTD for use in automatic validation. A human being has to evaluate pages for conformance.)
is on documents on government servers, because as with tfa the visually impaired might be using screen readers that will only really work if the page is standards compliant (for the most part) - its called ADA standards or something like that I think, and for as much as I care, it means that I couldnt make my site in kick ass Flash (its a college workstudy thing for a city/community sponsored organization for getting old people to socialize and its on the college server, which is government supported, and we are governed by a very picky board which you never know what they will get picky about, just might be accessablity)
If you can get around it, it's not "effective", now is it?
Your interpretation of "effective" does not match the interpretation of "effective" seen in Universal v. Reimerdes and other landmark DMCA cases. Judges have interpreted "effective" merely as "having the effect".
According to the accessibility czar here, JAWS is largely a chunk of Visual BASIC which wedges itself into Windows' screen display routines, about as elegant as Sidekick using TSR keyboard interrupts to coexist with DOS. Its authors are praying Microsoft will buy them out and rewrite the code into the OS for them. If Windows was open enough as an architecture to make writing a general purpose screen reader easy, JAWS would handle non-Microsoft apps just as well as MS apps, and it pretty clearly doesn't.
You want FOSS accessibility for browsers? FireVOX extension.
https://webspace.utexas.edu/chencl1/clc-4-tts/
I've run it successfully on Windows XP, OS X Tiger, and Debian Sarge. Under Windows you can even choose which speech engine to use; the one bundled with FireVOX or the one already installed on your PC.
"Made up/misattributed quote that makes me look smart. I am on
If you sincerely believe that the World Wide Web is and should be a multimedia information source, then what do you suggest that blind people use as an alternative to your conception of the World Wide Web? Not all countries' laws allow outright discrimination against blind people.
if anyone knows how to force the 'Reaver to leave my code alone, could you reply, please?
I hate those damn Reavers, too. Upgraded Zerglings are quite effective in getting rid of them, as are Dark Templar if they don't have an Observer in the area.
Perhaps I've been playing too much Starcraft.
For all those who might be interested, check out how the Target website does on some common standards and accessibility tools:
And of course, check out the source code . . . it's pretty horrendous.
I'd say you're still wrong. From www.ada.gov
Poorly designed websites can create unnecessary barriers for people with disabilities, just as poorly designed buildings prevent some from entering. Designers may not realize how simple features built into a web page will assist someone who, for instance, cannot see a computer monitor or use a mouse.
One example is a photo with no text description - as some blind people can't make out the photo but can read the text. That is no fault of the software company, but of the website designer.
So, the lawyers get paid... how?
This sig, aah-ah, is comin' like a ghost-sig...
Actually, Section 508 of the ADA DOES apply to websites.
Back in college, I worked as a student assistant for the Occupational Therapy dept. at the University at Buffalo. I had to make sure the department's site was handicapped accessible. We used Bobby, which was free back then. It helped catch a lot of easy-to-fix errors. I see that the product is still around, but now they charge for it:
b ilitytesting/default.aspx
http://www.watchfire.com/products/desktop/accessi
--The Programming goddess from Gorflaz
I've yet to hear of a reasonably sized and priced hearing aid that works just as excellently as does the natural ear. Granted, I don't know fully the differences between natural and aid-assisted hearing, as I was born with a need for the later. If you're not implying that you think hearing aids are available that are perfect, ignore me.