molly.com
Saturday 25 June 2005
WaSP ATF: Already a Smoking Gun?
It’s not even two days since WaSP announced the formation of the Accessibility Task Force, quickly coined the “ATF” by several folks despite a more sobering U.S. federal agency that goes by the same initialism (or would that be acronym?).
While clearly a long time coming, the immediacy and detailed response to the formation of this WaSP task force proves its timeliness and need.
I present to you our first exhibit, “ATF: Not Alcohol, Tobacco, or Firearms” by Joe Clark who provides a very comprehensive list about where he feels our efforts and energy should (and perhaps should not) go.
He’s got many great points in the article, I especially am interested in his advocacy regarding the testing of CSS layouts. Many of us, myself included, have made the mistake that a CSS layout is more accessible by default. While certainly a step in the right direction, just creating a site using CSS does not an accessible site make.
As our second exhibit, our own Andy Clarke has posted the announcement to his personal site and the responses have been in most cases very positive and often very specific in detail.
Clearly, the WaSP ATF has lots of work ahead. While the road not yet traveled appears somewhat bleary, smoky and a bit dangerous, it’s a great comfort to know how much support we have. This is true both in terms of the new members of WaSP and the ATF but also from you, our community at large, as we work together to improve Web standards implementation and methodologies worldwide.
[ Cross-posted with WaSP BUZZ, 25 June 2005 ].
Filed under: WaSP, standards, web design and development
Posted by: Molly | 13:32 | Comments (21)
Hi Molly, I’ve just read through Joe’s article and found it covered many aspects of (web) accessibility and included technologies that I’m not directly associated with at the moment – but bringing them to my attention all the same. It was very interesting to read his remarks on CSS, Opera, and hints at Adobe/PDF too.
The ‘ATF’ have definitely got a large job ahead of them – and maybe the force will need sub-divisions to cope with the workload(?) As a strong supporter of Web Accessibility – I wish the team every success in this venture and will try to follow the updates as they happen.
Matt
What Matt said plus an extra on the acronym.
Across the World, every mechanic in existence knows ATF means Automatic Transmission Fluid, a thin, usually red, oil that tastes only slightly better than diesel fuel!
really something to think about. what would it be, css and tables? javascript?
Going Yoda on us now, Molly?
I’ve expressed my thoughts elsewhere on this already, I won’t repeat them here…
I think using ATF as the acronym for this organization is a mistake. The impression it gives is that the task force will be an overbearing, overzealous group single-minded of purpose and rigid in enforcement.
Perhaps it could be changed to simply WaSP Task Force or WTF. Just a thought.
How do you plan to address Javascript related issues (and without shouting, if I may add)? JS and I; we’re like this! [finger thingy]
Neither does, the uhh, opposite. Accessibility and CSS are like Christianity and the GOP.
#Laughing #
Keith Burgin: WTF?
Yes, I can WaSP having a lot of luck approaching vendors with the acronym of ‘WTF’…..(That’s what the Vendors would be thinking too!)
Yes, I can SEE WaSP having a lot of luck approaching vendors with the acronym of ‘WTF’…
(Or I could use the word ‘SEE’ in the previous post if I had woken-up properly! Sorry Molly)
With the creation of the Department of Homeland Security, ATF (which was part of the Treasury Dept.) was broken up. The firearms part went to the Justice Dept., the alcohol and tobacco parts went to the Tax and Trade Bureau to be come the Alcohol, Tobacco, Tax and Trade Bureau.
LOL @ WTF. Got my vote.
Ha! All WaSP Task Forces are WTFs. That’s great! I can see upcoming press releases now
“The impression it gives is that the task force will be an overbearing, overzealous group single-minded of purpose and rigid in enforcement.”
I think that would really only be a problem if the acronym in question was “RNC”.
Hi,
I thank all those working on Web Site Accessibility ! I have a friend who can easily navigate just about any site using window eyes and in his day was the King of FoxPro programming !
I have long thought a test team of folks with different types of disabilities should be organized to test and prove out all the accessibility design theories.
Molly – I’ve been digging the accessibility coding tips (and others) in your book: 250 HTML and Weg design Secrets
Eric –
What, are you some kinda liberal or something?
Thanks Molly for helping pull the motley ATF gang together. They’re really needed!
As a follow on to Joe’s Clarkes (and your) wonderings about how CSS layouts affect assistive technology, I have the first round of experimentation going on over at Access Matters. This week, it is 4 of the Zen Garden designs, all visually different.
Next week, we’ll try some variations on source order.
Are there any further updates with this? Any plans that the task force can announce?
{position:(un)fixed;} for IE
While coding the layout for my (soon to be launch) company website, I had this sudden itch for making the interface a bit more unique. I wanted the entire sidebar (menu, news, updates,… etc) to be static while the rest…
Are there any further updates with this?
very interesting, whats the update on the ATF?
c
verry interesting, thank you
thanks for your sharing