This is being cros posted to Blind-l, access-l and vicug-l but please feel
free to forward it to anyone who may not be included here who might be
interested or impacted.
The below is an important announcement concerning access to the web for
people with disabilities and others who may have special circumstances. I
urge you all to review and follow the commenting instructions. If you have
questions about this draft or want more information as well, you can
contact:
Judy Brewer who is ccd on this notice.
Thanks to Judy and the working group and other contributors to this draft.
Johnnie Apple Seed
----- Original Message -----
From: "Judy Brewer" <[log in to unmask]>
To: "WAI Interest Group" <[log in to unmask]>
Sent: Thursday, November 25, 2004 1:06 AM
Subject: Call for Review: Working Draft of Web Content Accessibility
Guidelines 2.0
Dear WAI Interest Group Participants,
A new Working Draft of the Web Content Accessibility Guidelines 2.0 (WCAG
2.0) as well as four supporting documents were published 19 November 2004.
The Web Content Accessibility Guidelines Working Group (WCAG WG) invites
you to comment on these documents. W3C Working Drafts provide opportunities
for public comment during the development of a specification. Please send
comments to the public comments mailing list by 3 January 2005:
[log in to unmask]
WCAG 2.0 addresses accessibility of Web content for people with
disabilities. It will apply to a wider range of Web technologies than WCAG
1.0 and is intended to be understandable to a wider audience.
Since the previous public Working Draft of WCAG 2.0, published on 30 July
2004, the WCAG WG has incorporated over 200 public comments. To help
address usability issues raised with the July drafts, WAI also developed
"Introduction to Web Content Accessibility Guidelines (WCAG) 2.0 Working
Draft Documents" as a starting point for WCAG 2.0. The Introduction
illustrates the relationships between WCAG 2.0 and the supporting
documents, and links to the current version of each document. The
Introduction is available at:
<http://www.w3.org/WAI/intro/wcag20>
The five documents published on 19 November 2004:
- Web Content Accessibility Guidelines 2.0
<http://www.w3.org/TR/2004/WD-WCAG20-20041119/>
- General Techniques for WCAG 2.0
<http://www.w3.org/TR/2004/WD-WCAG20-GENERAL-20041119/>
- HTML Techniques for WCAG 2.0
<http://www.w3.org/TR/2004/WD-WCAG20-HTML-TECHS-20041119/>
- CSS Techniques for WCAG 2.0
<http://www.w3.org/TR/2004/WD-WCAG20-CSS-TECHS-20041119/>
- Client-side Scripting Techniques for WCAG 2.0:
<http://www.w3.org/TR/2004/WD-WCAG20-SCRIPT-TECHS-20041119/>
The Working Group is interested in discussion of the following questions.
1. In general, is this WCAG 2.0 Working Draft easy to understand?
Please identify phrases that are difficult to understand. Please
suggest wording for the Working Group to consider.
2. Does "Introduction to Web Content Accessibility Guidelines (WCAG) 2.0
Working Draft Documents" clarify the relationships between WCAG 2.0
and the four Techniques documents?
3. In WCAG 1.0, the WCAG WG identified temporary solutions for authors;
several guidelines begin "until user agents..." If WCAG 2.0 assumes
that end-users have browsers that conform to the User Agent
Accessibility Guidelines, WCAG 2.0 becomes simpler, but what is the
effect on the end-user? Please read and comment on the Editorial
Note at:
<http://www.w3.org/TR/2004/WD-WCAG20-20041119/#baseline-note>
4. The first public Working Draft of Client-side Scripting Techniques
for WCAG 2.0 was published to solicit early review and discussion.
Related to question #2 (about Baseline Technologies Assumption)
the WCAG WG asks, "Are functional alternatives required for content
that contains scripting?" In other words, should WCAG 2.0 move away
from the alternative functionality requirement of WCAG 1.0
Checkpoint 6.3 [1]?
[1] <http://www.w3.org/TR/WCAG10/wai-pageauth.html#tech-scripts>
Please send your comments by 3 January 2005 to:
[log in to unmask]
The archive for that mailing list is available at:
<http://lists.w3.org/Archives/Public/public-comments-wcag20/>
When sending comments, please:
- State the issue as clearly and simply as possible.
- Provide links to specific examples or references.
- If possible, suggest solutions.
- Remember that the Working Group welcomes volunteers
to help with the work.
When waiting for responses to comments:
- Track your issue in the open issues list
<http://trace.wisc.edu/bugzilla_wcag/condensedreports/wcag2_issues.php>
- Follow up on the mailing list if you don't find your issue in the
open issues list.
Please let us know if you have any questions. Many thanks in advance for
your comments. Additional information on the Working Group is available at:
<http://www.w3.org/WAI/GL/>
Note:
Our target is for WCAG 2.0 to become a W3C Recommendation in the first half
of 2005. Until then, WCAG 1.0 will continue to be the current and stable
document to use. If your site currently conforms to WCAG 1.0, be assured
that conformance to WCAG 2.0 will not require a complete redesign of your
site but it will likely require some tweaks.
Note:
This message may be circulated to other lists, avoiding cross-postings
where possible.
Wendy Chisholm - W3C Team Contact for WCAG WG
Judy Brewer - Director, Web Accessibility Initiative, W3C
Gregg Vanderheiden - Chair of WCAG WG, and Director of Trace R&D Center
--
Judy Brewer +1.617.258.9741 http://www.w3.org/WAI
Director, Web Accessibility Initiative (WAI), World Wide Web Consortium
(W3C)
MIT/CSAIL Building 32-G530
32 Vassar Street
Cambridge, MA, 02139, USA
VICUG-L is the Visually Impaired Computer User Group List.
To join or leave the list, send a message to
[log in to unmask] In the body of the message, simply type
"subscribe vicug-l" or "unsubscribe vicug-l" without the quotations.
VICUG-L is archived on the World Wide Web at
http://maelstrom.stjohns.edu/archives/vicug-l.html
|
