RE: 508 Question

Hi Inthane,
I am working backwards and thinking this.

*         Let's assume that I am using older technology such as Lynx, which, 
last time I checked, does not see JavaScript on the client side. Assuming that 
I am right about Lynx, the site needs to alert the user that scripts are 
running on the site. The most common way to do that is to use the <noscript> 
HTML tag.

*         Also, according to me, other paragraphs cover the output of scripts. 
For example, if a script uses a document.write statement and that statement 
creates HTML, and the HTML has an <img> tag, the <img> tag must have an alt 
attribute. That would be covered under paragraph (a), which talks about text 
alternatives.

I'm choosing to take a very literal approach to the paragraph that alerts the 
user about the presence of scripts. See what I mean? I'm letting the other 
paragraphs take over once we get to the point where we produce output. I don't 
care what generates the output as long as it is covered.

Thanks.

Jim

----------
Jim Homme, Usability Engineering.
412-544-1810.
Catch the gratitude attitude.

From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of The Elf
Sent: Tuesday, March 31, 2009 1:47 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Re: 508 Question

ok Jim,
I went over it five times before I answered, so this is not an snap answer, I 
see other words in this as more critical and defining:

utilize scripting languages(key word here, what's doing the providing) to 
display content (that which the scripting language is displaying),
the information provided by the script (again what is provided by the script or 
the afore mentioned scripting language) shall be identified with functional 
text (functional text I see as a text content that the adaptive technology can 
function with, instead of non functional text like graphics)

this is what I am seeing here, which means that a lot of java, and most general

captcha  coding does not meet 508 compliance



HTH,

inthane
----- Original Message -----
From: Homme, James<mailto:james.homme@xxxxxxxxxxxx>
To: programmingblind@xxxxxxxxxxxxx<mailto:programmingblind@xxxxxxxxxxxxx>
Sent: Friday, March 27, 2009 6:23 AM
Subject: 508 Question

Hi,
Paragraph (l) of the Section 508 web standards reads as follows.
When pages utilize scripting languages to display content, or to create 
interface elements, the information provided by the script shall be identified 
with functional text that can be read by assistive technology.
I'm focusing on the word "identified" in that paragraph. This sounds like that 
assistive technology only needs to know that script elements exist, not that it 
necessarily needs to be able to use those elements. Note that I'm only going on 
the language of the paragraph, not how I think that pages with scripts should 
function, as in assistive technology should be able to work with the script 
elements besides identify them. My question is how do you interpret this 
paragraph?
Thanks.
Jim


----------
Jim Homme, Usability Engineering.
412-544-1810.
Catch the gratitude attitude.


________________________________
This e-mail and any attachments to it are confidential and are intended solely 
for use of the individual or entity to whom they are addressed. If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it. If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this e-mail without the author's prior permission. 
The views expressed in this e-mail message do not necessarily represent the 
views of Highmark Inc., its subsidiaries, or affiliates.

________________________________
This e-mail and any attachments to it are confidential and are intended solely 
for use of the individual or entity to whom they are addressed. If you have 
received this e-mail in error, please notify the sender immediately and then 
delete it. If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this e-mail without the author's prior permission. 
The views expressed in this e-mail message do not necessarily represent the 
views of Highmark Inc., its subsidiaries, or affiliates.

Other related posts: