508 compliance and Javascript - Page 2

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View

Re: 508 compliance and Javascript

Quoted text here. Click to load it

Why go through the legal and technical minefield of trying to define
yourself out of a hole, instead of designing something so that it works
without special requirements?

Quoted text here. Click to load it

Where that (the end of the last sentence) falls apart is people's
incorrect perceptions of what disabilities preclude (e.g. blind people CAN
play table tennis, despite what you might think), or what a disabled
person might do for others as their job (e.g. the purchasing officer for
some company may be blind).

If you insist on e-mailing me, use the reply-to address (it's real but
temporary).  But please reply to the group, like you're supposed to.

This message was sent without a virus, please destroy some files yourself.

Re: 508 compliance and Javascript

wardy wrote:
Quoted text here. Click to load it

Having worked for state and local government, having worked in a
publicly held business heavily monitored by state and local government,
and so having taken a number of mandated classes and courses on what is
"valid" and what is "not valid", I assure you there is only one way to
know for sure:

When the judge or jury comes back with a verdict.

In the meantime continue doing your best, and please know that I am not
a lawyer and that this has not been legal advice in any way shape or form...

Re: 508 compliance and Javascript

On Thu, 16 Mar 2006 14:17:33 -0800, VK wrote:
Quoted text here. Click to load it

You have argued (and I have no reason to doubt the validity of your
argument) that the US law fails to do anything for disabled web users
provided web authors are devious enough to treat everyone equally badly.

The UK DDA is more sane.  It derives its purpose from an evident
inequality rather than from an Alice in Wonderland notion of equal
treatment: simple technologies exist that enable web sites to be
comparatively accessible, and the DDA requires that organisations do
everything reasonable to deploy these technologies.


Re: 508 compliance and Javascript

wardy wrote:
Quoted text here. Click to load it
To make a long story short.
Just place some text links a long the bottom of the pages that contain
the JS navigation. That means people who can't use JS, or who have it
turned off for whatever reason, can still navigate the site. Then just
instruct visitors accordingly.
As a blind webmaster, I do take a lot (if not all of these issues
concerning web accessibility very siriously).
You can view my site at: http://freewebdesign.cjb.cc
Or if that link is down, as it is at the moment, view
Regards Chad.

Re: 508 compliance and Javascript

Chaddy2222 wrote:
Quoted text here. Click to load it

Great advise - the same as I gave. And you always can hide it from
script-enabled browsers by placing it into <noscript> block.

Quoted text here. Click to load it

And you are using Internet Explorer 6.0 under Windows XP SP2 (sorry for
looking at your userAgent string). So you may tell if you know a
condition where a blind person would turn off script support or
<acronym>CSS</acronym> support or would use Lynx to get a better
accessibility on the Web?

Re: 508 compliance and Javascript

VK wrote:
Quoted text here. Click to load it
That's ok.
So you may tell if you know a
Quoted text here. Click to load it
Yes, well actaully, according to a lot of stats I have noticed, through
the hit counter on my site, which is hidden to those who have JS
enabled, if you don't enable JS you get a text link pointing to where
the counter is, but you need to log in to get the info.
But, back to the main point, around 1% of people Disable JS.
But, their are some people with low vision who use text only browsing
environments, which do not support images or JS. Or they use FF with JS
and images disabled.
CSS is another argument in itself, it's imposable to tell wether people
have CSS disalbed, and it would be just as hard to know if images are
being disabled by the user as well.
The main point, is that you don't know what sort of a set-up a user
will have, you can only prodict, so if you want your sites to be
accessed by the largest range of people, make them as simple of posable
and only use extra functions where necicary, such as Flash and
JavaScript. Also, for items such as form validation, it really should
be done server side. In case the user has JS disabled. It's also more
I hope this helps.
Regards Chad. http://home.primus.com.au/kellykk/freewebdesignonline

Re: 508 compliance and Javascript

Chaddy2222 wrote:
Quoted text here. Click to load it

You are luckier then I am then, because my traps stay empty so far. But
as I said in another place a right location for a successfull hunting
is everything (smile).

Quoted text here. Click to load it

Doesn't help to fight for extra funding with my customers for extra
coverage of 1% of exclusive visitors (if they are not officially
disabled). But it does help for common considerations while planning
the site.

May ask if you are using Microsoft text-to-speach module or any other
text-to-speach module integrated into your browser?

Does your current software supports aural style rules? If so did you
visit any sites with aural styling implemented and was it helpful?

Given a choice: would you prefer from a site to have its own
text-to-speach and speach recognition tools like
<acronym>SALT</acronym> or would you prefer to let it go as it is so do
not interfer with your own software?

Site Timeline