Highlights Drafts through 2008
See the main planning page for current planning, original parameters, and such.
Note: This Web page is an internal working draft and should not be referenced or quoted under any circumstances.
Archive Draft Blurbs through April 2008
Ordered with most recent at the top, oldest at the bottom:
WCAG 2.0 CR
[drafts of the WCAG 2.0 Last Call announcements]
last updated $Date: 2009/06/26 00:29:54 $
NOTE: This information is an unapproved draft and should not be referenced or quoted under any circumstances. Thank you.
W3C Home Page (and NewsWire and Member Newsletter):
W3C Invites Implementations of Web Content Accessibility Guidelines (WCAG) 2.0 (Candidate Recommendation)
2008-0@-@@: The Web Content Accessibility Guidelines (WCAG) Working Group has released Web Content Accessibility Guidelines 2.0 as a Candidate Recommendation, and published updated Working Drafts of Understanding WCAG 2.0 and Techniques for WCAG 2.0, along with How to Meet WCAG 2.0 and Comparison of WCAG 1.0 Checkpoints to WCAG 2.0. WCAG defines how to make Web sites, Web applications, and other Web content accessible to people with disabilities. Read the press release, invitation to implement, Overview of WCAG 2.0 Documents, and about the Web Accessibility Initiative.
notes:
- recent CR blurbs: XQuery Update Facility 1.0, SMIL 3.0
WAI Highlight for home page & RSS feed:
WCAG 2.0 On the Move: Ready to Test-Drive
We are excited to announce that Web Content Accessibility Guidelines 2.0 (WCAG 2.0) was published as a W3C Candidate Recommendation on 30 April 2008. The Candidate Recommendation stage means that there is broad consensus on the technical content, and W3C invites you to implement WCAG 2.0. Please see additional information in:
- WCAG 2.0 Candidate Recommendation Ready to Test Drive
- How WAI Develops Accessibility Guidelines through the W3C Process
- Overview of WCAG 2.0 Documents
If you are interested in sharing implementation experience, please let us know by 23 May 2008. (2008-04-30)
notes:
- title brainstorms (note that the most important message for this is
announcement is *WCAG is moving forward to the next stage*, and the
request for implementations is secondary)
- WCAG 2.0 On the Move: Ready for Test-Drives
- WCAG 2.0 Moves Up: Ready for Test-Drives
- WCAG 2.0 Moves Up: Ready for you to Test-Drive
- Ready for Implementations: WCAG 2.0 Advanced to the Next Stage
- Ready for Implementations: WCAG 2.0 Advances to the Next Stage
- beta test ?
- taste test
WAI IG email:
WCAG 2.0 Candidate Recommendation Ready to Test Drive
Dear WAI Interest Group Participants,
The Web Content Accessibility Guidelines (WCAG) Working Group is excited
to announce the publication of WCAG 2.0 as a W3C Candidate Recommendation on
@@ Month. WCAG 2.0 explains how to make Web sites, applications, and other
content accessible to people with disabilities, and many elderly users.
http://www.w3.org/TR/2008/CR-WCAG20-20080430/
Candidate Recommendation (CR) is a major step in the W3C standards
development process; it signals that there is broad consensus in the Working
Group and among public reviewers on the technical content of WCAG 2.0. The
W3C Process stages are described in:
How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
The primary purpose of this CR stage is for developers and designers to
"test drive" WCAG 2.0 to demonstrate that WCAG 2.0 can be implemented in Web
sites. WAI encourages a broad range of Web sites and Web applications to use
WCAG 2.0 at this stage, and share implementation experience. For information
on submitting your implementations, see:
WCAG 2.0 Candidate Recommendation Implementation Information
http://www.w3.org/WAI/WCAG20/CR/
If you plan to provide implementations, please let us know your
intentions by *23 May 2008*.
Actual implementations are due by *30 June 2008*.
From an accessibility prespective, it it important to note that some WCAG
2.0 requirements are at risk; that is, they may not be included if there are
not sufficient implementations. Items at risk are listed at:
http://www.w3.org/TR/2008/CR-WCAG20-20080430/#status_risk
While the focus of this stage is to collect implementations, you can also
submit comments using the form or email address provided in:
Instructions for Commenting on WCAG 2.0 Documents
http://www.w3.org/WAI/WCAG20/comments/
The different WCAG 2.0 documents that the WCAG Working Group updated with
this publication are introduced in:
Overview of Web Content Accessibility Guidelines (WCAG) 2.0 Documents
http://www.w3.org/WAI/intro/wcag20.php
A key tool for using WCAG 2.0 documents, which was previously called the
"Quick Reference", is:
How to Meet WCAG 2.0: A customizable quick reference to WCAG 2.0
requirements...
http://www.w3.org/WAI/WCAG20/quickref/
For more information about the Candidate Recommendation status of WCAG 2.0
and the changes since the last publication, see:
"Status of this Document" section of WCAG 2.0
http://www.w3.org/TR/2008/CR-WCAG20-20080430/#status
WCAG 2.0 is part of a series of accessibility guidelines/standards
developed by WAI, which are listed in:
WAI Guidelines and Techniques
http://www.w3.org/WAI/guid-tech.html
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Please let us know if you have any questions. Thank you in advance for your help implementing WCAG 2.0.
Regards,
~Shawn Lawton Henry and Judy Brewer
On behalf of:
Loretta Guarino Reid, Co-chair of WCAG WG, and Computer Scientist, Google
Inc.
Gregg Vanderheiden, Co-chair of WCAG WG, and Director of Trace R&D
Center, University of Wisconsin-Madison
Michael Cooper, W3C Team Contact for WCAG WG
notes:
- other subject brainstorms:
- WCAG 2.0 Candidate Recommendation Ready for Developers to Test Drive
- Call for Implementations: Test-Drive WCAG 2.0 Candidate Recommendation
- Call for Implementations: WCAG 2.0 Ready for Test-Drives
- WAI Invites Test-Drives of WCAG 2.0 Candidate Recommendation
W3C Q&A blog post:
WCAG 2.0 takes a giant leap forward — Now it's your turn
WCAG 2.0 is going, boldly, where it's never gone before: Today WCAG 2.0 is at "W3C Candidate Recommendation"! Can you feel the Web accessibility world shake? Candidate Recommendation means that we think the technical content is stable and we want developers and designers to start using WCAG 2.0, to test it out in every-day situations. For more about Candidate Recommendation, see How WAI Develops Accessibility Guidelines through the W3C Process.
I hear you asking, "When will it be completed?" We're optimistic that it will indeed be completed in 2008. If implementation goes well and there are no significant new issues, the "Proposed Recommendation" of WCAG 2.0 should be published in the third quarter of 2008, with the final Web standard W3C Recommendation published about two months after that.
What's important now is that we need your help moving WCAG 2.0 to the next stage. In order to advance WCAG 2.0, we need to demonstrate that it can be implemented in different types of Web content, in a variety of human languages, and using a variety of technologies. We're looking for at least two independent implementations of every success criterion, as well as several websites that conform at each level (A, AA, AAA). (Success criteria and levels are introduced in Overview of WCAG 2.0 Documents.) We welcome WCAG 2.0 implementation experience from a wide range of environments, including e-commerce, government, education, blogs, etc.
Note that there are a few success criteria that are at risk of becoming advisory if we don't get at least two implementations of them. Here is a special appeal for implementations of those at risk success criteria.
To be a part of this stage of WCAG 2.0 implementation experience, check out WCAG 2.0 Candidate Recommendation Implementation Information.
There are a lot of reasons to start implementing WCAG 2.0 now, in addition to the possibility of your website being publicly listed as an implementation; see "What are the benefits of using WCAG 2.0?" in the WCAG 2 FAQ.
Thanks for all the support moving WCAG 2.0 towards completion!
notes:
- Is WCAG 2.0 almost done?! W3C Q&A blog post from 12 December 2007
- Instead of "Here is a special appeal for implementations of those at risk
success criteria."
perhaps "We're asking especially for implementations of those at risk success criteria." - title brainstorms:
- WCAG 2.0 advances to the next to, next to final stage!
- WCAg 2.0 ready to roll
- ...
NOTE: This information is an unapproved draft and should not be referenced or quoted under any circumstances.
John Slatin
WAI Highlight (for home page & RSS feed):
John Slatin: Honored Accessibility Colleague and Friend
WAI mourns the passing of John Slatin, who was Co-Chair of the Web Content Accessibility Guidelines (WCAG) Working Group in 2005 and 2006. Through his persistence, patience, and keen insight, John contributed greatly to the field of accessibility, especially to the development of WCAG 2.0. He will be fondly remembered and greatly missed by his colleagues at W3C/WAI and in the broader accessibility community. For more information, see the e-mail thread: Sad news regarding John Slatin, highly-regarded Web accessibility expert and advocate. (2008-03-25)
notes:
- title brainstorms (remember, will
be in archive
forever -
Shawn strongly prefers a positive title, and notes that "mourns the passing" is the first words of the blurb.- John Slatin: Honored Accessibility Colleague and Friend
- John Slatin: Web Accessibility Colleague and Friend
- John Slatin: WAI Thankful for His Contributions
- Honored for Web Accessibility Contributions: John Slatin
- John Slatin: Web Accessibility Hero
- John Slatin: Giant in Web Accessibility
- WAI Honors John Slatin's Contributions
- John Slatin, former WCAG Co-Chair, Passes Away
- Should we link to anything? Perhaps WCAG 2.0; however, I don't want it to seem like we're taking an awkward opportunity to promote WCAG or anything like that!
- I wonder about celebrating his life or honoring his contributions or something more in that tone at the beginning instead of mourning?
- With minor tweaks: WAI mourns the passing of John Slatin, who was Co-Chair of the Web Content Accessibility Guidelines (WCAG) Working Group in 2005 and 2006. Through his persistence, patience, and keen insight, John contributed greatly to the field of accessibility, especially to the development of the WCAG 2.0. He will be fondly remembered and greatly missed by his colleagues at W3C/WAI and in the broader accessibility community.
- Judy's original: WAI mourns the passing of John Slatin, previously Co-Chair of the Web Content Accessibility Guidelines Working Group. Through his persistence, patience, and keen insight, John contributed greatly to the field of Web accessibility, especially to the development of the Web Content Accessibility Guidelines 2.0. He will be fondly remembered and greatly missed by his colleagues at W3C/WAI and in the broader Web accessibility community.
- photos:
- @@
- @@
- http://www.fundamentosweb.org/2005/img/ponentes/slatin.jpg
- http://www.drw.utexas.edu/featured/accessibility
WAI IG e-mail:
Sad news regarding John Slatin, highly-regarded Web accessibility expert and advocate
Dear WAI Interest Group Participants,
WAI mourns the passing of John Slatin, who was Co-Chair of the Web Content Accessibility Guidelines (WCAG) Working Group in 2005 and 2006. Through his persistence, patience, and keen insight, John contributed greatly to the field of accessibility, especially to the development of WCAG 2.0. He will be fondly remembered and greatly missed by his colleagues at W3C/WAI and in the broader accessibility community.
For those who want more information, John and his wife Anna have chronicled his experiences on his blog "Leukemia Letters" at http://leukemialetters.blogspot.com/ and information about services will be posted there.
Sadly,
Judy Brewer...
Shawn Henry...
...
notes
UAAG March 2008
W3C News Blurb:
User Agent Accessibility Guidelines (UAAG) 2.0: First Public Working Draft
2008-03-13: The User Agent Accessibility Guidelines Working Group has published a first public Working Draft of the User Agent Accessibility Guidelines 2.0. UAAG addresses accessibility of browsers and media players, and their interoperability with assistive technologies. It will cover more advanced Web technologies than UAAG 1.0. Read the invitation to review the UAAG 2.0 Working Draft and about the Web Accessibility Initiative.
notes:
- ...
WAI Highlight (for home page & RSS feed):
For Review: UAAG 2.0 First Public Working Draft
The First Public Working Draft of User Agent Accessibility Guidelines (UAAG) 2.0 was published 12 March 2008. UAAG explains how to make browsers and media players accessible to people with disabilities, and how to make them work better with assistive technologies. UAAG 2.0 will address more advanced Web technologies than UAAG 1.0. WAI encourages you to review UAAG 2.0 and submit any comments. See:
- @@LINK@@Call for Review: UAAG 2.0 First Public Working Draft,
- User Agent Accessibility Guidelines (UAAG) Overview.
Please send comments by 14 April 2008. (2008-03-13)
question:
WAI IG e-mail:
Call for Review: UAAG 2.0 First Public Working Draft
Dear WAI Interest Group participants,
The User Agent Accessibility Guidelines Working Group invites you to
comment on the First Public Working Draft of UAAG
2.0, published 12 March 2008:
User Agent Authoring Tool Accessibility Guidelines 2.0
http://www.w3.org/TR/UAAG20/
UAAG provides guidance on designing Web browsers, media players, and other
user agents to be accessible to people with disabilities, and to work better
with assistive technologies. UAAG is introduced in the UAAG Overview at:
http://www.w3.org/WAI/intro/uaag.php
UAAG is part of a series of accessibility guidelines/standards developed by
WAI, including Web Content Accessibility Guidelines (WCAG) and Authoring Tool
Accessibility Guidelines (ATAG). These are listed in WAI Guidelines and
Techniques at:
http://www.w3.org/WAI/guid-tech.html
Substantial changes in UAAG 2.0 since UAAG 1.0 include:
- clarifications and additions to the guidelines and success criteria, per
the UAAG 2.0 Requirements document
<http://www.w3.org/TR/UAAG20-requirements/>
- restructuring the document into five principles, similar to WCAG 2.0 and
ATAG 2.0
- providing success criteria at three levels, similar to WCAG 2.0 and ATAG
2.0.
The UAAG Working Group would like feedback on the following points:
- Is the new organization of this document clear and understandable?
- Do these success criteria cover the @@greatest needs for browser and media
player accessibility?
- Based on these preliminary success criteria, are there any concerns about
implementation feasibility?
- Are there areas in which the new draft is lacking?
WAI encourages developers of browsers, assistive technologies, plug-ins,
extensions, and accessibility APIs (application programming interfaces), and
people with disabilities, to provide feedback on this first draft, and to
consider more active participation in the development process. Please send
comments by 14 April 2008 to the comment list, which is publicly archived:
public-uaag2-comments@w3.org
UAAG 2.0 is currently informative only. After the UAAG Working Group is
rechartered to produce W3C Recommendations under the W3C Patent Policy, the
group expects to advance UAAG 2.0 through the Recommendation track. For more
information, see:
* How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
* User Agent Accessibility Guidelines Working Group (UAWG)
http://www.w3.org/WAI/UA/
Note: Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Thank you in advance for your comments,
Jan Richards - UAAG Interim W3C Staff Contact. Adaptive Technology
Resource Centre, University of Toronto
Jim Allan - UAAG Working Group Chair. Texas School for the Blind and Visually
Impaired
Judy Brewer - Director, Web Accessibility Initiative, W3C
Shawn Lawton Henry - W3C WAI EOWG Chair
notes:
Blog Post:
[not doing]ATAG March 2008
W3C News Blurb:
Authoring Tool Accessibility Guidelines (ATAG) 2.0: Working Draft
2008-03-10: The Authoring Tool Accessibility Guidelines Working Group published updated Working Drafts of Authoring Tool Accessibility Guidelines 2.0 and Implementation Techniques for ATAG 2.0. ATAG helps developers design tools that are accessible so that people with disabilities can use the tools, and so that the tools help produce accessible Web content. Read the Call for Review: Updated ATAG Documents announcement and about the Web Accessibility Initiative.
notes:
- previous w3c home page blurb
- do we want to say anything about stage — e.g., previously said: ", and requests comments prior to a second Last Call."? My feeling is that most people aren't in touch with the revision history of ATAG and so we don't want to point it out...
WAI Highlight (for home page & RSS feed):
For Review: Updated ATAG 2.0 Working Drafts
Updated Working Drafts of Authoring Tool Accessibility Guidelines 2.0 and Implementation Techniques for ATAG 2.0 were published 10 March 2008. WAI encourages you to review these documents and submit any comments. See:
Please send comments by 14 April 2008. (2008-03-10)
question:
- same question as above about stage
WAI IG e-mail:
Call for Review: Updated ATAG 2.0 Working Drafts
The Authoring Tool Accessibility Guidelines Working Group invites you to
comment on the following documents published 10 March 2008:
1. Authoring Tool Accessibility Guidelines (ATAG) 2.0
http://www.w3.org/TR/ATAG20/
2. Implementation Techniques for ATAG 2.0
http://www.w3.org/TR/ATAG20-TECHS/
ATAG defines how authoring tools should help Web developers produce Web
content that is accessible and conforms to the Web Content Accessibility
Guidelines; it also defines how to make authoring tools accessible so that
people with disabilities can use the tools. ATAG is introduced in the ATAG
Overview at:
http://www.w3.org/WAI/intro/atag.php
ATAG is part of a series of accessibility guidelines/standards developed by
WAI, which are listed in
WAI Guidelines and Techniques at:
http://www.w3.org/WAI/guid-tech.html
WAI encourages you to review the update ATAG 2.0 documents and submit comments on any issues that you think could present a barrier to future adoption and implementation of ATAG 2.0. Please send comments by14 April 2008 to the comment list, which is publicly archived: public-atag2-comments@w3.org
For more information, see:
* How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
* Authoring Tool Accessibility Guidelines Working Group (AUWG)
http://www.w3.org/WAI/AU/
Note: Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Thank you in advance for your comments,
Jan Richards - Interim W3C Staff Contact for AUWG
Jutta Treviranus - Chair of AUWG, and Director of Adaptive Technology
Resource Centre, University of Toronto
Judy Brewer - Director, Web Accessibility Initiative, W3C
Shawn Lawton Henry - W3C WAI EOWG Chair
notes:
- want something like this? "AUWG believes that it has resolved all previous comments on ATAG 2.0. Therefore, AUWG expects that this ATAG 2.0 Working Draft is close to the form that it will take in an upcoming ATAG 2.0 second Last Call Working Draft. However, the possibility exists that issues arising from comments on this draft, and/or from dependencies with WCAG 2.0, may result in additional changes."
Blog Post:
[not doing]Interviews Nov 2007 - Feb 2008
WAI Highlight (for home page & RSS feed):
WAI Interviews: Shadi and Shawn Talk Web Accessibility
Recent interviews with Shadi Abou-Zahra and Shawn Lawton Henry are available online:
- Webtalk: Shadi Abou-Zahra über die Web Accessibility Initiative with Shadi is in German.
- Radio New Zealand Interview, February 2008 with Shawn is audio with a text transcript.
(2008-03-05)
WAI IG e-mail:
WAI Staff on Talk about Web Accessibility - Recent Interviews
[or: Interviews with WAI Staff on Web Accessibility or:...]
Dear WAI Interest Group Participants,
Two interviews with WAI staff were recently posted online that you might be interested in.
1. "Webtalk: Shadi Abou-Zahra über die Web
Accessibility Initiative" (in German). Shadi talks about his work at
WAI, benefits of WCAG 2.0, and the Web Accessibility Initiative: Ageing
Education and Harmonisation (WAI-AGE) project.
http://www.mainweb.at/blog/2007/11/22/webtalk-shadi-abou-zahra-ueber-die-web-accessibility-initiative
2. "Radio New Zealand Interview, February 2008" (audio and text
transcript). Shawn talks about the potential for the Web to enable people
with disabilites to more actively participate in everyday life; the work of
the W3C WAI; and including accessibility from the begining when developing
technology.
http://www.w3.org/WAI/highlights/200802radioNZ
For more WAI Highlights, see the WAI home page:
* http://www.w3.org/WAI/
To subscribe to the WAI RSS feed, see:
* http://www.w3.org/WAI/highlights/about-rss.html
Please feel free to circulate this message, avoiding cross-postings where possible.
References and acronyms:
* W3C=World Wide Web Consortium <http://www.w3.org/>
* WAI=Web Accessibility Initiative <http://www.w3.org/WAI/>
* WCAG=Web Content Accessibility Guidelines
<http://www.w3.org/WAI/intro/wcag.php>
* WAI-AGE Project <http://www.w3.org/WAI/WAI-AGE/
* Shadi About-Zahra <http://www.w3.org/People/shadi/>
* Shawn Lawton Henry <http://www.w3.org/People/Shawn/>
Regards,
Judy
...
notes
WCAG March 2008 Update
WAI Highlight (for home page & RSS feed):
March 2008 Update on WCAG 2.0
The WCAG Working Group has addressed most of the comments received on the second Last Call Working Draft of WCAG 2.0, and is currently finalizing replies to commenters and preparing for the "Candidate Recommendation" stage in the W3C Process. See: "March 2008 Update: Moving WCAG 2.0 to the next stage" in the WCAG 2 FAQ. (2008-03-05)
notes:
WAI IG e-mail:
March 2008 Update: Moving WCAG 2.0 to the next stage
WAI Interest Group Participants,
Here is an update on WCAG 2.0 work to let you know how things are coming along since the December 2007 second Last Call Working Draft publication.
As of the beginning of March 2008, the Working Group has resolved most of
the 200+ editorial and technical comments on the second Last Call Working
Draft of WCAG 2.0. The Working Group is currently finalizing resolutions to
comments and replies to commenters, and preparing for the next stage in the
W3C Process, "Candidate Recommendation", which is introduced in How WAI
Develops Accessibility Guidelines through the W3C Process at:
http://www.w3.org/WAI/intro/w3c-process
The WCAG Working Group anticipates publishing WCAG 2.0 as a "Candidate Recommendation" in April or May 2008. The focus will then be on collecting "implementation experience" from Web designers and developers using WCAG 2.0 in their Web projects. WAI will be providing information on testing WCAG 2.0 implementation and contributing your feedback.
Depending on the duration of the Candidate Recommendation stage, the final draft of WCAG 2.0 (called "Proposed Recommendation") could be available the third quarter of 2008.
For information on WCAG 2.0, see:
* Overview of WCAG 2.0 Documents
http://www.w3.org/WAI/intro/wcag20
* WCAG 2 FAQ
http://www.w3.org/WAI/WCAG20/wcag2faq
Regards,
~Shawn
notes:
W3C News Blurb:
[not doing]Blog Post:
[not doing]WAI ARIA 4 Feb 2008
W3C News Blurb:
WAI-ARIA for Accessible Rich Web Applications: First Public Working Drafts
2008-02-04: The Protocols and Formats Working Group published First Public Working Drafts of:
- Accessible Rich Internet Applications (WAI-ARIA) Version 1.0 combines the two previously-published ARIA draft specifications: WAI-ARIA Roles, and WAI-ARIA States and Properties.
- WAI-ARIA Primer provides background on accessibility issues related to JavaScript, and introduces the technical approach used in WAI-ARIA.
- WAI-ARIA Best Practices describes how Web content developers can develop accessible rich Web applications using WAI-ARIA.
WAI-ARIA defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies. An updated WAI-ARIA Roadmap was also published.
Additionally, the Education and Outreach Working Group published a new WAI-ARIA FAQ and updated WAI-ARIA Overview. Read the Call for Review: New WAI-ARIA Documents announcement and about the Web Accessibility Initiative.
notes:
- previous blurb
2007-10-19 included:
- WAI-ARIA includes technologies to map controls, Ajax live regions, and events to accessibility APIs, including custom controls used for rich Internet applications. It also describes new navigation techniques to mark common Web structures as menus, primary content, secondary content, banner information and other types of Web structures.
- Implementation of WAI-ARIA in languages such as HTML 4, HTML 5 and XHTML is in active development.
WAI Highlight (for home page & RSS feed):
For Review: New WAI-ARIA Resources
WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies.
New WAI-ARIA documents were published 4 February 2008. The WAI-ARIA Primer provides background on accessibility issues related to JavaScript, and introduces the technical approach used in WAI-ARIA. WAI-ARIA Best Practices describes how Web content developers can develop accessible rich Web applications using WAI-ARIA. See:
- Call for Review: New WAI-ARIA Documents announcement e-mail;
- WAI-ARIA Overview which links to WAI-ARIA itself and the other documents;
- WAI-ARIA FAQ.
We welcome your comments, preferably by 20 February, otherwise by 3 March 2008. (2008-02-04)
heading brainstorms:
- For Review: New WAI-ARIA Documents
WAI IG e-mail:
Call for Review: New WAI-ARIA Documents
The Protocols and Formats Working Group invites you to comment on the
following documents published 4 February 2008:
1. Accessible Rich Internet Applications (WAI-ARIA) Version 1.0 - a technical
specification that combines the two previously-published ARIA draft
specifications: WAI-ARIA Roles, and WAI-ARIA States and Properties
http://www.w3.org/TR/wai-aria/
2. WAI-ARIA Primer - a new document that provides background on accessibility
issues related to JavaScript, and introduces the technical approach used in
WAI-ARIA
http://www.w3.org/TR/wai-aria-primer/
3. WAI-ARIA Best Practices - a new document that describes how Web content
developers can develop accessible rich Web applications using WAI-ARIA
http://www.w3.org/TR/wai-aria-practices/
WAI-ARIA, the Accessible Rich Internet Applications Suite, defines a way to make Web content and Web applications more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax (also known as AJAX), HTML, JavaScript, and related technologies.
For an introduction to WAI-ARIA and the problems that it addresses, as
well as changes to the WAI-ARIA Suite documents, please see the following
updated documents:
* WAI-ARIA Overview
http://www.w3.org/WAI/intro/aria
* WAI-ARIA FAQ
http://www.w3.org/WAI/aria/faq
* Roadmap for Accessible Rich Internet Applications (WAI-ARIA Roadmap)
http://www.w3.org/TR/wai-aria-roadmap/
There are specific review questions in the "Status" section of each of the
technical documents. Please send any comments on these documents to
public-pfwg-comments@w3.org
The comment period ends 3 March 2008. The Protocols and Formats Working Group
is meeting face-to-face the week of 18 February to work on the technical
documents. Therefore, if possible, please send comments before *20 February
2008*.
For more information, see:
* Protocols and Formats Working Group
http://www.w3.org/WAI/PF/
* How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
Note: Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Thank you in advance for your comments,
Michael Cooper - W3C Team Contact for PFWG
Al Gilman - Chair of PFWG
Judy Brewer - Director of Web Accessibility Initiative, W3C
Shawn Lawton Henry - W3C WAI EOWG Chair
W3C Q&A Blog Post:
New resources on making Ajax and related technologies accessible
Dateline Monday 4 February 2008: WAI publishes new WAI-ARIA documents for developers, and new overview material for everyone.
For the last two years or so, the W3C Web Accessibility (WAI) has been working on technical specifications to support making rich Web applications and sites designed with Ajax (also known as AJAX) and related technologies accessible to people with disabilities. The work has focused on defining technologies to map controls, Ajax live regions, and events to accessibility APIs, including custom controls; as well as describing new navigation techniques by marking common Web structures as menus, primary content, secondary content, banner information and other types of Web structures.
A particularly exciting aspect of this "WAI-ARIA" (Accessible Rich Internet Application Suite) work has been its early implementation in browsers and screen readers. Yet until now there hasn't been much guidance for web content developers/authors on what to do with WAI-ARIA (because the Working Group was focusing first on the specification).
Today WAI published documents that help Web content developers know how to use WAI-ARIA to develop accessible rich Web applications, including WAI-ARIA Primer and WAI-ARIA Best Practices. We also posted a WAI-ARIA FAQ that answers questions such as "As a Web developer, what should I do with WAI-ARIA now?" We welcome input on these documents.
Development of WAI-ARIA continues at a relatively fast pace, and "Last Call" Working Drafts could be published in the next few months. Now is the time for your input. In fact, the Working Group is meeting face-to-face the week of 18 February to address open issues and any new comments.
For links to and more details on these new documents, see the Call for Review: New WAI-ARIA Documents announcement e-mail and the WAI-ARIA Overview. Please let us know how these new resources work for you and how we can improve them.
notes:
- ...
Mobile-Accessible Overlap
W3C News Blurb:
Relationship Between Mobile Web and Web Content Accessibility (First Public Working Draft)
The Mobile Web Best Practices Working Group and the WAI Education and Outreach Working Group have published the First Public Working Draft of Relationship Between Mobile Web Best Practices 1.0 and Web Content Accessibility Guidelines. See the announcement email.
The groups encourage people to first read Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices, which introduces the overlap between design goals and guidelines. Experiences Shared by People with Disabilities and by People Using Mobile Devices provides examples of barriers that people (without disabilities) have when interacting with Web content via mobile devices, and similar barriers for people with disabilities using desktop computers. Learn more about the Mobile Web Initiative and the Web Accessibility Initiative (WAI).
notes:
- The Mobile Web Best
Practices Working Group and the WAI Education and Outreach
Working Group have published documents describing the overlap between
accessibility guidelines for people with disabilities and best practices
for mobile devices:
- Relationship Between Mobile Web Best Practices 1.0 and Web Content Accessibility Guidelines First Public Working Draft,
- Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices introductory document, and
- Experiences Shared by People with Disabilities and by People Using Mobile Devices.
See the announcement email. Learn more about the Mobile Web Initiative and the Web Accessibility Initiative (WAI).
- The Mobile Web Best Practices Working Group and the WAI Education and Outreach Working Group have published the First Public Working Draft of Relationship Between Mobile Web Best Practices 1.0 and Web Content Accessibility Guidelines, along with the introductory document Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices and Experiences Shared by People with Disabilities and by People Using Mobile Devices. These documents describe the overlap between design goals and guidelines covering accessibility for people with disabilities and for mobile devices. See the announcement email. Learn more about the Mobile Web Initiative and the Web Accessibility Initiative (WAI).
- maybe take out the Experiences Shared by People with Disabilities and by People Using Mobile Devices to simplify it - if can't use a list
- These documents describe the overlap between design goals and guidelines covering accessibility for people with disabilities and for mobile devices.
WAI Hightlight (for home page & RSS feed):
Accessible and Mobile: Two Birds with One Stone
Web sites can be designed more efficiently to be accessible for people with disabilities and also for people using mobile devices when developers understand the significant overlap between the two design goals and guidelines. On 22 January, W3C published material describing this overlap. See:
- First Public Working Draft: Relationship Between Mobile Web and Web Content Accessibility announcement e-mail;
- Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices introductory page;
- Relationship Between Mobile Web Best Practices 1.0 and Web Content Accessibility Guidelines First Public Working Draft.
We welcome your comments, preferrably by 3 March 2008. (2008-01-22)
heading brainstorms:
- Accessible and Mobile: Two Birds with One Stone
- Accessible and Mobile: Do them both easier
- Accessible and Mobile: Understanding the Overlap
- Accessible and Mobile: Buy One, Get One Free
- Accessible and Mobile: Do One, Get One Free
- Accessible and Mobile: Two-for-One Deal
- Synergy...
- Relationship Between Mobile Web and Web Content Accessibility: First Public Working Draft
WAI IG e-mail:
The Mobile Web Best Practices Working Group and the WAI Education and Outreach
Working Group invite you to comment on the following documents published 22
January 2008:
1. Web Content Accessibility and Mobile Web: Making a Web Site Accessible
Both for People with Disabilities and for Mobile Devices, an introductory
page
http://www.w3.org/WAI/mobile/
2. Experiences Shared by People with Disabilities and by People Using Mobile
Devices [Draft]
http://www.w3.org/WAI/mobile/experiences
3. Relationship Between Mobile Web Best Practices 1.0 and Web Content
Accessibility Guidelines, First Public Working Draft
http://www.w3.org/TR/mwbp-wcag
These documents describe the overlap between design goals and guidelines covering accessibility for people with disabilities, and design goals and best practices for mobile devices.
The draft documents provide a framework for the community to discuss and contribute to this work. Note that in some places there is draft content and in other places there is only a rough outline of potential content.
Please send any comments on these documents to public-bpwg@w3.org
If possible, please send comments by 3 March 2008.
For more information, see:
* Mobile Web Best Practices Working Group
http://www.w3.org/2005/MWI/BPWG/
* Web Accessibility Initiave
(WAI) Education and Outreach Working Group
http://www.w3.org/WAI/EO/
* How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
Note: Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Thank you in advance for your comments,
Shawn Lawton Henry, WAI EOWG Chair
Daniel Appelquist, MWI BPWG Co-Chair
Jo Rabin, MWI BPWG Co-Chair
MWI BPWG Blog Post:
Mobile, and Accessible to People with Disabilities
... @@...
notes:
- Accessibility advocates have been saying for years that making your Web site accessible to people with disabilities makes it more usable for others, including people using mobile devices. Now W3C is documenting that.
WCAG 2.0 Last Call
WAI Highlight for home page & RSS feed:
FINAL VERSION at http://www.w3.org/WAI/highlights/archive#x20071211a
For Review: WCAG 2.0 Last Call Working Draft
A Web Content Accessibility Guidelines 2.0 (WCAG 2.0) second Last Call Working Draft and updated supporting documents were published 11 December 2007. This Last Call is provided for public review of the document with all resolutions from previous comments incorporated. See:
Please send comments by 1 February 2008. (2007-12-11)
W3C Home Page (and NewsWire and Member Newsletter):
Last Call: Web Content Accessibility Guidelines (WCAG) 2.0 Working Draft
2007-12-11: The Web Content Accessibility Guidelines (WCAG) Working Group has released a second Last Call Working Draft of Web Content Accessibility Guidelines 2.0, and Working Drafts of Understanding WCAG 2.0 and Techniques for WCAG 2.0. Following WCAG makes Web content more accessible to the vast majority of users, including people with disabilities and older users, using many different devices including a wide variety of assistive technologies. Comments are requested by 1 February 2008. Read the WCAG Overview, Call for Review, and about the Web Accessibility Initiative.
(note: designed to be highlighly skimmable :)
Call for Review: WCAG 2.0 Last Call Working Draft
Dear WAI Interest Group Participants,
The Web Content Accessibility Guidelines (WCAG) Working Group invites you
to review the second WCAG 2.0 Last Call Working Draft published on 11
December 2007. WCAG 2.0 explains how to make Web sites, applications, and
other content accessible to people with disabilities. Please submit any
comments on the following document by 1 February 2008:
http://www.w3.org/TR/2007/WD-WCAG20-20071211/
This second WCAG 2.0 Last Call Working Draft is provided for public review
of the document now that it has all resolutions from previous comments
incorporated. The WCAG Working Group hopes that it has resolved all
substantive issues with this draft, and looks forward to progressing to the
next stages in completing WCAG 2.0. The next stages are described in:
How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
The different WCAG 2.0 documents that the WCAG Working Group updated are
introduced in:
Overview of Web Content Accessibility Guidelines (WCAG) 2.0 Documents
http://www.w3.org/WAI/intro/wcag20.php
A key tool for reviewing and working with WCAG 2.0 documents is:
WCAG 2.0 Quick Reference
http://www.w3.org/WAI/WCAG20/quickref/
For a summary of issues, revisions, and rationales on WCAG 2.0 Working
Drafts--such as coverage of cognitive disabilities and testability--see:
Issues and Changes to WCAG 2.0
http://www.w3.org/WAI/GL/2007/12/change-summary
Note that the navigation between the documents is changed in these drafts. Now each topic in "Understanding WCAG 2.0" and "Techniques for WCAG 2.0" is in a separate small Web page.
When you review the updated documents, if there are any significant
additional issues that you feel could present a barrier to adoption and
implementation of WCAG 2.0, please submit comments by:
Friday 1 February 2008
Please use the comment form or the email address provided in:
Instructions for Commenting on WCAG 2.0 Documents
http://www.w3.org/WAI/WCAG20/comments/
Comments in support of progressing WCAG 2.0 to the next stages are also
welcome.
WCAG 2.0 is part of a series of accessibility guidelines/standards
developed by WAI, which are listed in:
WAI Guidelines and Techniques
http://www.w3.org/WAI/guid-tech.html
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Please let us know if you have any questions. Thank you in advance for your review of WCAG 2.0 documents.
Regards,
~Shawn Henry and Judy Brewer
On behalf of:
Loretta Guarino Reid, Co-chair of WCAG WG, and Computer Scientist, Google
Inc.
Gregg Vanderheiden, Co-chair of WCAG WG, and Director of Trace R&D
Center, University of Wisconsin-Madison
Michael Cooper, W3C Team Contact for WCAG WG
W3C Q&A blog post:
last updated $Date: 2009/06/26 00:29:54 $
NOTE: This information is an unapproved draft and should not be referenced or quoted under any circumstances. Thank you.
Is WCAG 2.0 almost done?!
A Last Call Working Draft of WCAG 2.0 was just published. This means that the WCAG Working Group has integrated all resolutions from previous comments. Yeah! Now the question is whether this draft of WCAG 2.0 is ready for the community to support moving it on towards becoming a Web standard (W3C Recommendation)?
I've watched WCAG 2.0's development over the last 7 years (first from outside W3C and then from inside W3C). Hundreds of people have contributed, critiqued, and debated WCAG 2.0 from a broad range of perspectives — individual web developers, large organizations, people with disabilities, and many more. The dedication and struggles of the WCAG Working Group and the thoughtful input from the community has resulted in a strong second Last Call Working Draft that has reached a mature state (and I think everyone will agree is vastly improved from the first Last Call in April 2006!).
It's inherent in the complex issues of web accessibility that guidelines will not be perfect and not everyone will be fully satisfied. So when do you say WCAG 2.0 is good enough? The WCAG Working Group has provided their proposal with this Last Call Working Draft.
I think we've come to the point now where the question should be: Is it better for web accessibility overall for the community to continue to debate, or is it better to polish and accept WCAG 2.0? ...I say, onward. And I hope that the community can also soon say go forward with WCAG 2.0 (and continue to refine the companion material linked below).
WCAG 1.0 has provided a vital international standard. Yet WCAG 2.0 is urgently needed to address current and future technologies and situations.
One of the beauties of the WCAG 2.0 documents is its ability to provide both a stable standard and specific guidance for techniques, technologies, and tools as they advance. WCAG 2.0 itself provides the stable standard, a foundation that doesn't change; Techniques for WCAG 2.0 and Understanding WCAG 2.0 can be updated periodically, for example, to expand the techniques and advice covering accessibility for people with cognitive disabilities.
To those interested in the development of WCAG 2.0, I ask if you would carefully consider your approach to reviewing and commenting on these latest Working Drafts, and think about how your feedback can best advance web accessibility overall. Consider supporting efforts to complete WCAG 2.0.
Now I'm off to review how the WCAG Working Group responded to my previous comments, prepared to accept good enough in the interest of moving forward...
By Shawn Henry
NOTE: This information is an unapproved draft and should not be referenced or quoted under any circumstances.
For Review: UAAG 2.0 Requirements
User Agent Accessibility Guidelines (UAAG) provides guidance on designing Web browsers, media players, assistive technologies, and other 'user agents' to increase accessibility of the Web to people with disabilities. Plans for new work on a second generation of UAAG was published in the UAAG 2.0 Requirements, Working Draft on 31 October 2007. WAI encourages you to review this document, submit any comments, and consider participating in the UAAG Working Group. See:
- Call for Review: UAAG 2.0 Requirements;
- UAAG Overview;
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
Please send comments by 14 December 2007. (2007-10-31)
W3C News Blurb:
UAAG 2.0 Requirements: Working Draft
2007-10-31: The User Agent Accessibility Guidelines (UAAG) Working Group has released a first Working Draft of User Agent Accessibility Guidelines 2.0 Requirements, which defines planned new work on the second generation of UAAG. UAAG provides guidance on designing Web browsers, media players, assistive technologies, and other 'user agents' to be accessible and to increase accessibility of Web content for people with disabilities. UAAG is part of a series of accessibility guidelines described in Essential Components of Web Accessibility. Read the UAAG Overview and about WAI.
notes:
- The User Agent Accessibility Guidelines (UAAG) documents explain how to make user agents accessible to people with disabilities, particularly to increase accessibility to Web content. User agents include Web browsers, media players, and assistive technologies, which are software that some people with disabilities use in interacting with computers.
- provides guidelines for designing user agents (browsers) that lower barriers to Web accessibility for people with disabilities
- initial thoughts:
- this is about accessibility of browsers & media players
- and interoperability w/ assistive technologies
- it updates technical coverage from UAAG 1.0
- will be part of WAI Guidelines 2.0
- inviting comment and participation
- good time to get us your comments
- we need different perspectives
- This requirements document introduces planned new work on a second generation of guidelines for browser and media player accessibility.
Pass It On: WCAG 2.0 Presentation Materials
"About WCAG 2.0 Web Content Accessibility Guidelines" is a presentation that covers the benefits of WCAG 2.0, shortcuts for using WCAG 2.0, how it differs from WCAG 1.0, and related topics. The presentation "slides" and extensive notes are designed for presenters to use for their own presentations. It is also available for anyone who wants to learn about WCAG 2.0. See Instructions for the "About WCAG 2.0" Presentation. (2007-10-31)
Headline brainstorms:
- Presentation Materials: Tell the World About WCAG 2.0
- Presentation Materials: Spread the Word About WCAG 2.0
- Presentation Materials: Spreading the Word About WCAG 2.0
- Presentation Materials: All About WCAG 2.0
- Presentation Materials: About WCAG 2.0
- Presentation Template: About WCAG 2.0
- WCAG 2.0 Presentation Materials
body brainstorms:
- perhaps delete this sentence: "It is also available for anyone who wants to learn about WCAG 2.0. See Instructions for the "About WCAG 2.0" Presentation." - because that's kinda obvious and not worth taking space in a highlight?
October 2007 Update on WCAG 2.0
The WCAG Working Group is completing resolution of comments on the latest WCAG 2.0 Public Working Draft documents. In November 2007 they plan to send responses on each comment, asking for reply from the reviewer. The Working group plans to publish a second WCAG 2.0 Last Call Working Draft in December 2007, before moving on to the next stages. See:
- WCAG 2 FAQ;
- WCAG 2.0 Overview;
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
For Review: Updated WAI-ARIA Working Drafts
W3C WAI's work on accessibility of Ajax, DHTML, and other application technologies includes the Accessible Rich Internet Applications Suite (WAI-ARIA). Updated Working Drafts of the WAI-ARIA documents were published 18 October 2007. A Best Practices Guide for web developers will be published in a few months. See:
- Call for Review: WAI-ARIA updated Working Drafts[@@LINK];
- WAI-ARIA Suite Overview;
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
Please send comments by @@ 2007. (2007-10-18)
Mitsue-Links interview & Yahoo presentation
Previous interview blurbs:
WaSP Interview: Judy Brewer on WCAG 2
Judy Brewer discusses WCAG 2.0 status and upcoming drafts with Web Standards Project (WaSP) Accessibility Task Force member Jared Smith. See Interview with Judy Brewer. (2007-05-07)
Podcast: Interview on WCAG 2Shawn Henry discusses WCAG 2.0 with UK UPA president Giles Colborne: transcript and audio files. (2006-07-06)
A Video Interview with Shawn Henry, From California to Japan
As part of the Mitsue-Links "Meet the Professionals" video series, Shawn Henry of W3C WAI talks with Kazuhito Kidachi about shared responsibilities between web site developers, browsers, and assistive technologies; the importance of different types of authoring tools supporting accessibility; how WCAG 2.0 and WAI-ARIA address the more difficult aspects of Web accessibility; WAI's outreach resources; and what led Shawn to accessibility years ago. See video with English audio and Japanese subtitles, and text transcripts. (2007-07-11)
title brainstorms:
- From California to Japan: A Video Interview with Shawn Henry
- A Video Interview with Shawn Henry (on much
more than WCAG 2.0)
Yes, there's more to talk about than WCAG 2.0: A Video Interview with Shawn Henry
Video Interview with Shawn Henry (Yes, there's more to talk about than WCAG 2.0)
Video Interview: Shawn Henry on Web Accessibility other than WCAG 2.0
Almost no WCAG 2.0: Video Interview with Shawn Henry - Video Interview: Shawn Henry on Web Accessibility
- [note: the company is Japanese, but the actual interview was conducted in the US]
- Video Interview: WAI Reaches Out from Japan
- Outreach from Japan: Video Interview with Shawn Henry on Web Accessibility
- Dateline Japan: Shawn Henry Talks about Web Accessibility
Worldwide
Dateline Japan: Shawn Henry Talks about Web Accessibility around the World
Dateline Japan: Shawn Henry Talks about the World of Web Accessibility
- Finding your WAI: The World of Web Accessibility
Finding your WAI: The World of Web Accessibility according to Shawn - Shawn Henry Talks Web Accessibility from Japan
- Meet the Professionals, Japan: Shawn Henry Talks about Web Accessibility
- Video Interview: Shawn Henry in Meet the Professionals
Video Interview: Shawn Henry Discusses ?
Video Interview: Shawn Henry Finds the WAI in Japan - Shawn Henry provides perspectives from Japan
body brainstorms:
- shadi: "how to implement accessibility effectively" = "fix simple things first", "working together", and "importance of authoring tools" were really important to me. They gave high-level advice on "what do i need to do" (more for decision maker than developers actually, but that's the good thing).
- ... Filmed at a technology and disability conference in California, the video is available with English audio and Japanese subtitles, and text transcripts.
- [version went over with Judy] Shawn Henry of W3C WAI talks
about shared responsibilities between web site developers, browsers, and
assistive technologies; the importance of different types of authoring
tools supporting accessibility; how WCAG 2.0 and WAI-ARIA address the
more difficult aspects of Web accessibility; and WAI's outreach
resources. As part of the
Mitsue-Links @@??start with??"Meet the Professionals" video series with Kazuhito Kidachi, Shawn also tells what led her to accessibility, and her hopes for designers and developers around the world. See video with English audio and Japanese subtitles, and text transcriptsin English and Japanese. (2007-07-11) - [previous one that Shadi commented on] What is the current state of web accessibility around the world? What is your opinion about the relationship between Web content and browsers? What is the most difficult accessibility challenge today in the "Web 2.0 era"? Get answers to these questions and more in a video interview (in English and Japanese) with Kazuhito Kidachi of Mitsue-Links.
- [with title "Video Interview: WAI Reaches Out from Japan"] Shawn Henry discussed Web accessibility issues with Kazuhito Kidachi of Mitsue-Links, including W3C WAI's education and outreach activities, accessibility issues around the world, and the role of browsers and authoring tools. See video with English audio and Japanese subtitles, and text transcripts in English and Japanese.
- ... for Mitsue-Links' "Meet the Professionals" video series... how Shawn got into Web accessibility and her hopes for designers and developers around the world.
NOTE: perhaps different framing for Keio -- more formal, more text. (100-150 words)
questions/topics (questions in email):
- my background
- WAI education & outreach
- accessibility around the world
- accessibility of browsers & authoring tools
- responsibilities between content & browsers
- difficult challenges in accesibility today, & solutions
- my hope for designers/developers around the world
Now Showing at the YUI Theater: WCAG 2.0 Presentation
Learn how the WCAG 2.0 Working Draft differs from WCAG 1.0, get shortcuts for using WCAG 2.0, and hear answers to common questions on W3C WAI's work in Shawn Henry's presentation to the Yahoo! Developer Network. Shawn also addresses the role of browsers and authoring tools in Web accessibility, and combining standards and usability techniques to optimize accessibility. See video with audio, slides, and text transcript. (2007-08-09)
title brainstorms:
- Now Showing at the YUI Theater: Web Accessibility Guidelines Update
- Now Showing at the YUI Theater: WCAG 2.0
Now Showing at the YUI Theater: WCAG 2.0 Presentation
WCAG 2.0 Presentation: YUI Theater - From the London Tour June 2007
WCAG 2.0 Presentation, From the June 2007 London Tour
WCAG 2.0 Presentation, From the London Tour, June 2007
From the London Tour, June 2007: WCAG 2.0 Presentation
From the London Tour: WCAG 2.0 Presentation, June 2007
From the London Tour: June 2007 Presentation on WCAG 2.0
June 2007 London Tour: WAI Update - Get the Scoop: WCAG 2.0 Presentation
- [Video] Presentation [Online]: [WAI] [Web] Accessibility Guidelines Update
- [Video] Presentation [Online]: Update on [WAI] [Web] Accessibility Guidelines
- Live from London:... Can You Handle the Truth...WCAG 2.0 Today: June 2007... June 2007: Where We are with WCAG 2.0... Find the Facts: WCAG 2.0... From the Horse's Mouth... All in an Hour... Get the Real Deal...WAI Speaks Out
- Mythbusters: WCAG 2.0 Edition -- save for something that more directly addresses myths... although it's not done well so might not want to be assocaited with it
body brainstorms:
- previous: Learn how the WCAG 2.0 Working Draft differs from WCAG 1.0, get shortcuts for using WCAG 2.0, and hear answers to common questions on W3C WAI's work in Shawn Henry's presentation to the Yahoo! UI Developers Network. Shawn also addresses the role of browsers and authoring tools in Web accessibility, and combining standards and usability techniques to optimize accessibility. See Yahoo UI video with audio, slides, and text transcript. (2007-07-13)
- [for From the London Tour, June 2007: WCAG 2.0] ... as part of an outreach tour that included a free session organized by RNIB, and @media conferences...
- ... and covering Web accessibility from both the users' perspectives and the standards perspective.
- ... and approaching Web accessibility to cover both the users' perspectives and the standards.
- ... and approaches to Web accessibility covering both the users' perspectives and the standards.
- ... and combining the usability approach and standards approach to accessibility.
- ... and combining standards and usability techniques for accessibility.
- ... and combining standards and usability techniques to optimize the user experience for people with disabilities.
- ... and how to approach to Web accessibility from both users' perspectives and standards perspective.
- Shawn Henry provides an update on W3C WAI's Web Accessibility Guidelines in a video presentation. She explains differences between WCAG 1.0 and WCAG 2.0 Working Draft, provides shortcuts for using WCAG 2.0, clarifies some misunderstandings, and answers several questions. She also addresses the role of browsers and authoring tools in Web accessibility, and guidelines for each. See Yahoo UI video and text transcript .
- Learn how the WCAG 2.0 Working Draft differs from WCAG 1.0, get shortcuts for using WCAG 2.0, and hear answers to common questions on W3C WAI's work. It's all in Shawn Henry's presentation to the Yahoo! UI Developers Network in London. Shawn also addresses the role of browsers and authoring tools in Web accessibility, and how different approaches to Web accessibility work together. See Yahoo UI video and text transcript.
- Learn differences between WCAG 1.0 and WCAG 2.0 Working Draft, get shortcuts for using WCAG 2.0, and hear answers to common questions in a presentation by W3C WAI's Shawn Henry to the Yahoo! UI Developers Network in London. Shawn also addresses the role of browsers and authoring tools in Web accessibility, and how different guidelines and approaches work together for Web accessibility. See Yahoo UI video and text transcript .
- unofficial draft of the video note: final will also have audio & video of slides, but no video of me per se. note: might also want to give a nod to the RNIB session, which is audio only
- comments:
Judy: - Not wild about the "...from the London Tour"; might sound hifalutin to some people. - Also the syntax seems a bit off at "Shawn also addresses..., and combining standards..." The verbs don't agree. You *could* say: "...and how to combine standards and usability techniques to optimize accessibility." - Description of linked resources is better now.
Shadi: Agree with Judy. Also not sure if the location, "London", is important this time. Actually, having "Yahoo! UI" in the title may be more relevant in this particular case.
summary of content (slides in powerpoint):
- Process 101
- Role of guidelines & standards in developing accessible content
- WCAG 2.0: difference with WCAG 1.0, testability, more flexible, scripting, wai-aria, techniques, understanding, Quick Ref
- browser (user agent) accessibility
- authoring tool accessibility, actively encourage improvements
July 2007 Update on WCAG 2.0
The WCAG Working Group received many constructive comments on the 17 May 2007 Drafts. They separated the comments into about 450 issues, ranging from minor edits to technical issues. In the first two weeks of July, the Working Group had eight half-day worksessions where they addressed about 150 of those issues and started work on another 100. See the "Update July 2007" section of the WCAG 2 FAQ for more...
(2007-07-27)
title brainstorms:
- WCAG 2.0 Udate: July 2007
- 150 down, 300 to go: WCAG 2.0 Update
body brainstorms:
- The WCAG Working Group received many
constructive comments
on the 17 May 2007 Drafts. They separated the comments into about 450
issues, ranging from minor edits to technical issues. In the first two
weeks of July, the Working Group had eight half-day worksessions in which
they addressed about 150 of those issues and started work on another 100.
It will likely take 3 to 4 months to address all of the issues and
prepare the next draft.
The Working Group will respond to each comment. Once the comments have been addressed, the Working Group plans to publish a second WCAG 2.0 Last Call Working Draft to provide for review of the completed edits before moving on to the next stages. The next stages are described in How WAI Develops Accessibility Guidelines through the W3C Process.
See also: WCAG 2 FAQ.
For Review: Updated WAI-ARIA Working Drafts
W3C WAI's work on accessibility of AJAX, DHTML, and other application technologies includes the Accessibility for Rich Internet Applications (WAI-ARIA) Suite. Updated Working Drafts of the WAI-ARIA Suite documents were published @@ Month 2007. WAI encourages you to review these documents and submit any comments. See:
- Call for Review: Updated Accessible Rich Internet Applications (WAI-ARIA) Working Drafts e-mail; @@link
- WAI-ARIA Suite Overview;
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
Please send comments by @@ Month 2007. (2007-@@-@@)
For Review: Updated WCAG 2.0 Documents
Updated Web Content Accessibility Guidelines 2.0 (WCAG 2.0) Working Draft documents were published 17 May 2007. These documents incorporate resolutions to comments from the 2006 Last Call Working Draft. WAI encourages you to review these drafts and submit any new comments. Please see the additional information in:
- Call for Review: Updated WCAG 2.0 Documents [@@update link to IG email]
- Overview of WCAG 2.0 Documents
- WCAG 2 FAQ
Please send comments by 29 June 2007. (2007-05-17)
body ideas:
Handouts & WCAG 2 update
Updates: WCAG 2.0 and WAI Resources Handouts
WCAG 2.0 primary points, current status, and Web accessibility resources from W3C WAI are topics covered in new handouts that you can use for conferences and presentations. The handouts direct readers to the updated WCAG 2 FAQ, How WAI Develops Accessibility Guidelines through the W3C Process, and other documents. See:
- Updates: WCAG 2.0 and WAI Resources Handouts e-mail [@@link to WAI IG msg]
- WAI Handouts and WAI Flyer page
title brainstorms:
- Updates: WCAG 2.0 and WAI Resources Handouts
- Spreading the Word: WCAG Handout
- Handouts Update WCAG 2.0
- Sha
body brainstorms:
- WCAG 2.0 Primary Points, WCAG 2.0 Current Status, and Web Accessibility
Resources from W3C WAI are topics covered in handouts that can be used
for conferences and presentations. The handouts direct readers to the
WCAG 2 FAQ, with March 2007 updates, How WAI Develops
Accessibility Guidelines through the W3C Process: Milestones and
Opportunities to Contribute, and other documents. See:
- @@WAI IG e-mail
- WAI Flyer and Handouts
NOTE DONE: Update on WCAG 2.0 & Handouts
WCAG 2.0 @@
The Web Content Accessibility Guidelines (WCAG) Working Group has addressed most of the 900 comments from the last review and plans to provide updated Public Working Drafts of WCAG 2.0 documents in late April or May 2007. Please see the WCAG 2 FAQ "Update March 2007" sections and the new WCAG 2.0 handout. (2007-04-04)
title brainstorms:
- Sneak Peak... Around the Corner...
- WCAG 2.0 Comments: 800 Down, 100 To Go
- Update: 800 Down, 100 To Go
(WCAG 2.0 Comments Addressed|Resolved) - Update: WCAG 2.0 Comments Almost Done
- Update: WCAG 2.0 Working Group Working
- Update: WCAG 2.0 Working Group Work
- Update on WCAG 2.0 Work
- Update: WCAG 2.0 Publication Plans
- News Flash: WCAG 2.0 Publication Plans
- Coming Soon: WCAG 2.0 Publication Plans
- More WCAG 2 F.A.Q. Info
- WCAG 2 FAQ Update
- What's News with WCAG 2
body brainstorms:
- The Web Content Accessibility Guidelines (WCAG) Working Group has addressed most of the 900 comments from the last review. We plan to provide updated Public Working Drafts of WCAG 2.0 documents in late April or May 2007. Please see the WCAG 2 FAQ "Update March 2007" sections and the new WCAG 2.0 handout. (2007-04-04)
- The Web Content Accessibility Guidelines (WCAG) Working Group plans to provide|publish updated Public Working Drafts of WCAG 2.0 documents in late April or May 2007. Please see the WCAG 2 FAQ "Update March 2007" sections and the new WCAG 2.0 handout for details|more information. (2007-04-04)
- The Web Content Accessibility Guidelines (WCAG) Working Group has addressed most of the 900 comments from the last review and plans to provide updated Public Working Drafts of WCAG 2.0 documents in late April or May 2007. Please see the WCAG 2 FAQ "Update March 2007" sections and the new WCAG 2.0 handout. (2007-04-04)
For Review: EARL 1.0 Schema Last Call Working Draft
Evaluation and Report Language (EARL) is a format to exchange, combine, and analyze results from different evaluation tools and checkers. EARL 1.0 Schema Last Call Working Draft and HTTP Vocabulary in RDF Working Draft were published 23 March 2007. See:
- Last Call Review: EARL 1.0 Schema Last Call Working Draft
- Evaluation and Report Language (EARL) Overview,
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
Please send comments by 20 April 2007. (2007-03-23)
First Authorized Translation: WCAG 1.0 in Catalan
The W3C Authorized Catalan Translation of the Web Content Accessibility Guidelines (WCAG) 1.0 is now available. See:
- Directrius per a l'accessibilitat al contingut web, versió 1.0. (Web Content Accessibility Guidelines 1.0)
- Web Content Accessibility Guidelines (WCAG) Overview
- Policy for W3C Authorized Translations
This WCAG 1.0 Catalan translation is W3C's first Authorized Translation. (2006-12-19)
Heading brainstorms:
- W3C's First Authorized Translation: WCAG 1.0 in Catalan
- Authorized: WCAG 1.0 Catalan Translation
- Authorized: Catalan Translation of WCAG 1.0
- [deleted "It's Official:"
W3C planned announcment:
Authorized Translation of the Web Content Accessibility Guidelines in Catalan
2006-12-18: Today the World Web Consortium released the Authorized Catalan Translation of the Web Content Accessibility Guidelines (WCAG) 1.0. The Leading Translation Organization for this Authorized Translation was the Facultat de Biblioteconomia i Documentació - Universitat de Barcelona. Visit the Web Accessibility Initiative home page and the Policy of W3C Authorized Translations.
For Review: Updated WAI-ARIA Working Drafts
W3C WAI's work on accessibility of AJAX, DHTML, and other application technologies includes the Accessibility for Rich Internet Applications (WAI-ARIA) Suite. Updated Working Drafts of the WAI-ARIA Suite documents were published 20 December 2006. WAI encourages you to review these documents and submit any comments. See:
- WAI-ARIA Suite Overview, a new document
- Call for Review: Updated Accessible Rich Internet Applications (WAI-ARIA) Working Drafts e-mail
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute
Please send comments by 19 January 2006. (2006-12-20)
For Review: ATAG 2.0 Working Draft
An updated Authoring Tool Accessibility Guidelines (ATAG) 2.0 Working Draft was published 7 December 2006. WAI encourages you to review this document and submit any comments. See:
- Call for Review: ATAG 2.0 Working Draft - explains that this draft is complete and ready for Last Call
- Authoring Tool Accessibility Guidelines (ATAG) Overview - describes different types of authoring tools
- Essential Components of Web Accessibility - explains how ATAG relates to the other WAI guidelines
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute
Please send comments by 11 January 2007. (2006-12-07)
WCAG 2 FAQ
Got Questions? View the New WCAG 2 F.A.Q.
WAI gathered a few frequent asked questions (FAQ) about Web Content Accessibility Guidelines (WCAG) 2.0 and provided answers in WCAG 2 FAQ. There we address: When will WCAG 2.0 be done? What is the current status? When should I start using WCAG 2.0? (2006-11-01)
title brainstorms:
- WCAG 2 FAQ Live
- Got Questions? See the New WCAG 2 FAQ.
- Got Questions? Check the WCAG 2 FAQ.
- Got a Question About WCAG 2? Lookie Here
- Get a Clue: View the New WCAG 2 FAQ
- Your Questions on WCAG 2.0 Answered
- WCAG 2.0 Q&A: You Asked, We Answered
- WCAG 2.0 Q&A: You Asked, WAI Answered
- Have You Seen the New WCAG 2 FAQ?
- clue, crew, cue, do, few, grew, knew, que, slew, threw, through. thru, to, too, true, two, 2, view, you
body brainstorms:
- When will Web Content Accessibility
Guidelines (WCAG) 2.0 be done? What is the current status? When should I
start using WCAG 2.0? Find
A Few WCAG 2 Questions & Answers . - When will WCAG 2.0 be done? What is the current status? When should I
start using WCAG 2.0? Find out from the new WAI document:
A Few WCAG 2 Questions & Answers . - WAI gathered some common questions about WCAG 2.0 and provided answers in A Few WCAG 2 Questions & Answers.
- See A Few WCAG 2 Questions & Answers for: When will WCAG 2.0 be done? What is the current status of WCAG 2.0? When should I start using WCAG 2.0?
For Review: Updated EARL 1.0 Schema Working Draft
Evaluation and Report Language (EARL) is a format to exchange, combine, and analyze results from different Web accessibility evaluation tools. EARL 1.0 Schema Working Draft was published 27 September 2006. See:
- Call for Review: Evaluation and Report Language (EARL) 1.0 Schema [Updated Working Draft]
- Evaluation and Report Language (EARL) Overview
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute
Please send comments by 25 October 2006. (2006-09-27)
ARIA
Accessibility for Rich Internet Applications: WAI-ARIA Suite Debuts
- W3C Announces Roadmap for Accessible Rich Internet Applications (ARIA) press release
- [Call for Review: First Public Working Drafts of ARIA Suite for Accessible Rich Internet Applications @@WAI IG] e-mail
For information on how Working Drafts are developed, see: How WAI Develops Accessibility Guidelines through the W3C Process. (2006-09-26)
title brainstorms:
- WAI-ARIA Suite Debuts: Accessibility for Rich Internet Applications
- ARIA Suite Debuts: Accessible Rich Internet Applications
- Accessible Rich Internet Applications: ARIA Suite Debuts
body brainstorms:
- previous version: W3C WAI's work on accessiblity of AJAX, DHTML, and emerging rich Internet application technologies is available for review.
- W3C WAI today provided First Public Working
Drafts of work on accessiblity of AJAX, DHTML, and emerging rich Internet
application technologies.
- tweak: W3C WAI published First Public Working Drafts of the ARIA suite that addresses accessiblity of AJAX, DHTML, and emerging rich Internet application technologies.
- W3C WAI's work on accessiblity of AJAX, DHTML, and other emerging rich Internet application technologies is available for review. WAI-ARIA Roadmap provides an overview, WAI-ARIA Roles addresses user interface controls and navigation, and WAI-ARIA States and Properties addresses behavior of elements. See:
- [from michael] A Roadmap for Accessible Rich Internet Applications describes how technologies support accessibility of rich Web content, for example in AJAX and other emerging technologies. Two companion specifications provide detail in specific areas needed to fulfill the roadmap. ARIARoles addresses user interface controls and navigation, and ARIA States and Properties addresses behavior of elements.
Access Board Appointment
source material & notes
- http://lists.w3.org/Archives/Team/w3t-wai/2006Jul/0044.html
- http://www.access-board.gov/news/508committee.htm
- note that this will be the first that many people have heard that 508 is opening up for update
- ought to lead with "508" since that's what most people know (rather than "Access Board")
- probably can leave out the 255 Telecommunications part, since that's less relevant for us. Also note that some of the Access Board articles lead with 508 in title, even though covered both
- probably don't need to include full name of committee, nor full name of Access Board "Architectural and Transportation Barriers Compliance Board"
- try to limit repetetive info between title& body to be succinct & stronger (e.g.,avoid saying "appointed to" in both, use "update" in one and "revising" in another)
- quotes from source material:
- "The Architectural and Transportation Barriers Compliance Board (Access Board) has decided to establish an advisory committee to assist it in revising and updating accessibility guidelines for telecommunications products and accessibility standards for electronic and information technology"
- "Telecommunications and Electronic and Information Technology Advisory Committee (Committee)"
- "Board Names Advisory Committee for 508 Standards Update July 6,
2006
The Board has organized a new advisory committee to assist in updating its access standards for electronic and information technologies procured by the Federal government. - "The committee will provide a forum for establishing consensus on updating the 508 standards... ... and their harmonization with comparable international efforts in this area.""
WAI to Advise on 508 Standards Update
W3C WAI has been appointed to the Advisory Committee for the revision of U.S. Section 255 guidelines and Section 508 standards, which include Web accessibility. WAI looks forward to continuing to coordinate with organizations around the world to develop harmonized standards for Web accessibility. Additional information is available in the U.S. Access Board article: Board Names Advisory Committee for 508 Standards Update. (2006-07-20)
title brainstorms:
- would like something other than "appointed to committee" for title/heading -- something more active on our part. also would be good if heading makes it clear that Section 508 is to be updated
- WAI Contributes to 508 Standards Update
- WAI to Contribute to 508 Standards Update
- WAI Appointed to 508 Standards Update Committee
- WAI Joins 508 Standards Update Committee
WAI Named to 508 Standards Update Committee
WAI Appointed to 508 Standards Update Advisory Committee
WAI Appointed to 508 Standards Advisory Committee
WAI Appointed to 508 Standards Committee - WAI Advises on 508 Standards Update for Web Accessibility
- WAI Appointed to U.S. Access Board Committee for Accessibility Standards
- W3C WAI ...
body brainstorms:
- first sentence without 255: W3C WAI has been appointed the Advisory Committee for the revision of U.S. Section 508 standards, which include Web accessibility.
- previous version: WAI will participate in the committee to assist in revising U.S. Section 508 standards, which include Web accessibility. WAI looks forward to continuing to coordinate with organizations around the world to develop harmonized standards for Web accessibility. Additional information is available in the U.S. Access Board article: Board Names Advisory Committee for 508 Standards Update.
- WAI will participate in the Committee to assist in revising U.S. Section 255 guidelines and Section 508 standards, which include Web accessibility.
- W3C WAI will participate in the Advisory Committee convened by the U.S. Access Board to assist in updating accessibility standards for electronic and information technology, including Web sites.
- The Advisory Committee will assist in updating accessibility standards for electronic and information technology, including Web sites.
- [09:55] <judy> w3c wai has been appointed to a u.s. access board
committee to [refresh] u.s. section 508 and 255, which address
accessibility of electronic and information technology, including web
accessibility. (and then...)
[09:56] <judy> (want to say, but not quite right...)
[09:56] <judy> w3c wai hopes to use this opportunity to promote harmonization on web accessibility standards
[09:56] <judy> or some such
[09:56] <judy> but can't say...
[09:56] <judy> hey, we want to twist your arm, look out! ;)
UK UPA podcast
Podcast: Interview on WCAG 2
Shawn Henry discusses WCAG 2.0 with UK UPA president Giles Colborne: transcript and audio files. (2006-07-06)
heading brainstorms:
- Podcast: A Brief Chat on WCAG 2.0
- Interview on WCAG 2: June 2006 Podcast Available
- Podcast: A Few Questions on WCAG 2.0
- A Chat on WCAG 2.0: Podcast Available
- Podcast: A Few Perspectives on WCAG 2.0
- Podcast: Tips on WCAG 2.0
- rejected:
- Interview: Wassup with WCAG 2
- Briefly: WAI Responds to Questions on WCAG 2.0
- Brief Bits: Shawn Henry answers questions on WCAG
- Interview Questions: A Few on WCAG Two
- WAI Responds to WCAG Two Questions
- From the Horses Mouth [heh]
body brainstorms:
- Shawn Henry discusses WCAG 2.0 with UK UPA president Giles Colborne: WCAG 2.0 for current and future Web development, existing and planned materials, testable, additional opportunties to comment. Online: transcript, audio file. (2006-07-06)
- applies to more advanced today and in the future technologies, more precisely testable, more flexible for developers, more effective accessibility, will be more understandable & usable wwith supporting materials under development
- Shawn Henry, W3C WAI, discusses WCAG 2.0 with Giles Colborne, UK UPA president: Why WCAG 2.0? AJAX? Approaching WCAG 2.0 unfamiliar territory? More testable? Concerns? Missed comment period? Online: transcript, audio file
- Shawn Henry, W3C WAI, discusses WCAG 2.0 with Giles Colborne, UK UPA president: audio file, transcript.
- WAI Staff addresses the length of WCAG 2.0 supporting material, commenting on WCAG 2.0 documents, and goals for WCAG 2.0.
Custom View of WCAG Two: Quick Reference
WCAG 2.0 Quick Reference lists the basic requirements of WCAG 2.0, which are the success criteria. For each success criteria, it lists techniques that tell you how to meet the requirements. You can customize the Quick Reference for the Web technologies you are using and Levels 1, 2, or 3. See also: Overview of WCAG 2.0 Documents. (2006-06-20)
other heading ideas:
- New Resource: WCAG 2.0 Quick Reference
- Birdseye View of WCAG Two: Quick Reference
- A Customizable List of What and How: WCAG 2.0 Quick Reference
- Just the Facts: WCAG 2.0 Quick Reference
- Cut to the Chase: WCAG 2.0 Quick Reference
- WCAG 2.0 Quick Reference: The Bare Bones
other body ideas:
- WCAG 2.0 Quick Reference lists requirements (success criteria) and techniques to meet WCAG 2.0. You can customize it to list the success criteria levels and Web technologies that you are using. See also: Overview of WCAG 2.0 Documents.
- WCAG 2.0 Quick Reference lists the basic requirements of WCAG 2.0, which are the success criteria. For each success critieria, it lists techniques that tell you how to meet the requirements. You can customize the Quick Reference based on levels and the technologies you are using. See also: Overview of WCAG 2.0 Documents.
- WCAG 2.0 Quick Reference lists requirements and techniques to meet WCAG 2.0. It can be customized for success criteria levels and Web technologies. See also: Overview of WCAG 2.0 Documents
fyi, from WAI IG email:
I'd also like to bring your attention to the draft "WCAG 2.0 Quick Reference"
document, which might be helpful as you review and comment on WCAG 2.0. The
WCAG 2.0 Quick Reference is a summary of WCAG 2.0 requirements (success
criteria) and the techniques which are sufficient to meet the success
criteria when using specific Web technologies.
Extended Deadline: WCAG 2.0 Last Call Review
Web Content Accessibility Guidelines 2.0 (WCAG 2.0) Last Call Working Draft and supporting documents were published 27 April 2006. WAI encourages you to review these documents and submit any comments. See:
Please send comments by 22 June 2006. (2006-04-27)
WCAG 2.0 Last Call
W3C Home Page (and NewsWire and Newsletter):
[based on Dec 2005
announcement]
Last Call: Web Content Accessibility Guidelines (WCAG) 2.0
2006-04-26: The Web Content Accessibility Guidelines (WCAG) Working Group has released the Last Call Working Draft of Web Content Accessibility Guidelines 2.0, and Working Drafts ofUnderstanding WCAG 2.0, Techniques for WCAG 2.0, and About Baselines for WCAG 2.0. Following WCAG makes Web content more accessible to the vast majority of users, including people with disabilities and older users, using many different devices including a wide variety of assistive technologies. Comments are welcome through 31 May. Read about the Web Accessibility Initiative.
WAI Home Page Highlight and RSS Feed:
[based on Dec
2005 announcement]
For Review: WCAG 2.0 Last Call
Web Content Accessibility Guidelines 2.0 (WCAG 2.0) Last Call Working Draft and supporting documents were published 27 April 2006. WAI encourages you to review these documents and submit any comments. See:
Please send comments by 31 May 2006. (2006-04-27)
Involving Users in Eval doc:
goal of highlight:
- liven up the WAI home page
- catch people's attention (mostly in RSS aggregators I guess)
- get them to read & distribute the document
here's an example of the format and length:
Want to know how people with disabilities use your Web site? Ask.
Web accessibility guidelines, techniques, and tools provide the basis for Web accessibility. Including people with disabilites in the Web development process helps to understand the "why" behind accessibility. It leads to more effective accessibility solutions, developed more efficiently. See Involving Users in Web Accessibility Evaluation . (2005-10-@@)
replies to request for brainstorming incorporated below
some heading thoughts:
- Powerful, Effective, Enlightening: Including People with Disabilities in Web Evaluation
- Empowering, Enlightening, Effective: Include People with Disabilities in your Web Evaluation
- Ever Wonder How People with Disabilities use the Web? Ask.
- Want to know how people with disabilities use your Web site? Ask.
- Guidelines, Tools, People with Disabilities: The Next Level of Web Accessibility Evaluation
some body thoughts:
- Get the most from your accessibility investment and develop effective accessibility solutions by including users. Involving Users in Web Accessibility Evaluation