- From: Al Gilman <asgilman@iamdigex.net>
- Date: Wed, 03 May 2000 10:23:15 -0500
- To: Web Content Accessibility Guidelines <w3c-wai-gl@w3.org>
[just some notes] At 08:21 AM 2000-05-03 -0400, Wendy A Chisholm wrote: >1. Add requirements beyond HTML and CSSWCAG 2.0 will include requirements for: >HTML >CSS >SVG >SMIL >MathML >Metadata -- use of metadata includes topics that stretch across WCA and PF territory. >DOM -- not clear how to separate WCA, UA, PF roles in DOM area >XML technologies (DTD authoring? namespaces?) -- as with metadata, contains WCA and PF action items, likely. >Non-W3C technologies such as JAVASCRIPT, PDF, and Flash -- I would attempt to group the requirements functionally, not politically like this. -- for example, have a work item on forms. This group would work on fill-out forms -- in HTML, XHTML, PDF, and xHTML+JAVASCRIPT. -- A concern is that 'forms' might make more progress as a WG of its own. -- My latest soapbox: what the world needs is a reference design for a universally -- accessible absentee-ballot application. >WCAG 2.0 requirements should be expressed in generic terms so that they may >apply to more than one markup language. -- I thought at CSUN we were doing pretty well at arriving at a shared vision of a -- multilevel approach with abstract and specific both included each in its place. -- Maybe I don't understand where the remark you are promising goes. > >At 09:26 AM 5/2/00 , Jon Gunderson wrote: >>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 > >-- >wendy a chisholm >world wide web consortium >web accessibility initiative >madison, wi usa >tel: +1 608 663 6346 >/-- >
Received on Wednesday, 3 May 2000 10:17:46 UTC