W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2000

RE: Final review of WCAG requirements document prior to publi cation as a W3C note

From: Cynthia Shelly <cyns@microsoft.com>
Date: Tue, 2 May 2000 18:57:45 -0700
Message-ID: <71EFB697F464184990DF0AC5B050E9EE0306F9D1@red-msg-17.redmond.corp.microsoft.com>
To: "'Jon Gunderson'" <jongund@ux1.cso.uiuc.edu>, Wendy A Chisholm <wendy@w3.org>, Ian Jacobs <ij@w3.org>, Jason White <jasonw@ariel.ucs.unimelb.EDU.AU>
Cc: Web Content Accessibility Guidelines <w3c-wai-gl@w3.org>
I tend to agree with Jon that people will be looking for JavaScript or DHTML
rather than DOM.  Could we solve this by calling the section DOM and adding
the other related non-W3C technologies in parens?  Something like:

Section 12.8 DOM (Includes JavaScript, DHTML, blah, foo, and stuff)

That way a visual scan or text search for one of these technologies would
get people to the right place.

-----Original Message-----
From: Jon Gunderson [mailto:jongund@ux1.cso.uiuc.edu]
Sent: Tuesday, May 02, 2000 6:26 AM
To: Wendy A Chisholm; Ian Jacobs; Jason White
Cc: Web Content Accessibility Guidelines
Subject: Re: Final review of WCAG requirements document prior to
publication as a W3C note


Wendy,
It seems to me that JavaScript is what people would more likely be looking 
for accessibility information on, than a topic called the DOM.

Jon


At 07:21 AM 5/2/00 -0400, Wendy A Chisholm wrote:
>I have included "DOM" in the list.
>--w
>
>At 11:10 AM 4/28/00 , Jon Gunderson wrote:
>>I would like to see "JavaScript" under the added requirements in the 
>>following section:
>>
>>1. Add requirements beyond HTML and CSS
>>
>>I know that scripting is alluded to in the following statement:
>>"Clearly specify how content that is tailored according to client or user 
>>capabilities may conform (dynamic content or database driven)"
>>
>>But I think it should have its own section for some of the following
reasons:
>>
>>1. What is the "standard" or "recommended" way to support the DOM. 
>>Currently IE and NN support different models for access the DOM with
scripting.
>>
>>2. Designing for device independence.
>>
>>3. Identifying open versus proprietary scripting markup techniques
>>
>>
>>Jon
>>
>>Jon Gunderson, Ph.D., ATP
>>Coordinator of Assistive Communication and Information Technology
>>Chair, W3C WAI User Agent Working Group
>>Division of Rehabilitation - Education Services
>>College of Applied Life Studies
>>University of Illinois at Urbana/Champaign
>>1207 S. Oak Street, Champaign, IL  61820
>>
>>Voice: (217) 244-5870
>>Fax: (217) 333-0248
>>
>>E-mail: jongund@uiuc.edu
>>
>>WWW: http://www.staff.uiuc.edu/~jongund
>>WWW: http://www.w3.org/wai/ua
>
>--
>wendy a chisholm
>world wide web consortium
>web accessibility initiative
>madison, wi usa
>tel: +1 608 663 6346
>/--

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Chair, W3C WAI User Agent Working Group
Division of Rehabilitation - Education Services
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL  61820

Voice: (217) 244-5870
Fax: (217) 333-0248

E-mail: jongund@uiuc.edu

WWW: http://www.staff.uiuc.edu/~jongund
WWW: http://www.w3.org/wai/ua
Received on Tuesday, 2 May 2000 21:58:30 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:04 GMT