Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: ergophobe
It is now 2009 ... in just 11 days, it will have been 10 years since the Web Content Accessibility Guidelines [w3.org] first became a W3C recommendation.
And where are we at today? What is the status of this tremendous effort?
Progress in review
On the upside, we have come a very long way from where we stood in 1999. CSS is now a commonly accepted (and used) standard for all websites. Even the WYSIWYG editors* have joined the "standards" bandwagon. We are no longer coding for X browsers. Rather, we are coding to a standard; one that actually most browsers (yes, even IE these days) adhere to.
But despite all this progress, we have overall not really progressed much. In certain areas, giant leaps forward have been made. But in other areas, we have taken equally large steps backwards.
Much still remains to be done
I recently sat in a meeting with supposed web "professionals" ... Some of the design aspects that were discussed were outright horrid from an accessibility and usability perspective. When I expressed my concern over where the discussion was heading, citing certain aspects of the WCAG, there was a big silence in the group ... Quietly, and confidently, awaiting feedback to my remarks, one person spoke up. In fact, he was exactly the person I expected to first say anything. Young, inexperienced, very much "new media" oriented, where the bells and whistles are more important than how stuff actually works.
"Where are you getting that stuff from?" he asked with clear scepticism in his voice.
When I mentioned "the Web Content Accessibility Guidelines", the room went even more silent, with a big "Who? What? Where?" look on everyone's face.
I cannot say I was directly surprised, as I have been in many of those meetings before.
"Why should we care?" "This does not apply to us." Or, the worst one of them all: "Those are not the types of customers we are seeking to attract."
This little story and the experience that goes along with it summarizes very well the current problem.
So very few truly understand what accessibility and usability is about!
Ignorance is not an excuse! Usability is for everyone!
A few highlights, in no particular order:
Again -- ignorance is no excuse!
Are there other common mistakes out there? What can we do, as designers/developers to provide a counter balance in favor of more awareness of accessibility and usability?
* Or -- perhaps more accurately -- WYSIWYG+, since you seem to get just a little more markup than you had initially bargained for.
[edited by: DrDoc at 4:56 pm (utc) on April 25, 2009]
How long is a last name
It's amazing how many ecommerce sites or search on social sites will reject a last name that is shorter than a three letters. Forget that the most common names in the entire world are, in fact, two-letters long. I once went through the Berkeley phone book and concluded that over 1% of all listings had two-character last names.
Numbers only for phone numbers and credit card numbers
My CC number is printed on my card with *spaces* and 0-9. The phone company lists my number with hyphens and parentheses. In other countries, . are often used in phone nums. Take any data, strip all non-numbers, then validate!
Don't worry, all users have color-calibrated monitors and eprfect color vision
Okay, maybe they don't. Maybe, just maybe, some monitors have different gamma, gamut, contrast, brightness, and maybe, just maybe some of your users are color-impaired (as in at least a few percent of the population). So take a screenshot and convert to grayscale. Is it readable? Because frankly, your green type on a red background, red type on a red background to me.
>>Please upgrade to IE4+
I have gotten these messages for IE7 - in other words, they test to see if I have IE 5 or 6. But, failing to accept my browser of choice, I switch to IE7, which fails their stupid test.
A quick check looks to me like w3c.org no longer has a validation tool specific to WCAG.
I'm looking for a tool a non-technical client can use without getting bogged down in other validation nit picking.