Popular Posts
-
MailShadowG is an application that will allow you to sync Outlook with Gmail. MailShadowG is a product of Cemaphore Systems , a California b... -
The Indian finance ministry has begun a public competition to select a design for the symbol of ...
-
I have used every one of these resources as a graphic designer and website developer and have hand picked all of these resources based on th...
-
For web designers and graphic designers, gradients provide almost unlimited options for creating the perfect look. This list is a collection...
-
Navigation menus have really important role in any website. For big sites full with a lot of pages and articles, drop down menus and tabs ar...
-
We live in a world surrounded by Times New Roman, Arial and Helvetica, typefaces so functional that they have long since become boring. It’s...
-
If you are like me then, you definitely enjoy a good advertisment and also spread the word about that product or service. Even if is about c...
-
It’s quite easy to get stuck in creativity blocks, but it’s damn hard to get out of them. Particularly if you are out of time and don’t want...
-
In today’s marketplace, every company needs an effective website. Of course, the purposes and needs of each company’s site will be unique, b...
-
BADGES Web 2.0 Badges - A set of free badges to download and use in your own designs. Fresh Badge - Quickly generate your own badge. adClu...
Helping others understand web accessibility
Friday, February 22, 2008
When I hold workshops for people who want to learn more about web standards and accessibility, I often notice that the attendants really have tried to improve their accessibility knowledge. But they get overwhelmed when they go to the official documentation from the W3C and try to understand it.
Mike Cherim brings this up in Making Web Accessibility Accessible, an article that is over a year old but still just as relevant. He notes that accessibility is harder to get into than it should be for several reasons, one of which being that the documentation (WCAG 1.0) is hard to understand. And it doesn’t look like things will get much easier when WCAG 2.0 is released and becomes the norm.
In addition to the documentation problem, Mike also mentions the unhelpful attitude held by some people who seem like they don’t want to help the less experienced, the misguided or the misinformed, and instead choose to criticise them. I see it too sometimes, and I have probably been guilty of doing that myself. But I really try to help where I can by sharing what I’ve learned about web accessibility so far. And I’m still learning, so I really appreciate when other people share their knowledge.
Over the years I’ve spent countless hours writing articles, responding to email and comments, and participating on discussion forums. No matter how much I would like to, there is no time for me to do more unless I quit my dayjob. And since my dayjob is how I pay the mortgage, well, that’s not very likely. Writing articles takes lots of time, for me anyway.
Going back to Mike’s article, he suggests a few things to think about when you talk about accessibility with other people who work in the fields of web design and development:
Be a translator: Learn the specs and translate them into English.
Be willing to give back: If somebody asks for your help, try to find time to respond.
Accessibility is happy: Give accessibility a smiling face.
Encourage don’t admonish: When somebody makes progress, acknowledge that instead of criticising what they do wrong.
Good suggestions, Mike. I will try to get better at each of them. For instance, I guess I could be a little less grumpy sometimes when I come across bad examples or implementations. But not always… ;-)
Mike Cherim brings this up in Making Web Accessibility Accessible, an article that is over a year old but still just as relevant. He notes that accessibility is harder to get into than it should be for several reasons, one of which being that the documentation (WCAG 1.0) is hard to understand. And it doesn’t look like things will get much easier when WCAG 2.0 is released and becomes the norm.
In addition to the documentation problem, Mike also mentions the unhelpful attitude held by some people who seem like they don’t want to help the less experienced, the misguided or the misinformed, and instead choose to criticise them. I see it too sometimes, and I have probably been guilty of doing that myself. But I really try to help where I can by sharing what I’ve learned about web accessibility so far. And I’m still learning, so I really appreciate when other people share their knowledge.
Over the years I’ve spent countless hours writing articles, responding to email and comments, and participating on discussion forums. No matter how much I would like to, there is no time for me to do more unless I quit my dayjob. And since my dayjob is how I pay the mortgage, well, that’s not very likely. Writing articles takes lots of time, for me anyway.
Going back to Mike’s article, he suggests a few things to think about when you talk about accessibility with other people who work in the fields of web design and development:
Be a translator: Learn the specs and translate them into English.
Be willing to give back: If somebody asks for your help, try to find time to respond.
Accessibility is happy: Give accessibility a smiling face.
Encourage don’t admonish: When somebody makes progress, acknowledge that instead of criticising what they do wrong.
Good suggestions, Mike. I will try to get better at each of them. For instance, I guess I could be a little less grumpy sometimes when I come across bad examples or implementations. But not always… ;-)
Comments[ 0 ]
Post a Comment