Tools aren't skills aren't knowledge
Yesterday I was asked by a colleague in another local authority what software I had used to make our website accessible. The question threw me for a second. Since I no longer think of web development in terms of tools, it hadn't consciously occured to me that others in the business still do. I started to list the software tools I do use - HomeSite, TopStyle, Bullet Proof FTP, Firefox, CSE Validator Pro and so on. But of course software doesn't make websites accessible - at the stage we're at as an industry it's pretty much down to knowledge, research and understanding.
So I explained that it wasn't really the software I had used that was important so much as the time I had invested in learning what makes an site accessible, through the GAWDs mailing list, AccessifyForum and many websites. The more I thought about it the more I realised what a steep learning curve I'd been on in the past 12 months, and just how much time I'd dedicated to re-learning the fundamentals of the job of a web developer. Lists like css-discuss and Evolt's thelist, sites like ALA and QuirksMode, books by Zeldman, Meyer and Clark - I've read them all over the past 2 years or so, tried to learn from them and apply what I've learned. How do you get that across to someone who's looking for a magic software bullet to achieve a worthy aim, without scaring them off?
When it comes down to it tools can only be used to apply the knowledge you have using the skills you've developed (or if you're lucky were born with), and the production of just about anything of quality relies on all the presence of all three.