Hi

We're all application developers, so how does everyone here ensure their
site is accessible? I don't know about the rest of you but we are never
given time to scan every aspect of our web-site to ensure it's accessible.

So how do you guys deal with this? Do you have help from others or do you do
it yourself? Or don't you care lol?

Thanks
Kev

Mantorok napisa³(a):
> Hi
>
> We're all application developers, so how does everyone here ensure their
> site is accessible? I don't know about the rest of you but we are never
> given time to scan every aspect of our web-site to ensure it's accessible.
>
> So how do you guys deal with this? Do you have help from others or do you do
> it yourself? Or don't you care lol?
>

You can try those sites:
http://webxact.watchfire.com
http://www.contentquality.com

Also good idea is using Firefox with extensions (for example web
developer extension). There are many options to test different aspects
of your site.

And of course the best and most simple test - try to use your site with
lynx browser.

--
PP

I found it best to simply follow standards.

W3C have a useful document highlighting the important points:
Web Content Accessibility Guidelines 1.0 @
http://www.w3.org/TR/WAI-WEBCONTENT/

I've also found that following these standards has a great side-effect
on your web app - it becomes more compatible with many of the tools out
there (search engines, bookmark / clipping services, etc) and it makes
it more reliable (increasing browser compatibility, less dependency on
unreliable JavaScript, etc).

Yes indeed who needs unreliable JavaScript perhaps the most ubiquitous
language on the net.

"yanivg" wrote:

> I found it best to simply follow standards.
>
> W3C have a useful document highlighting the important points:
> Web Content Accessibility Guidelines 1.0 @
> http://www.w3.org/TR/WAI-WEBCONTENT/
>
> I've also found that following these standards has a great side-effect
> on your web app - it becomes more compatible with many of the tools out
> there (search engines, bookmark / clipping services, etc) and it makes
> it more reliable (increasing browser compatibility, less dependency on
> unreliable JavaScript, etc).
>
>