WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Section 508 Question and Scripting languages

for

From: Joshue O Connor
Date: Jan 7, 2006 5:40AM

I am based in Ireland so please forgive me if I am speaking out of turn. The post brought up a couple of issues for me
so I am creating a new thread.

> The question is this: if the JS provides core functionality (for example
> a text input that fires on "OnSelect" without the presence of a submit
> button), does this fail the "interface element" criteria, even though
> there really is no means of providing "functional text"?

Should you use JS or other non-supported scripting languages for core functionality at all?.

JS has a "do-not-touch " status in the world of accessibility that I think is unwarranted.
This may change in the future when support for scripting languages improves (if). JS is a potent and powerful
client side scripting language and has much promise for powerful Web based applications via the DOM.

Anyway, the checkpoint to my mind is worded in a rather convoluted fashion. It could be more straightforward.
What the checkpoint refers to as "functional text" seems to refer to "indication of function", in that if you click this button, this action will happen.
This should always be clear for all to see.

Interface elements can be designed so anything "under the hood" can be shown to the user in a clear fashion.
So practically, its a matter of using good design supported by languages that AT devices will currently recognise.

As an aside, it is better (IMO) that websites and other ICT's are practically accessible and usable rather than the onus being on fitting with
or failing on an obscurely (or badly) worded checkpoints. I realise this whole issue does have teeth however, as under federal law in the US you need to be 508 compliant. It is not like this in Europe and it brings up the issue of "getting the standards right" from the beginning.

Joshue O Connor

Web Accessibility Consultant

**Centre for Inclusive Technology (CFIT)* *
National Council for the Blind of Ireland

CFIT Website:www.cfit.ie
<EMAIL REMOVED> +353 1 8821915






John Foliot - WATS.ca wrote:
> As I am less familiar with compliance to Section 508, perhaps somebody
> could answer a question for me.
>
> Checkpoint Section 1194.22(l) states: "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."
>
> The question is this: if the JS provides core functionality (for example
> a text input that fires on "OnSelect" without the presence of a submit
> button), does this fail the "interface element" criteria, even though
> there really is no means of providing "functional text"?
>
> Instinctively I know it is "wrong", but does it fail on the technical
> merit as well? Ideally an authoritive reference would be the best, but
> otherwise some experienced input would be great.
>
> Thanks in advance.
>
> JF
> --
> John Foliot <EMAIL REMOVED>
> Web Accessibility Specialist / Co-founder of WATS.ca
> Web Accessibility Testing and Services
> http://www.wats.ca
> Phone: 1-613-482-7053
>
>
>
>
>
>
>