The real trick is to understand what the specification means and why it says what it says. There has always been disputes about the validity of an automated tester saying 'Yes this site is compliant'. You can code a terrible page that will pass an automated test. It is important to code in the spirit and intent of the specification and not necessarily to the word of the specification. Online validators are a tool to help you get there.
I do use an automated tester, but not very often. I am familiar enough with the specs that I do not need to. As the page near completion I will run a validator to fix a few probs.
I have friends in Iriga - visit Iriga Joe Motors. =)
On 4/13/05, Cole Kuryakin - x7m <[EMAIL PROTECTED]> wrote:
Thanks Shane. I'll give it a look - Getting specific books from local
bookstores here (in the philipines) can be a real challenge, but I'll see if
I can source the one you've recommended.
After you do a site (or during) do you "validate" your code against one of
these Accessibility web sites I mentioned?
Cole
--
______________________________________
"Bugs are, by definition, necessary.
Just ask Microsoft!"
www.co.sauk.wi.us (Work)
www.arionshome.com (Personal)
www.freexenon.com (Consulting)
______________________________________
Take Back the Web with Mozilla Fire Fox
http://www.mozilla.org/products/firefox/
Making a Commercial Case for Adopting Web Standards
http://www.maccaws.org/
Web Standards Project
http://www.webstandards.org/
Web Standards Group
http://www.webstandardsgroup.org/
Guild of Accessible Web Designers
http://www.gawds.org/
