Re: 20 Sept 2001 minutes

>GV Do we think that pages should be accessible with browser that do not
>support scripting?
>JM If the decision is that we won't make a decision and give them
>techniques for them to make their choices, we need to state that
explicitly.
>GV If we leave it to the dev, we have made a decision. Implies, requiring
>scripts is ok.
>WC We might want to do some research.
>JW I think that devs should be aware of the consequences of either
option.
>If require them, there are a variety of UAs that won't support them or
>turne doff for security. Therefore, limiting audience in some way. I'm a
>bit worried about mobile devices which don't have many resources.
>WC WAPScript. Need to do some research.

AvantGo, and PocketIE which are currently palm sized devices and I think
are likely a better example of currently used and future mobile devices
than the failure that is WAP, both have reasonable scripting support,
although only really in the area of forms, and core script, other DOM
methods are generally unavailable especially in AvantGo.

I am absolutely horrified by the notion of requiring scripts, we have CERT
advisory's stating scripting should be disabled, we have a level of
scripting ability amongst developers that is pathetic, most can hardly
make scripts that work, let alone scripts that work and are accessible.
There's little that scripts give that make otherwise inaccessible content
accessible (are there some examples or even just ideas?)

I've now read and participated in most usenet and other community
javascript groups for 3 years or more, I've got a lot of scripting
knowledge and an interest in good scripting, what I see is little thought
of accessibility (even when the interest is there, appreciating how your
script may effect others isn't easy.)  I also have to be honest and don't
believe from reading the previous minutes etc. that the group currently
has the knowledge of scripting to provide example and techniques in the
script arena that would be required to even explain how scripting could be
used accessibly let alone how it can be used to make inaccessible content
accessible.

I'm extremely pro-scripting, but it cannot and should not be relied on in
webpages.

Regards,

Jim.

Received on Thursday, 20 September 2001 19:17:26 UTC