Highlights Drafts May 2008 - November 2009
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.
Posting videos on YouTube, dotSUB, etc.
background on reason for this post
W3C Q&A blog post:
Posting Videos Online
@@ see Judy's comments @@
We recently discussed the issue of posting W3C videos on non-W3C websites. Here are some thoughts and initial decisions.
W3C is a vendor-neutral organization and we are careful to not [@@favor? endorse?] a specific vendor over another. This issue came recently as we discussed posting videos online. While we plan to post videos on the W3C website, we also want to take advantage of visibility and features on other sites.
Our initial decision is to go ahead and post on sites such as YouTube (because of the visibility), dotSUB (because of the ease of community translation of captions), and maybe others. Please note that we are not endorsing these vendors or sites over others.
We plan on announcing videos on Web accessibility topics in the coming weeks...
p.s. We will provide transcripts for the videos, as well as captions and translations for some.
Process Intro/"101"
http://www.w3.org/WAI/intro/w3c-process
Developing WAI Guidelines: The ABCs of W3C Process
Call for Review, Last Call Working Draft, WAI Web Accessibility Guidelines, W3C Recommendation, Web Standard, W3C Technical Report—these concepts and more are clarified in How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute. This new WAI document introduces the process designed to bring together a broad range of perspectives to develop consensus on Web accessibility solutions. (2006-09-@@)
title brainstorms:
- Developing Accessibility Guidelines: The WAI Way
- Developing Web Accessibility Guidelines: Why the WAI Way
- W3C Process Revealed in Plain Language
- How WAI Guidelines Get Developed: An Intro
- W3C WAI Last Call Working Draft... Huh?
- W3C WAI Last Call Working Draft... What's That?
- W3C WAI Working Draft... What's it all mean?
- W3C Process in 5 Easy Steps
- Opening up the Black Box: W3C Process Intro
- W3C Process Intro: Ah, Now I Get It!
- Not so Secret After All: The W3C Process
- For Ah-Hah Moments: The W3C Process Intro
body brainstorms:
- The new WAI resource How WAI Develops Accessibility Guidelines through the W3C Process describes milestones and opportunities for you to contribute. It answer questions you may have about ...
- Call for Review, Last Call Working Draft, WAI Accessibility Guidelines, W3C Recommendation, Web Standard, W3C Technical Report—these concepts and more are clarified in the new WAI document How WAI Develops Accessibility Guidelines through the W3C Process, which describes development milestones and opportunities for you to contribute. It introduces the process designed to bring together a broad range of perspectives to develop consensus on Web accessibility solutions.
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute introduces how WAI works through a process designed to ensure broad community input and encourage consensus development.
- WAI has recently announced Working Drafts of accessibility guidelines. But what does that mean?
- Last Call Working Draft, Call for Review, WAI Accessibility Guidelines, W3C Recommendation, Web Standard, W3C Technical Report -- these concepts and more are clarified in How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
Standards Harmonization
http://www.w3.org/WAI/Policy/harmon
Sing the Same Song: Standards Harmonization
Why Standards Harmonization is Essential for Web Accessibility describes the benefits of consistent international standards, why people develop different standards, and how adopting common standards can accelerate progress on Web accessibility. (2006-00-00)
title brainstorms:
- Sing the Same Song: Standards Harmonization
- Singing the Same Song: Standards Harmonization
- Standards Harmonization: Singing the Same Song
- Standards Harmonization: Sing the Same Song
body brainstorms:
- Why Standards Harmonization is Essential for Web Accessibility describes the benefits of consistent international standards, explores why people develop different standards, and states how adopting common standards can accelerate Web accessibility progress. (2006-00-00)
- Why Standards Harmonization is Essential for Web Accessibility describes the benefits of adopting a consistent set of international standards. It explores why people develop different standards, and the accelerated progress that can be made through adoption of common standards. (2006-00-00)
- [from WAI TIES update] "Why Standards Harmonization is Essential for Web Accessibility" describes the benefits of adopting a consistent set of international technical standards for Web accessibility. It explores reasons why people develop different standards, as well as the accelerated progress that can be made through adoption of a common standard.
- [from WAI site annotated navigation page] Explains the key role that harmonization of standards plays in increasing the accessibility of the Web for people with disabilities.
- ... investigates the issues surrounding...
Evaluation Tools Database Search
http://www.w3.org/WAI/ER/tools/Overview.html
Finding the Right Tool for the Job: Database Search
Web accessibility evaluation tools are software programs or online services that help determine if a Web site meets accessibility guidelines. Web Accessibility Evaluation Tools is a database of over 100 tools that you can search and sort. (2006-00-00)
title brainstorms:
- Finding the Right Tool for the Job: Database Search
- Finding the Right Tool for the You: Evaluation List
- So Many Tools, So Little Time: Sort Through 'Em
- Hammer or Screwdriver: Find the Right Tool
- Tools List: Check Your Criteria
- Check Your criteria: Evaluation Tools Search
- 100 to 1: Evaluation Tools Search
- Web Accessibility Evaluation Tools: Search and Sort
- Accessibility Evaluation Tools Database: Search Options Galore
- Just Right...
- Toolbox...
- Evaluating Accessibility: Sorting through the Tools
- Accessibility Evaluation: Sorting through the Tools
body brainstorms:
- Web accessibility evaluation tools are software programs or online services that help determine if a Web site meets accessibility [guidelines|standards]. Web Accessibility Evaluation Tools is a database of over 100 tools that you can search on 15 categories and sort on 3 fields.
- Provides a comprehensive list of Web accessibility evaluation tools that is searchable and sortable.
W3C Authorized Translation Policy
http://www.w3.org/2005/02/TranslationPolicy.html
title brainstorms:
- It's Official: W3C Authorized Translation Policy
notes:
- highlight points to longer WAI IG message
Retrofitting
http://www.w3.org/WAI/impl/improving.html
"Improving the Accessibility of Your Web Site" provides guidance for fixing accessibility barriers in existing Web sites. It describes strategies for identifying priorities, developing a retrofitting plan, and repairing accessibility barriers efficiently.
CAPTCHA:
Robot or Human? Tests Discriminate Against Humans
Tests designed to block software robots from interacting with a Web site also block humans who are blind, deaf, hard of hearing, have low vision, or a learning disability such as dyslexia.
The W3C Note Inaccessibility of CAPTCHA examines potential solutions to test that users are human in a way that is accessible to people with disabilities. (2005-00-00)
Glossary/Lexicon:
notes: [@@not needed???] While the primary purpose of the glossary if to help translators of...
Deciphering WAI Geek Speak: A Basic Glossary
Does the sentence: "The user agent doesn't render the deprecated markup" leave your head spinning? The "Basic Glossary for WAI Documents" helps to clarify the meaning of these and other words used in WAI documents.
More ABCs from WAI: A Basic Glossary
The "Basic Glossary for WAI Documents" helps to clarify the meaning of key words used in WAI documents. It is part of a series of introduction and overview documents developed by WAI in 2005.
Archive Draft Blurbs through April 2008
These were moved to planning-to-2008, to cut down on page & file size.
Archive May 2008 - Present
NOTE: This information is an unapproved draft and should not be referenced or quoted under any circumstances.
Ordered with oldest at the top, most recent at the bottom:
WAI-AGE Literature Review FPWD
[10:27] <judy> - work underway on accessibility/ageing angle of web
accessibility
[10:27] <judy> - shiny first draft to look at
[10:28] <judy> - (task force starting up if interested)
[10:28] <judy> - by the way, some interesting overlaps &
intersections (or whatever, abt the relevance of accessibility to ageing
area)
[10:29] <judy> - project page is is *here* for more info
[10:39] <shawn> wai-age lit review kicks off wai-age project
[10:39] <shawn> neat stuff to look at in newish area underway
[10:41] <shawn> shiney - neat stuff, someting ageing, work underway
W3C Home Page (and Newsletters):
"Web Accessibility for Older Users: A Literature Review" -- Comments Welcome on First Public Draft
2008-05-14: The Web Accessibility Initiative (WAI) Education and Outreach Working Group Working Group (EOWG) has published Web Accessibility for Older Users: A Literature Review as a First Public Working Draft. The document includes reviews and analysis of guidelines and articles covering the requirements of people with Web accessibility needs related to ageing. This literature review will inform WAI efforts to promote accessibility solutions for older Web users and potentially to develop profiles or extensions to WAI guidelines. The literature review is a deliverable of the WAI-AGE Project (Ageing Education and Harmonisation). See the call for review and participation for an introduction to the project and an invitation to contribute to the literature review and other WAI-AGE work; and about the Web Accessibility Initiative.
notes:
- recent headlines:
- Content Transformation Guidelines 1.0, Comments on First Public Draft Welcome 2008-04-14
- XQuery Scripting Extension 1.0 and Use Cases; Comments on First Public Drafts Welcome 2008-03-28
- Extensible Stylesheet Language (XSL) Requirements Version 2.0; Comments Welcome on First Public Draft 2008-03-26
WAI Highlight for home page & RSS feed:
WAI-AGE: Addressing Accessibility Needs Due to Ageing
The WAI-AGE Project (Ageing Education and Harmonisation) focuses on education and outreach regarding the requirements of people with Web accessibility needs related to ageing. One of the early deliverables of the WAI-AGE project is Web Accessibility for Older Users: A Literature Review, published on 14 March as a First Public Working Draft. WAI encourages you to review this draft and submit any comments by 4 June 2008, if possible.
See Call for Review and Participation: WAI-AGE Literature Review and Task Force[link] for an introduction to the project and an invitation to contribute to the literature review and other WAI-AGE work. (2008-05-14)
notes:
- title brainstorms (note, for length, i think can leave "web" out of title
- given the context of WAI, and make sure clear in text)
- WAI-AGE: Addressing Accessibility Needs Due to Ageing
- WAI-AGE: Addressing Accessibility Needs Related to Ageing
- WAI-AGE Project Presents First Deliverable
- Accessibility Needs Due to Ageing (it happens to the best of us)
- Literature Review kicks off project on accessibility needs related to ageing
- body brainstorms
- ...
- ...
WAI IG email:
Call for Review and Participation: WAI-AGE Literature Review and Task Force
Dear WAI Interest Group Participants,
The Web Accessibility Initiative: Ageing Education and Harmonisation
(WAI-AGE) Project is a European Commission-funded project that focuses on
education and outreach regarding the requirements of people with Web
accessibility needs related to ageing. See:
WAI-AGE Project page
http://www.w3.org/WAI/WAI-AGE/
As part of the WAI-AGE project, today the WAI Education and Outreach Working
Group Working Group (EOWG) published a literature review as a First Public
Working Draft:
Web Accessibility for Older Users: A Literature Review
http://www.w3.org/TR/2008/WD-wai-age-literature-20080514/
This draft document reviews and analyzes guidelines and articles covering the
requirements of people with Web accessibility needs related to ageing. The
purpose of the literature review is to inform education and outreach to better
promote accessibility solutions for older Web users, and potentially develop
profiles or extensions to WAI guidelines.
We welcome your comments on the literature review by 4 June 2008 if
possible. The e-mail address for sending comments, which is publicly archived,
is:
public-comments-wai-age@w3.org
To learn about participating in the WAI-AGE Task Force, contact Andrew Arch
<andrew@w3.org>. WAI-AGE work is being conducted in cooperation with
EOWG:
Education and Outreach Working Group (EOWG)
http://www.w3.org/WAI/EO/
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry
On behalf of:
Andrew Arch, WAI-AGE Web Accessibility and Ageing Specialist
Shadi Abou-Zahra, WAI-AGE Web Accessibility Specialist for Europe
Judy Brewer, WAI-AGE Project Coordinator
notes:
- reviewed first paragraph: "The Web Accessibility Initiative-Ageing Education and Harmonisation (WAI-AGE) Project focuses on education and outreach regarding the requirements of people with Web accessibility needs related to ageing. WAI-AGE is a European Commission Information Society Technology (IST) Specific Support Action with the goal of increasing accessibility of the Web for the elderly as well as for people with disabilities in European Union Member States."
- other
subject brainstorms:
- WAI-AGE Task Force and Literature Review on Web Accessibility
Needs Due to Ageing
WAI-AGE Literature Review and Task Force on Web Accessibility Needs Due to Ageing - WAI-AGE Work on Web Accessibility Needs Due to Ageing
- call bunch:
- Call for Review and Participation: Web Accessibility Needs Due to Ageing Project (WAI-AGE) Literature Review and Task Force
- Call for Review and Participation: WAI-AGE Project Literature Review and Task Force
- Call for Review and Participation: WAI-AGE Project Literature Review and Task Force on Web Accessibility Needs Due to Ageing
- Call for Review and Participation: WAI-AGE Ageing Education and Harmonisation Project Work
- Web Accessibility Needs Due to Ageing Task Force and Literature Review
- Web Accessibility Needs Due to Ageing: WAI-AGE First Project Announcements
- first draft: WAI-AGE Invitation: Contribute to Project on Web Accessibility Needs Due to Ageing
- Judy's: Project on Web accessibility and Ageing: literature review; task force
- WAI-AGE Task Force and Literature Review on Web Accessibility
Needs Due to Ageing
WAI-ARIA Public Editor's Draft May 2008
last updated $Date: 2011/02/14 15:42:16 $
- Which version will the links go to? Proposal:
- PFWG Public Page links go to the Editors' Drafts - and they are clearly labeled as "in-progress Editors' Drafts"
- WAI-ARIA Overview links go to the Public Working Drafts - and we add a note to that page that in-progress Editors' Drafts are also available, with links
- http://www.w3.org/WAI/PF/aria-primer/and http://www.w3.org/WAI/PF/aria-practices/ needs change from "W3C Working Draft 7 May 2008" to "Editors' Draft 7 May 2008", yes? (others, too, maybe, I didn't check)
WAI Highlight for home page & RSS feed:
Public Drafts: Updated WAI-ARIA Documents
Updated Editors' Drafts of the WAI-ARIA documents are now publicly available so that anyone can follow how issues are being addressed in the draft WAI-ARIA specification. These documents are works-in-progress, not official "Public Working Drafts". Please see more information in Updated WAI-ARIA Editors' Drafts Now Publicly Available[link]. (2008-05-28)
Other ideas:
- For Review: Updated WAI-ARIA Documents
- [another first sentence] Updated Editors' Drafts of the WAI-ARIA
documents are now publicly available, enabling anyone to read how issues
are currently being addressed in the draft WAI-ARIA specification.
WAI IG email:
Updated WAI-ARIA Editors' Drafts Now Publicly Available
Dear WAI Interest Group Participants,
Previously WAI's Accessible Rich Internet Applications (WAI-ARIA) documents were periodically published as a Public Working Drafts, and the in-progress "Editors' Drafts" were available only to W3C members. As of today, the Editors' Drafts are available publicly, so that anyone can follow how issues are being addressed in the developing WAI-ARIA documents.
The following drafts are now available:
- WAI-ARIA 1.0 Editors' Draft
<http://www.w3.org/WAI/PF/Group/aria/>
- WAI-ARIA Primer Editors' Draft
<http://www.w3.org/WAI/PF/aria-primer/>
- WAI-ARIA Best Practices Editors' Draft
<http://www.w3.org/WAI/PF/aria-practices/>
- WAI-ARIA Roadmap Editors' Draft
<http://www.w3.org/WAI/PF/Group/roadmap/>
Unlike Public Working Drafts, the in-progress Editors' Drafts:
* Do not necessarily represent Working Group consensus, that is, the drafts may
include proposals that the Working Group has not agreed on
* May change frequently without public notification
* May not yet be up-to-date with recent Working Group decisions
* Include internal "Todo" notes and areas that are not ready for review or
comment
When the documents are published as Public Working Drafts and are ready for more detailed review, we will announce a Call for Review. For now, the Protocols and Formats Working Group invites comments on host language embedding and other technical issues under discussion in W3C Working Groups.
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, see:
- WAI-ARIA Overview
<http://www.w3.org/WAI/intro/aria>
For more information, see:
- WAI-ARIA FAQ
<http://www.w3.org/WAI/aria/faq>
- 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>
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry
On behalf of:
Michael Cooper - W3C Team Contact for PFWG
Al Gilman - Chair of PFWG
Notes:...
WCAG 2.0 at a Glance
WAI Highlight for home page & RSS feed:
For Review: WCAG 2 at a Glance
Web Accessibility: WCAG 2.0 at a Glance provides a summary of Web Content Accessibility Guidelines (WCAG) 2.0. We welcome your comments on this draft, preferably by 15 July 2008. (2008-07-07)
other ideas:
- ...
WAI IG e-mail:
Call For Review: WCAG 2.0 at a Glance
Dear WAI Interest Group Participants,
WAI invites you to comment on a new draft resource:
* Web Accessibility: WCAG 2.0 at a Glance
http://www.w3.org/WAI/WCAG20/glance/
We plan to provide this resource in a print version and incorporate it into WCAG 2.0 presentations, such as the "About WCAG 2.0" presentation at <http://www.w3.org/WAI/presentations/WCAG20_about/>
In order to make this available soon, we would like to receive comments
by:
* 15 July 2008 * at the publicly-archived mailing list:
wai-eo-editors@w3.org
WCAG 2.0 at a Glance is developed with the Education and Outreach Working Group (EOWG) <http://www.w3.org/WAI/EO/> and Web Content Accessibility Guidelines Working Group (WCAG WG) <http://www.w3.org/WAI/GL/>.
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
NOTE: When we announce the print version, we might decide to say that additional comments are welcome, which we will consider for an updated version....
Q&A Blog Post:
probably wait to do this with the final version...
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.
Mobile Experiences doc July 2008
last updated $Date: 2011/02/14 15:42:16 $
WAI Highlight for home page & RSS feed:
Shared Web Experiences: Mobile and Accessibility Barriers
WAI has just published an updated draft of Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities. This document is particularly useful for demonstrating the overlap between accessible and mobile-friendly Web content, for developing a business case for accessibility, and for more efficiently developing your Web site for both accessibility and mobile devices. See:
- Call for Review: Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities 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.
Please send comments by 20 August 2008, if possible. (2008-07-28)
title brainstorms:
- Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities
- Shared Web Experiences: Mobile and Accessible
- Shared Web Experiences: Common Barriers
- Shared Web Experiences: Mobile and Accessibility Barriers
- Mobile and Accessible: Shared Web Experiences
body brainstorms:
- options to add "links to recommendations from the Web Content
Accessibility Guidelines (WCAG) and the Mobile Web Best Practices (MWBP)
for designing Web content that is both accessible and
mobile-friendly." (but then very long)
- WAI has just published an updated draft of Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities. This document is particularly useful for demonstrating the overlap between accessible and mobile-friendly Web content, for developing a business case for accessibility, and for more efficiently developing your Web site for both accessibility and mobile devices. It links to recommendations from the Web Content Accessibility Guidelines (WCAG) and the Mobile Web Best Practices (MWBP) for designing Web content that is both accessible and mobile-friendly. See:
- WAI has just published an updated draft of Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities, which links to recommendations from the Web Content Accessibility Guidelines (WCAG) and the Mobile Web Best Practices (MWBP) for designing Web content that is both accessible and mobile-friendly. This document is particularly useful for demonstrating the overlap between accessible and mobile-friendly Web content, for developing a business case for accessibility, and for more efficiently developing your Web site for both accessibility and mobile devices. See:
- an idea for an additional first sentence (but then pretty long):
- People who use the Web on mobile devices experience similar barriers in Web interaction as people with disabilities using desktop or laptop computers.
- People who use the Web on mobile devices have a lot in common with people who have disabilities — they experience similar barriers in Web interaction.
- ...which lists these barriers and links to recommendations for designing Web content to avoid these barriers from the ...
- There is much talk of the overlap between designing Web sites to be
mobile-friendly and to be accessible to people with disabilities. WAI has
just published an updated draft document that helps clarify this overlap:
Shared Web
Experiences...
[or WAI has just published an updated draft resource that documents this overlap...
or WAI has just published an updated draft document that clarifies this overlap...] - too boring:
- WAI has published an updated draft of Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities. It provides examples of how people with disabilities (using desktop or laptop computers) and people without disabilities who are using mobile devices experience similar barriers when interacting with Web sites. It links to recommendations for designing Web content without these barriers from the Web Content Accessibility Guidelines (WCAG) and the Mobile Web Best Practices (MWBP).
- (used something like this first sentence in previous announcements): Web sites can be more efficiently designed to be mobile-friendly and accessible for people with disabilities when developers understand the significant overlap between the two design goals and guidelines. Today WAI published an updated draft document that helps understand that overlap: Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities.
WAI IG email:
Call for Review: Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities
Dear WAI Interest Group Participants,
The Education and Outreach Working Group and the Mobile Web Best Practices
Working Group invite you to comment on the following updated draft published 28
July 2008:
* Shared Web Experiences: Barriers Common to Mobile Device Users and People
with Disabilities
http://www.w3.org/WAI/mobile/experiences
This WAI resource is particularly useful for demonstrating the overlap between accessible and mobile-friendly Web content, for developing a business case for accessibility, and for more efficiently developing your Web site for both accessibility and mobile devices.
The document provides examples of how people with disabilities (using desktop or laptop computers) and people without disabilities who are using mobile devices experience similar barriers when interacting with Web sites. It links to recommendations from the Web Content Accessibility Guidelines (WCAG) and the Mobile Web Best Practices (MWBP) for designing Web content that is both accessible and mobile-friendly.
The overlap between design goals and guidelines covering accessibility for
people with disabilities, and design goals and best practices for mobile
devices is introduced in:
* Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both
for People with Disabilities and for Mobile Devices
http://www.w3.org/WAI/mobile/
The Working Groups particularly seek feedback on:
- Is it clear what information is provided in each document, and where to get
other related information?
- In the "Shared Web Experiences" document, is the detailed information clear
yet succinct?
- Are there other examples that we might want to include in the "Shared Web
Experiences" document?
Please send comments on these documents by 20
August 2008 if possible, to the publicly-archived mailing list:
wai-eo-editors@w3.org
For more information on the Working Groups, see:
* Web Accessibility Initiative (WAI) Education and Outreach Working Group
http://www.w3.org/WAI/EO/
* Mobile Web Best Practices Working Group
http://www.w3.org/2005/MWI/BPWG/
Note: Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Thank you in advance for your comments.
Regards,
Shawn Lawton Henry, EOWG Chair
notes:
- another way to word: "It links to recommendations from the Web Content Accessibility Guidelines (WCAG) and the Mobile Web Best Practices (MWBP) for designing Web content that is both accessible and mobile-friendly." would be: "It links to recommendations for designing Web content without these barriers from the Web Content Accessibility Guidelines (WCAG) and the Mobile Web Best Practices (MWBP)."
WAI ARIA 6 Aug 2008
W3C Home Page (and Newsletters):
Accessible Rich Internet Applications (WAI-ARIA) Working Draft Published
2008-08-06: The Protocols and Formats Working Group published an updated Working Draft of Accessible Rich Internet Applications (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. WAI-ARIA is introduced in the WAI-ARIA Overview and the WAI-ARIA FAQ.
Read the updated WAI-ARIA Specification announcement that requests feedback on host language embedding, and about the Web Accessibility Initiative.
notes:
WAI Highlight for home page & RSS feed:
For Review: Updated WAI-ARIA Specification
WAI has published an updated Working Draft of WAI-ARIA, the Accessible Rich Internet Applications technical specification. We especially request review of how WAI-ARIA is implemented in host languages, such as HTML, XHTML, and SVG. See:
- Call for Review: Updated WAI-ARIA Specification announcement e-mail;
- WAI-ARIA Overview, which links to WAI-ARIA FAQ and related documents for Web site developers.
Please send comments by 3 September 2008. (2008-08-06)
WAI IG email:
Call for Review: Updated WAI-ARIA Specification
Dear WAI Interest Group Participants
The Protocols and Formats Working Group invites you to comment on the
following updated document published 6 August 2008:
* Accessible Rich Internet Applications (WAI-ARIA) 1.0 Working Draft
http://www.w3.org/TR/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 (also known as AJAX), HTML, JavaScript, and related technologies.
For an introduction to WAI-ARIA and links to related documents for Web site
developers, please see:
* WAI-ARIA Overview
http://www.w3.org/WAI/intro/aria
* WAI-ARIA FAQ
http://www.w3.org/WAI/aria/faq
The Working Group particularly seeks feedback on host language embedding,
that is, how ARIA is implemented in HTML, XHTML, SVG, and other host languages.
This is defined in section 6 "Implementation in Host Languages" and section 7
"Quality Assurance". Please send any comments
* by 3 September 2008 to
public-pfwg-comments@w3.org
For more information, see:
* How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
* Protocols and Formats Working Group
http://www.w3.org/WAI/PF/
Note: Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Thank you in advance for your comments.
Regards,
Shawn Henry, W3C WAI
On behalf of:
Al Gilman, Chair of PFWG
notes:
- ...
NOTE: This information is an unapproved draft and should not be referenced or quoted under any circumstances.
Upcoming presentations (sent Aug 2008)
WAI IG email:
subject: Upcoming WAI Presentations in 2008 and SXSW voting
Dear WAI Interest Group Participants,
WAI staff will be presenting the following sessions in the upcoming months and would enjoy meeting with those of you who attend the conferences:
* HCI and the Older Population 2008 in Liverpool, United Kingdom on 1
September: "Web Accessibility and the Older Population", Andrew Arch
<http://www-edc.eng.cam.ac.uk/~jag76/hci_workshop08/>
* Accessible Design in the Digital World in York, United Kingdom on 23
September: "How web accessibility guidelines apply to design for the ageing
population", Andrew Arch
<http://www.addw08.org/>
* Web Builder 2.0 in Las Vegas, NV, USA on 13 and 14 October: "Getting Real
with Accesibility" and "Accessibility in a Web 2.0 World", Shawn Henry
<http://webbuilderconference.com/2008/>
* User eXperience Ru 2008 in Moscow, Russia on 30 and 31 October: "Web
Accessibility Standards: A Foundation for International Cooperation and Local
Implementation" and "Making the Web Accessible to All", Shawn Henry
<http://userexp.ru/>, English: <http://userexp.ru/en/>
* UPA Europe 2008, Usability and design: cultivating diversity in Turin,
Italy on 5 and 6 December: "Overlapping User Experiences: Mobile Web Usability
and Accessibility for People with Disabilities" and "How New Web Accessibility
Standards Impact User Experience Design", Shawn Henry
<http://www.upaeurope2008.org/>
Additional presentations will be announced soon. For an updated list of WAI
presentations, see the WAI home page, under "Events, Meetings, Presentations"
at:
<http://www.w3.org/WAI/#announce>
You can search for upcoming and past W3C presentations at:
<http://www.w3.org/Talks/>
---
SXSW <http://sxsw.com/interactive/> is a conference where we would particularly like to engage in discussions about Web accessibility with developers and designers. SXSW uses community input to help choose which session proposals to accept.
Please consider taking a couple of minutes to vote for accessibility
sessions, before the deadline of 29 August. They are listed at:
<http://panelpicker.sxsw.com/ideas/index/3/q:accessibility>
---
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry, W3C WAI Education and Outreach
notes:previous similar ones:
ERT pubs May 2008
last updated $Date: 2011/02/14 15:42:16 $
W3C Home Page (and Newsletters):
Representing Content in RDF and HTTP Vocabulary in RDF Drafts Published
2008-@@-@@: The Evaluation and Repair Tools Working Group today published Representing Content in RDF as a First Public Working Draft. This document provides a vocabulary to represent content in RDF, and is flexible for any type of content available on the Web or in local storage media. The Working Group also published an an updated Working Draft of HTTP Vocabulary in RDF, which defines terms to allow HTTP headers that have been exchanged between a client and a server to be recorded in RDF. These documents can be used to extend the Evaluation and Report Language (EARL) 1.0 Schema, an RDF vocabulary to record test results such as those generated by Web accessibility evaluation tools. They are part of the EARL Specification. Learn more about the Web Accessibility Initiative.
Other title ideas:
- EARL Companion Documents Published
Other body ideas:
- The Evaluation and Repair Tools Working Group today published two companion documents to Evaluation and Report Language (EARL), a format to exchange, combine, and analyze results from different evaluation tools. Representing Content in RDF, First Public Working Draft, provides a vocabulary to represent content in RDF, and is flexible for any type of content available on the Web or in local storage media. HTTP Vocabulary in RDF, updated Working Draft, defines terms to allow HTTP headers that have been exchanged between a client and a server to be recorded in RDF. Read about the Web Accessibility Initiative.
WAI Highlight for home page & RSS feed:
For Review: EARL Companion Documents
The Evaluation and Repair Tools Working Group today published Representing Content in RDF as a First Public Working Draft, and an updated Working Draft of HTTP Vocabulary in RDF. These documents are companions to Evaluation and Report Language (EARL), a format to exchange, combine, and analyze results from different evaluation tools. See:
- Call for Review: EARL Companion Documents e-mail,
- Evaluation and Report Language (EARL) Overview,
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
Please send comments by 29 September 2008. (2008-09-08)
notes:
- title brainstorms
- body brainstorms
- .............. These documents support work on Evaluation and Report
Language (EARL)...
(instead of) These documents are companions to Evaluation and Report Language (EARL)...
- .............. These documents support work on Evaluation and Report
Language (EARL)...
WAI IG email:
Call for Review: EARL Companion Documents
Dear WAI Interest Group Participants,
The W3C WAI Evaluation and Repair Tools Working Group (ERT WG) invites you
to comment on two documents published @@ Month 2008:
- Representing Content in RDF
(Resource Description Framework), First Public Working Draft
<http://www.w3.org/TR/@@/>
- HTTP (HyperText Transfer Protocol) Vocabulary in RDF, updated Working
Draft
<http://www.w3.org/TR/HTTP-in-RDF/>
These documents are of particular interest to Web developers and researchers who are interested in software-supported evaluation and validation of Web sites, and in Semantic Web technologies to support evaluations. The ERT Working Group is particularly looking for feedback on [[@@shadi]]. Specific questions are also highlighted within the documents.
Please send comments by @@ Month 2008 to:
- ERT WG public mailing list
<public-wai-ert@w3.org>
"Representing Content in RDF" and "HTTP Vocabulary in RDF" are companion
documents to Evaluation and Report Language (EARL). EARL is a format to
exchange, combine, and analyze results from different Web accessibility
evaluation tools in a vendor-neutral and platform-independent format. It also
provides a vocabulary that can be used for other Web quality assurance testing
and validation. For more details on EARL and companion documents, see:
- Evaluation and Report Language (EARL) Overview
<http://www.w3.org/WAI/intro/earl.php>
The two documents published today are intended to become W3C Working Group
Notes (as opposed to W3C Recommendations Web standards). For a description of
the different types of W3C documents, milestones, and opportunities to
contribute to this work, see:
- How WAI Develops Accessibility Guidelines through the W3C Process
<http://www.w3.org/WAI/intro/w3c-process>
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Henry
On behalf of:
Shadi Abou-Zahra - W3C ERT WG Chair
notes:
WCAG20 Update September 2008
WAI Highlight for home page & RSS feed:
WCAG 2.0 Implementations: Most done, a few to go
Since publishing Web Content Accessibility Guidelines (WCAG) 2.0 as a Candidate Recommendation, the WCAG Working Group has been collecting and evaluating implementations (that is, examples of how real Web sites meet WCAG 2.0). We have implementions for almost all success critieria, and need a few more. For an updated list of implementations needed, see the Update in the WCAG 2 FAQ.
The WCAG Working Group is meeting 1-3 October 2008 to address remaining issues. We are still hoping to complete WCAG 2.0 in 2008, and will provide another status update by November. See How WAI Develops Accessibility Guidelines through the W3C Process for the steps needed to complete WCAG 2.0. (2008-09-30)
title brainstorms:
- WCAG 2.0 Implementatons: 100s done, a few to go...
- WCAG 2.0 Implementations Update: Almost
- WCAG 2.0 Update: Implementation Nearly Complete
- WCAG 2.0 Getting Closer...
- WCAG 2.0 Implementations Almost There
- WCAG 2.0 Implementations Coming Along Well
body brainstorms:
- instead of "We have implementions for almost all success critieria, and
need a few more."
maybe: "There are implementions for almost all success critieria, and a few more implementations are needed."
notes:
- See also the FAQ update draft
- previous blurbs:
WAI IG email:
Update on WCAG 2.0: Need a few more implementations
Dear WAI Interest Group Participants,
Since publishing Web Content Accessibility Guidelines (WCAG) 2.0 as a Candidate Recommendation, the WCAG Working Group has been collecting and evaluating implementations (that is, examples of how real Web sites meet WCAG 2.0). We have implementations for almost all success criteria, and need a few more.
We currently need implementations of at least the following WCAG 2.0 Success Criteria:
* 1.2.1 Audio-only and Video-only (Prerecorded) <http://www.w3.org/TR/2008/WD-UNDERSTANDING-WCAG20-20080430/media-equiv-av-only-alt.html>
* 1.2.7 Audio Description (Extended) <http://www.w3.org/TR/2008/WD-UNDERSTANDING-WCAG20-20080430/media-equiv-extended-ad.html>
* 2.2.5 Re-authenticating <http://www.w3.org/TR/2008/WD-UNDERSTANDING-WCAG20-20080430/time-limits-server-timeout.html>
For a comprehensive, updated list of implementations needed, see the WCAG 2
FAQ update at
<http://www.w3.org/WAI/WCAG20/wcag2faq.html#update1>
If you are able to provide implementations of these success criteria, please e-mail <team-wcag2-implementations@w3.org> and Loretta Guarino Reid at <lorettaguarino@google.com>.
Next Steps:
The WCAG Working Group is meeting face-to-face 1-3 October 2008 to address remaining issues. They are still hoping to complete WCAG 2.0 in 2008. We will provide another status update in October or November.
See How WAI Develops Accessibility Guidelines through the W3C Process for the steps needed to complete WCAG 2.0.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
notes:
WCAG 2.0 PR
last updated $Date: 2011/02/14 15:42:16 $
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):
Web Content Accessibility Guidelines (WCAG) 2.0 is a Proposed Recommendation
2008-11-03: The Web Content Accessibility Guidelines (WCAG) Working Group has published the Web Content Accessibility Guidelines 2.0 as a Proposed Recommendation, and published updated Working Drafts of Understanding WCAG 2.0,Techniques for WCAG 2.0, and How to Meet WCAG 2.0. WCAG defines how to make Web sites, Web applications, and other Web content accessible to people with disabilities. Read the announcement, Overview of WCAG 2.0 Documents, and about the Web Accessibility Initiative.
notes:
- @@Ian: Can we have the headline above for the general W3C
News blurb. And for the W3C Member Newsletter add "Call for Review" at the
beginning?
(If not, we strongly prefer not to have "Call for review" at all given that this is not a public call for review") - I assume that we have to have "Comments are welcome by 2 December." but am checking with Ian on this.
- WCAG CR blurb
- recent PR blurbs: SMIL,
DD
- other wordings of first sentence:"2008-01-29: The XML Core Working Group has published the Proposed Recommendation of Canonical XML 1.0"
- title: many of the PR news blurbs start with "Call for
Review" but not all of them. I assume that we don't want this to.
WAI Highlight for home page & RSS feed:
WCAG 2.0 succeeds in test sites, moves to last stage
Web Content Accessibility Guidelines (WCAG) 2.0 was published as a W3C Proposed Recommendation on 3 November 2008. This means that the technical material of WCAG 2.0 is complete and it has been implemented in real sites. The next stage is the final publication, which is expected in December 2008. Please see additional information in:
- WCAG 2.0 moves to last stage for expected final publication in December 2008
- How WAI Develops Accessibility Guidelines through the W3C Process
- Overview of WCAG 2.0 Documents
(2008-11-03)
notes:
- title brainstorms
- WCAG 2.0: One Short Step
Left
WCAG 2.0: One Short Step Away
WCAG 2.0: One Short Step Remaining - [jb: not entirely comfortable with this one, in case something goes wrong in the last stage.]
- WCAG 2.0 Nears the Finish
Line
WCAG 2.0 Reaches for the Finish Line
WCAG 2.0 Rounds the Last Bend - [jb: Any of the three above might work; the last one is better
because it has less of an implication of coming in slowly at the end of
a long marathon.] [slh; hum, I think "rounding the bend" sounds more
like a long marathon. where as "finish line" could be a short sprint.]
maybe:
- WCAG 2.0 Sprinting to the Finish Line
WCAG 2.0 Implementations Complete, Sprinting to the Finish Line - WCAG 2.0 Reaching for the Ribbon
- WCAG 2.0 Implementations Complete, Rounding the
Last Bend
WCAG 2.0 Implementations Complete, Preparing for Final Publication
WCAG 2.0 Implementations Complete; Member Review Starts - WCAG 2.0 Passes Implementations, Becomes Proposed Recommendation
- WCAG 2.0 Passes Implementations Stage/Tests/
WCAG 2.0 Passes Implementations Stage: Moves on
WCAG 2.0 Passes Implementations Stage: Moving on
WCAG 2.0 moves on after passing implementation stage
WCAG 2.0 Passes Implementations; Moves to Last Stage
WCAG 2.0 moves to last stage after passing implementations
WCAG 2.0 passes implementations and moves to last stage
WCAG 2.0 passes implementation tests and moves to last stage
WCAG 2.0 passes implementation trials and moves to last stage
passes beta tests
WCAG 2.0 passes beta test and moves to last stage
WCAG 2.0 passes "beta test" and moves to last stage - [slh thinks "member review starts" maybe too processy for headline... and maybe "Implementations Complete", also too jargony]
- WCAG 2.0 Implementations Complete: Last Step
- To PR: WCAG 2.0 Proves Implementable
- WCAG 2.0: One Short Step
Left
- I assume that we don't want to have in this blurb: "Comments are welcome by 2 December 2008."[jb: agreed]
WAI IG email:
WCAG 2.0 moves to last stage for expected final publication in December 2008
Dear WAI Interest Group Participants,
The Web Content Accessibility Guidelines (WCAG) Working Group announces the
publication of WCAG 2.0 as a W3C Proposed Recommendation on 03 November 2008.
WCAG 2.0 explains how to make Web sites, applications, and other content
accessible to people with disabilities, and older users.
http://www.w3.org/TR/2008/PR-WCAG20-20081103/
This means that the technical material of WCAG 2.0 is complete and it has
been implemented in real sites. Information about implementations and changes
since the last publications are available in the "Status of this Document"
section at:
http://www.w3.org/TR/2008/PR-WCAG20-20081103/#status
During this "Proposed Recommendation" stage, WCAG 2.0 is submitted to the
W3C membership for final review and endorsement. 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 next step is the final publication; which we expect in December
2008.*
W3C WAI encourages you to start implementing WCAG 2.0 now; see:
"What are the benefits of using WCAG 2.0?"
in the WCAG 2 FAQ
http://www.w3.org/WAI/WCAG20/wcag2faq-update.html#start
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/
While the focus of this stage is review by W3C Members, anyone can 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/
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.
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:
- [12:19] <shawn> moving towards the light. clear.
[12:19] <judy> stable
[12:19] <judy> implementations were neat! great!
[12:19] <shawn> ... stable. implementations
[12:20] <shawn> we're really serious, we mean it, it's really close,. use it now!
[12:21] <shawn> continues momentium towards
[12:22] <judy> completes next step towards expected finalization in december
[12:22] <judy> s/finalization/standard/whatever
[12:23] <shawn> Moves on to next step towards expected final publication in December 2008
[12:24] <shawn> Moves on towards expected final publication in December 2008
[12:24] <shawn> Moves to next step for expected final publication in December 2008 - WCAG 2.0 Advances to the Final Stage towards Completion
- WCAG 2.0 Implementations Complete, Preparing for Final Publication
- [12:19] <shawn> moving towards the light. clear.
W3C AC email:
"Announcement: The Director MUST announce the Call for Review to the Advisory Committee." - http://www.w3.org/2005/10/Process-20051014/tr.html#cfr
- Michael drafted.
W3C Q&A blog post:
With real world implementations WCAG 2.0 steps closer to expected December 2008 publication
Today W3C WAI published WCAG 2.0 as a "W3C Proposed Recommendation". This means that the technical material of WCAG 2.0 is complete and it has been used successfully in real websites. Up next: final publication as a Web standards "W3C Recommendation", which we expect in December!
Over the last few months, the Web Content Accessibility Guidelines (WCAG) Working Group has been going through a process to ensure that WCAG 2.0 can be implemented. Developers and dsigners from around the world gave WCAG 2.0 a "test drive" in their own Web content.
The result: Successful implementations in a wide range of sites including education, commerce, government, and a blog; in languages including Japanese, German, English, and French; and using a wide range of technologies including scripting, multimedia, Flash, and WAI-ARIA. You can get the nitty-gritty details from the Implementation Report.
We learned more about how people use WCAG 2.0 and got additional feedback that resulted in a few changes from the previous publication.
Now that WCAG 2.0 technical material is stable and is proven implementable, there's one more step: submit WCAG 2.0 Proposed Recommendation to W3C Members for final review and endorsement. That takes us into December.
Over the next few weeks we'll also be updating existing WCAG materials and providing new materials to help transitioning to WCAG 2.0; for example, a printable version of WCAG 2.0 at a Glance and more WCAG 2.0 presentations.
But you don't need to wait for any of that. There are a lot of reasons to start implementing WCAG 2.0 right away. See "What are the benefits of using WCAG 2.0?" in the WCAG 2 FAQ.
Note that the best place to start with WCAG 2.0 is not necessarily the technical standard itself. Instead start with:
- Overview of WCAG
2.0 Documents
- How to Meet WCAG
2.0: A customizable quick reference to WCAG 2.0
requirements...
As always, we welcome suggestions for improving these supporting documents, and we encourage translations. Each document has an e-mail address for comments, which is often in the footer, e.g., "Feedback welcome to wai-eo-editors@w3.org."
Thanks for all the support moving WCAG 2.0 towards completion. We look forward to seeing more websites and web applications meet WCAG 2.0.
notes:
- perhaps at the end:
Is WCAG 2.0 perfect? There's no such thing as perfect. Do we need WCAG 2.0 now? Yes. Will your website meet WCAG 2.0 soon? Go for it! ]] - Previous posts
- WCAG 2.0 takes a giant leap forward — Now it's your turn W3C Q&A blog post from April 2008
- Is WCAG 2.0 almost done?! W3C Q&A blog post from 12 December 2007
- title brainstorms:
- ...
NOTE: This information is an unapproved draft and should not be referenced or quoted under any circumstances.
ATAG October 2008
W3C Home Page (and Newsletters):
Authoring Tool Accessibility Guidelines (ATAG) 2.0: Updated Working Draft
2008-11-24: The Authoring Tool Accessibility Guidelines Working Group has published an updated Working Draft of the Authoring Tool Accessibility Guidelines (ATAG) 2.0. ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to the Web Content Accessibility Guidelines. ATAG also defines how to make authoring tools accessible so that people with disabilities can use them. Read the invitation to review the ATAG 2.0 Working Draft and about the Web Accessibility Initiative.
notes:
WAI Highlight for home page & RSS feed:
For Review: ATAG 2.0 Updated Working Draft
An updated Authoring Tool Accessibility Guidelines (ATAG) 2.0 Working Draft was published 24 November 2008. ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to the Web Content Accessibility Guidelines. ATAG also defines how to make authoring tools accessible so that people with disabilities can use them. WAI encourages you to review ATAG 2.0 and submit any comments. See:
- Call for Review: ATAG 2.0 Working Draft Updated,
- Authoring Tool Accessibility Guidelines (ATAG) Overview.
Please send comments by 6 January 2008. (2008-11-24)
notes:
WAI IG email:
Call for Review: ATAG 2.0 Working Draft updated
Dear WAI Interest Group participants,
The Authoring Tool Accessibility Guidelines Working Group invites you to
comment on the updated Authoring Tool Accessibility Guidelines (ATAG) 2.0
Working Draft published 24 November 2008 at:
http://www.w3.org/TR/ATAG20/
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
The group has refocused Part A, which addresses authoring tool user interface accessibility, and restructured Part B to replace the concept of "Web Content Accessibility Benchmark" with a more straightforward relationship with WCAG 2.0. The group welcomes feedback on these changes.
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 by 6 January 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/
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry and Judy Brewer
On behalf of:
Jutta Treviranus, Chair of AUWG, and Director of the Assistive Technology
Research Center, University of Toronto)
Jeanne Spellman, W3C Staff Contact for AUWG
notes:
UAAG Sept 2008
W3C Home Page (and Newsletters):
User Agent Accessibility Guidelines (UAAG) 2.0: Updated Working Draft
2008-09-30: The User Agent Accessibility Guidelines Working Group has published an updated Working Draft of the User Agent Accessibility Guidelines (UAAG) 2.0. UAAG 2.0 addresses accessibility of browsers and media players and their interoperability with assistive technologies. 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 Updated Working Draft
An updated User Agent Accessibility Guidelines (UAAG) 2.0 Working Draft was published 30 September 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. WAI encourages you to review UAAG 2.0 and submit any comments. See:
- Call for Review: UAAG 2.0 Working Draft Updated,
- User Agent Accessibility Guidelines (UAAG) Overview.
Please send comments by @@ Month 2008. (2008-09-30)
notes:
WAI IG email:
Call for Review: UAAG 2.0 Working Draft updated
Dear WAI Interest Group participants,
The User Agent Accessibility Guidelines Working Group invites you to comment
on an updated Working Draft of User Agent Accessibility Guidelines (UAAG) 2.0,
published 30 September 2008 at:
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
[[ @@ section on current status and what to focus on for this round of review and comment @@ ]]
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 draft, and to consider
more active participation in the development process. Please send comments by
@@ Month 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/
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
notes:
WAI ARIA February 2009
W3C Home Page (and Newsletters):
Last Call: Accessible Rich Internet Applications (WAI-ARIA); Best
Practices and Implementation Guide Drafts Also Published
2009-02-24: The Protocols
and Formats Working Group published the Last Call Working Draft of Accessible Rich Internet Applications
(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.
The Working Group also published a First Public Working Draft of the WAI-ARIA User Agent Implementation Guide that provides guidance on how browsers and other user agents should expose WAI-ARIA features to platform accessibility APIs. The updated Working Draft of WAI-ARIA Best Practices that was published today describes how Web content developers can develop accessible rich Web applications using WAI-ARIA.
These WAI-ARIA documents are described in the WAI-ARIA Overview. Read details in the review announcement, and about the Web Accessibility Initiative (WAI).
notes:
- Last Call: Accessible Rich Internet Applications (WAI-ARIA), and
WAI-ARIA User Agent Implementation Guide
[@@Ian suggested putting these 3 publications in one blurb, but I'm not sure how to do the headline -- epsecially since we really want to call attention to the Last Call and probably also to the FPWD...]
Ian proposes: Last Call for WAI-ARIA; Best Practices and Implementation Guide Drafts Also Published
(Michael OK with not highlighting the Implementation Guide more) - Aug 2008 blurb, Feb 2008 blurb
- recent W3C Last Call blurbs XSD, widgets
WAI Highlight for home page & RSS feed:
For Review: WAI-ARIA Last Call
WAI has published the Last Call Working Draft of WAI-ARIA, the Accessible Rich Internet Applications technical specification. This Last Call is provided for public review of the document with all resolutions from previous comments incorporated. See:
- Call for Review: WAI-ARIA Last Call and New Document for Browsers announcement e-mail;
- WAI-ARIA Overview, which links to WAI-ARIA FAQ and related documents for Web site developers and browser developers;
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
Please send comments by 24 March 2009. (2009-02-24)
For Review: New WAI-ARIA document for browsers
WAI has published the First Public Working Draft of the WAI-ARIA User Agent Implementation Guide that describes how browsers and other user agents should support the Accessible Rich Internet Applications (WAI-ARIA) technical specification, particularly how they should expose WAI-ARIA features to platform accessibility APIs. See:
- Call for Review: WAI-ARIA Last Call and New Document for Browsers announcement e-mail,
- WAI-ARIA Overview.
Please send comments by 24 March 2009. (2009-02-24)
WAI IG email:
[subject:] Call for Review: WAI-ARIA Last Call and New Document for Browsers
Dear WAI Interest Group Participants
The Protocols and Formats Working Group invites you to review the following
documents published 24 February 2009:
* Accessible Rich Internet Applications (WAI-ARIA) 1.0 - Last Call Working
Draft
http://www.w3.org/TR/wai-aria/
* WAI-ARIA User Agent Implementation Guide - First Public Working Draft
http://www.w3.org/TR/wai-aria-implementation/
* WAI-ARIA Best Practices - updated Working Draft
http://www.w3.org/TR/wai-aria-practices/
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 (also known as AJAX), HTML, JavaScript, and related technologies.
The WAI-ARIA User Agent Implementation Guide provides guidance on how browsers and other user agents should expose WAI-ARIA features to platform accessibility APIs.
WAI-ARIA Best Practices describes how Web content developers can develop accessible rich internet applications using WAI-ARIA.
For an introduction to WAI-ARIA and links to related documents for Web site
developers, please see:
* WAI-ARIA Overview
http://www.w3.org/WAI/intro/aria
* WAI-ARIA FAQ
http://www.w3.org/WAI/aria/faq
Last Call Status:
The main WAI-ARIA technical specification is provided as a *Last Call
Working Draft* for public review of the document now that it has all
resolutions from previous comments incorporated. The Working Group hopes that
it has resolved all substantive issues with this draft, and looks forward to
progressing to the next stages in completing WAI-ARIA. The next stages are
described in:
* How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
Please send any comments
* by 24 March 2009 to
public-pfwg-comments@w3.org
Note: Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Thank you in advance for your comments.
Regards,
Shawn Henry and Judy Brewer, W3C WAI
On behalf of:
Janina Sajka, Chair of PFWG
Michael Cooper, W3C WAI Staff Contact for PFWG
notes:
ATAG Jan 2009
W3C Home Page (and Newsletters):
Authoring Tool Accessibility Guidelines (ATAG) 2.0: Updated Working Draft
2009-01-@@: The Authoring Tool Accessibility Guidelines Working Group has published an updated Working Draft of Authoring Tool Accessibility Guidelines (ATAG) 2.0 that is synchronized with the finalized WCAG 2.0. ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content Accessibility Guidelines (WCAG) 2.0. ATAG also defines how to make authoring tools accessible so that people with disabilities can use them. Read the invitation to review the ATAG 2.0 Working Draft and about the Web Accessibility Initiative.
WAI Highlight for home page & RSS feed:
For Review: ATAG 2.0 Updated Working Draft
An updated Authoring Tool Accessibility Guidelines (ATAG) 2.0 Working Draft that is synchronized with the finalized WCAG 2.0 was published @@ January 2009. ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content Accessibility Guidelines (WCAG) 2.0. ATAG also defines how to make authoring tools accessible so that people with disabilities can use them. WAI encourages you to review ATAG 2.0 and submit any comments. See:
- Call for Review: ATAG 2.0 Working Draft Updated,
- Authoring Tool Accessibility Guidelines (ATAG) Overview.
Please send comments by @@ February 2009. (2009-01-@@)
WAI IG email:
Call for Review: ATAG 2.0 Working Draft updated
Dear WAI Interest Group participants,
The Authoring Tool Accessibility Guidelines Working Group invites you to
comment on the updated Authoring Tool Accessibility Guidelines (ATAG) 2.0
Working Draft published @@ January 2009 at:
http://www.w3.org/TR/ATAG20/
ATAG defines how authoring tools should help Web developers produce Web
content that is accessible and conforms to Web Content Accessibility Guidelines
(WCAG) 2.0. 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
This Working Draft has minor updates to synchronize with the finalized WCAG
2.0 and to improve clarity. The Working Group is still seeking feedback on the
substantive changes of the 24 November 2008 Working Draft:
* Refocused Part A, which addresses authoring tool user interface
accessibility
* Restructured Part B to replace the concept of "Web Content Accessibility
Benchmark" with a more straightforward relationship with WCAG 2.0.
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 by @@ February
2009 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/
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry and Judy Brewer
On behalf of:
Jutta Treviranus, Chair of AUWG, and Director of the Assistive Technology
Research Center, University of Toronto)
Jeanne Spellman, W3C Staff Contact for AUWG
notes:
WCAG 2 Authorized Translations
W3C Home Page (and Newsletters):
Authorized Translations of WCAG 2.0 Target International Deployment
2009-02-03: The W3C Web Accessibility Initiative (WAI) announces Translations of Web Content Accessibility Guidelines (WCAG) 2.0, including draft Authorized W3C Translations. The Policy for Authorized W3C Translations provides a process for stakeholder review and designation as an official translation. Learn more about WCAG 2.0 Translations in-progress, WCAG 2.0, and the Web Accessibility Initiative (WAI).
title brainstorms:
- WCAG 2.0 Authorized Translations in Progress
- WCAG 2.0 Authorized Translations Planned
- WCAG 2.0 Authorized Translations under Development
- [15:02] <IanJ> how about more exciting headline:
[15:03] * shawn all for more exciting! :-) (see the ones below for ideas)
[15:03] <IanJ> Translator Community Sets Teeth into WCAG 2.0
[15:04] <IanJ> Volunteer Translators Help International Deployment of WCAG 2.0
[15:04] <IanJ> Volunteer Translators Speed International Deployment of WCAG 2.0
[15:04] <IanJ> Volunteer Translators Speed International Adoption of WCAG 2.0
[15:05] <shawn> I like the idea of more exciting headline; however, I think we want "Authorized Translations" to come thoruhg clearly. what abotu somthing like:
[15:05] <shawn> Translators Help International Deployment of WCAG 2.0 with Authorized Translations
[15:06] <IanJ> How about:
[15:06] <IanJ> Authorized Translations of WCAG 2.0 Expected to Help International Deployment
[15:07] * shawn likes, wonders if can be do w/o Expected...
[15:07] <IanJ> +1
[15:07] <IanJ> Authorized Translations of WCAG 2.0 Target International Deployment
[15:07] <IanJ> or
[15:07] <shawn> Authorized Translations of WCAG 2.0 Further International Deployment
[15:07] <IanJ> either one ok with me
[15:07] <shawn> target nice and active!
body brainstorms:
- ...including expected Authorized W3C Translations.
- ... provides a process for developing translations that are reviewed by stakeholders and officially recognized by W3C.
- ...30-day review periods will be announced on the WAI IG mailing list...
- ... French translation now in 30-day review period...
WAI Highlight for home page & RSS feed:
WCAG 2.0 Official in Multiple Languages
Web Content Accessibility Guidelines (WCAG) 2.0 will soon be available in several languages as W3C Authorized Translations. The Policy for Authorized W3C Translations provides a process for stakeholder review and designation as an official translation. Draft "Candidate Authorized Translations" available for review will be announced to the WAI Interest Group (IG) mailing list.
WCAG 2.0 Translations lists completed and planned translations, and links to more information on W3C translations. (2009-02-03)
title brainstorms:
- (see W3C news blurbs title brainstorms above)
body brainstorms:
- ... provides a process for developing translations that are reviewed by stakeholders and officially recognized by W3C.
- Web Content Accessibility Guidelines (WCAG) 2.0 will soon be available in
several languages as W3C Authorized Translations. See:
(2009-02-@@)
WAI IG email:
WCAG Authorized W3C Translations to make WCAG 2.0 official in multiple languages
Dear WAI Interest Group Participants,
W3C Web Accessibility Initiative (WAI) is pleased to announce that several
Authorized W3C Translations of Web Content Accessibility Guidelines (WCAG) 2.0
are being developed. Completed and planned translations are listed in
*WCAG 2.0 Translations* at:
http://www.w3.org/WAI/WCAG20/translations
Authorized W3C Translations are reviewed by stakeholders and then designated
as official translations, as defined in the *Policy for Authorized W3C
Translations* at:
http://www.w3.org/2005/02/TranslationPolicy
Draft "Candidate Authorized Translations" available for review will be
announced to the WAI Interest Group (IG) mailing list, described at:
http://www.w3.org/WAI/IG/#mailinglist
W3C encourages the translation of its specifications and resources into
different languages. For information on translating documents and links to
existing translations, see W3C Translations at:
http://www.w3.org/Consortium/Translation/
WAI particularly encourages the development of W3C Authorized Translations
of WCAG 2.0 and other technical specifications to facilitate their adoption and
implementation internationally. For a list of translation priorities, see
Translating WAI Documents at:
http://www.w3.org/WAI/translation
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry, W3C WAI Outreach Coordinator
Shadi Abou-Zahra, W3C WAI International Program Office Activity Lead
notes:
- (see W3C news blurbs title brainstorms above)
WAI IG email:
Call for Review: French WCAG 2.0 Candidate Authorized Translation
Dear WAI Interest Group Participants,
W3C Web Accessibility Initiative (WAI) invites you to review the draft
French translation of Web Content Accessibility Guidelines (WCAG) 2.0 at:
http://www.braillenet.org/accessibilite/wcag20/wcag20_fr/fr_WCAG20_25fev09.htm
Please send your comments in French or English to:
public-auth-trans-fr@w3.org
by *2 April 2009*
Comments are publicly archived at
http://lists.w3.org/Archives/Public/public-auth-trans-fr/
This draft translation is a "Candidate Authorized Translation" developed
under the Policy for Authorized W3C Translations, which provides a process for
stakeholder review and designation as an official translation, described at:
http://www.w3.org/2005/02/TranslationPolicy
WAI encourages the development of W3C Authorized Translations of WCAG 2.0
and other technical specifications to facilitate their adoption and
implementation internationally. Completed and planned WCAG 2.0 Translations are
listed at:
http://www.w3.org/WAI/WCAG20/translations
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry, W3C WAI Outreach Coordinator
Shadi Abou-Zahra, W3C WAI International Program Office Activity Lead
notes:
- (see W3C news blurbs title brainstorms above)
ERT pubs February 2009
last updated $Date: 2011/02/14 15:42:16 $
W3C Home Page (and Newsletters):
Pointer Methods in RDF: First Draft Published
2009-03-10: The Evaluation and Repair Tools Working Group today published Pointer Methods in RDF as a First Public Working Draft. This document provides a framework for representing pointers to identify locations in content or portions of content, using Resource Description Framework (RDF). This document is part of Evaluation and Report Language (EARL) and can be used to extend the EARL 1.0 Schema. Read the invitation to review Pointer Methods in RDF and learn more about the Web Accessibility Initiative (WAI).
Other title ideas:
- Pointer Methods in RDF: EARL Companion Document Published
Other body ideas:
- ....
WAI Highlight for home page & RSS feed:
For Review: Pointer Methods in RDF (EARL Companion Document)
WAI has published Pointer Methods in RDF as a First Public Working Draft. This document provides a framework for representing pointers to identify locations in content or portions of content, using Resource Description Framework (RDF). It is a companion to Evaluation and Report Language (EARL), a format to exchange, combine, and analyze results from different evaluation tools. See:
- @@Call for Review: Pointer Methods in RDF e-mail,
- Evaluation and Report Language (EARL) Overview,
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
Please send comments by 7 April 2009. (2009-03-10)
notes:
WAI IG email:
Call for Review: Pointer Methods in RDF (EARL Companion Document)
Dear WAI Interest Group Participants,
The W3C WAI Evaluation and Repair Tools Working Group (ERT WG) invites you
to comment on a First Public Working Draft published 10 March 2009:
Pointer Methods in RDF
http://www.w3.org/TR/Pointers-in-RDF/>
This document provides a framework for representing pointers to identify locations in content or portions of content, using Resource Description Framework (RDF). It is of particular interest to Web developers and researchers who are interested in software-supported evaluation and validation of Web sites, and in Semantic Web technologies to support evaluations.
The ERT Working Group is particularly looking for feedback on:
* The extent to which the ERT WG is following best practices for the
description and publication of new vocabularies
* The practicality of the use cases suggested in section 1.3 as well as other
possible use cases not listed
* Other pointer methods not discussed by this document
Please send comments by 7 April 2009 to:
ERT WG public mailing list
public-wai-ert@w3.org
Pointer Methods in RDF is a companion document to Evaluation and Report
Language (EARL). EARL is a format to exchange, combine, and analyze results
from different Web accessibility evaluation tools in a vendor-neutral and
platform-independent format. It also provides a vocabulary that can be used for
other Web quality assurance testing and validation. For more details on EARL
and companion documents, see:
Evaluation and Report Language (EARL) Overview
http://www.w3.org/WAI/intro/earl.php
Pointer Methods in RDF is intended to become a W3C Working Group Note (as
opposed to a W3C Recommendation). For a description of the different types of
W3C documents along with milestones and opportunities to contribute to this
work, see:
How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process>
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Henry and Judy Brewer, W3C WAI
On behalf of:
Mike Squillace, IBM, ERT WG Co-Chair
Shadi Abou-Zahra, W3C, ERT WG Co-Chair
notes:
UAAG Sept 2008
Mar 2009
W3C Home Page (and Newsletters):
User Agent Accessibility Guidelines (UAAG) 2.0: Updated Working Draft
2009-03-11: The User Agent Accessibility Guidelines Working Group has published an updated Working Draft of the User Agent Accessibility Guidelines (UAAG) 2.0. UAAG defines how browsers, media players, and other "user agents" should support accessibility for people with disabilities and work with assistive technologies. 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 Updated Working Draft
WAI has published an updated User Agent Accessibility Guidelines (UAAG) 2.0 Working Draft. UAAG defines how browsers, media players, and other "user agents" should support accessibility for people with disabilities and work with assistive technologies. WAI encourages you to review UAAG 2.0 and submit any comments, particularly on keyboard accessibility and defining Web applications as user agents. See:
- @@Call for Review: UAAG 2.0 Working Draft Updated,
- User Agent Accessibility Guidelines (UAAG) Overview.
Please send comments by 22 April 2009. (2009-03-11)
notes:
WAI IG email:
Call for Review: UAAG 2.0 Working Draft updated
Dear WAI Interest Group participants,
The User Agent Accessibility Guidelines Working Group invites you to comment
on an updated Working Draft published 11 March 2009:
User Agent Accessibility Guidelines (UAAG) 2.0
http://www.w3.org/TR/UAAG20/
UAAG defines how browsers, media players, and other "user agents" should
support accessibility for people with disabilities and work with assistive
technologies. UAAG is introduced in:
UAAG Overview
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), which are listed in:
WAI Guidelines and Techniques
http://www.w3.org/WAI/guid-tech.html
Changes in the updated UAAG 2.0 Working Draft include:
* defining Web applications as user agents,
* expanded coverage of keyboard access,
* how assistive technologies interact with emerging technologies.
The Working Group is looking for feedback on these changes along with the
specific questions that are listed in the Status section at:
http://www.w3.org/TR/UAAG20/#status
WAI encourages people with disabilities and developers of browsers,
assistive technologies, plug-ins, extensions, and accessibility APIs
(application programming interfaces) to provide feedback on this draft, and to
consider more active participation in developing UAAG 2.0. Please send comments
to the publicly archived list:
public-uaag2-comments@w3.org
by 22 April 2009
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/
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Henry and Judy Brewer, W3C WAI
On behalf of UAAG Working Group Chairs
notes:
Referencing TR docs
DRAFT: Referencing WAI Guidelines and Technical Reports
WAI Highlight for home page & RSS feed:
Which links to what: Referencing WCAG, ATAG, UAAG, and WAI-ARIA
Ever wonder which URI (Web address) you should use for links to WCAG or other WAI technical documents? To learn which URI to use for what, which have stable content, and which give you the latest version, see Referencing and Linking to WAI Guidelines and Technical Documents. (2009-03-12)
title brainstorms:
- Which links to what: Referencing WCAG and other WAI technical documents
WAI IG email:
Referencing and Linking to WCAG and other WAI technical documents
Dear WAI Interest Group Participants,
Ever wonder which URI (Web address) you should use for links to WCAG, ATAG, UAAG, WAI-ARIA, or other WAI technical documents? What if you want to reference the latest version? What if you want to point to a specific section within a technique?
To learn which URI to use for what, which have stable content, and which
give you the latest version, see:
*Referencing and Linking to WAI Guidelines and Technical
Documents*
http://www.w3.org/WAI/intro/linking.html
Let us know if you have any questions.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Henry, W3C WAI Outreach Coordinator, EOWG Chair
notes:
- More WAI highlights are available on the WAI home page:
http://www.w3.org/WAI/#highlights
via RSS feed from:
http://www.w3.org/WAI/highlights/about-rss.html
and archived at:
http://www.w3.org/WAI/highlights/archive ...
How PWD Use Web Intro page April 2009
WAI Highlight for home page & RSS feed:
How People with Disabilities Use the Web - Draft Introduced
"How People with Disabilities Use the Web" provides detailed examples of people with different disabilities using Web sites, applications, browsers, and authoring tools. It is currently a draft, and will soon be updated to reflect current best practice. Introduction to "How People with Disabilities Use the Web" provides a stable reference that will always link to the latest version of the main document. (2009-04-22)
notes:
- I prefer to keep this short, and point elsewhere for more info. I'm not sure if need to point to WAI IG email, or not - since the info there is in the documents themselves?
body brainstorms:
- pervious version:
Introduction to "How People with Disabilities Use the Web" introduces detailed examples of people with different disabilities using Web sites, applications, browsers, and authoring tools. Information on linking to the latest version of the main document is in a WAI IG e-mail. - ? do we need the phrase in brackets:
Introduction to "How People with Disabilities Use the Web" introduces [a document that provides] detailed examples of people with different disabilities using Web sites,...
- alt last sentence:
...See the WAI IG e-mail with information on referencing and linking to the latest version of the document.
WAI IG email:
New page introduces How People with Disabilities Use the Web
Dear WAI Interest Group Participants,
The W3C WAI Education and Outreach Working Group (EOWG) has published:
Introduction to "How People with Disabilities Use the Web"
http://www.w3.org/WAI/intro/people-use-web
The main "How People with Disabilities Use the Web" draft document provides detailed examples of people with different disabilities using websites, applications, browsers, and authoring tools. The document will soon be updated to reflect current best practice. The Introduction page linked above provides a stable reference link to get to the latest version of the main document.
Please do not link to, reference, or quote the draft of the main document
because it is currently an unapproved internal draft and some of the techniques
and terminology are out-of-date; for example, WCAG 2.0 is now recommended
instead of WCAG 1.0.
Instead, please link to the _Introduction to "How People with Disabilities Use
the Web"_ page <http://www.w3.org/WAI/intro/people-use-web>, which will
always point to the latest version of the main document.
We expect to have an updated draft of the main document in 2009.
Please feel free to circulate this message, avoiding cross-postings where possible.
Regards,
~Shawn Lawton Henry, EOWG Chair
[]
notes:
Tweet (140 characters)
"How People with Disabilities Use the Web" Introduction published http://tinyurl.com/pwd-web WAI IG email on it http://tinyurl.com/IG0422
(above is 137 characters)
EARL 2009 04April 28
W3C Home Page (and Newsletters):
Evaluation and Report Language (EARL) 1.0 Schema: Working Draft Published
2009-04-28: The Evaluation and Repair Tools Working Group (ERT WG) today published an updated Working Draft of Evaluation and Report Language (EARL) 1.0 Schema. This document provides the formal schema of EARL 1.0, a vocabulary to express test results. EARL is a format to exchange, combine, and analyze results from different evaluation tools. Read the [@@@] invitation to review EARL 1.0 Schema and learn more about the Web Accessibility Initiative (WAI).
notes:
title brainstorms:
- ...
body brainstorms:
- ...
WAI Highlight for home page & RSS feed:
For Review: Evaluation and Report Language (EARL) 1.0 Schema
WAI has published an updated Working Draft of Evaluation and Report Language (EARL) 1.0 Schema. This document provides the formal schema of EARL 1.0, a vocabulary to express test results. EARL is a format to exchange, combine, and analyze results from different evaluation tools. See:
- Call for Review: Evaluation and Report Language (EARL) 1.0 Schema e-mail
- Evaluation and Report Language (EARL) Overview
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute
Please send comments by 26 May 2009. (2009-04-28)
notes:
title brainstorms:
- ...
body brainstorms:
- ...
WAI IG email:
Call for Review: Evaluation and Report Language (EARL) 1.0 Schema
Dear WAI Interest Group Participants,
The W3C WAI Evaluation and Repair Tools (ERT) Working Group invites you to
comment on an updated Working Draft published on 28 April 2009:
Evaluation and Report Language (EARL) 1.0 Schema
http://www.w3.org/TR/EARL10-Schema/
This document provides the formal schema of the Evaluation and Report Language (EARL) 1.0, a vocabulary to express test results. It is of particular interest to Web developers and researchers who are interested in software-supported evaluation and validation of Web sites, and in Semantic Web technologies to support evaluations.
The ERT Working Group is particularly looking for feedback on:
Adoption of foaf:Document external link as a further refinement for
earl:TestSubject (see Editor's note 1)
Providing subclasses for earl:TestMode, similarly to the approach taken by
earl:OutcomeValue (see Editor's note 2)
Replacing or partially replacing earl:Software with terms from the DOAP
vocabulary (see Editor's note 3)
Structure and clarity of the entire conformance section (see Editor's note 4,
5, and 6)
Please send comments by 26 May 2009 to:
ERT WG public mailing list
public-wai-ert@w3.org
EARL is a format to exchange, combine, and analyze results from different
Web accessibility evaluation tools in a vendor-neutral and platform-independent
format. It also provides a vocabulary that can be used for other Web quality
assurance testing and validation. For more details on EARL and its companion
documents, see:
Evaluation and Report Language (EARL) Overview
http://www.w3.org/WAI/intro/earl.php
EARL 1.0 Schema is intended to become a W3C Recommendation after further
refinement. For a description of the different types of W3C documents,
milestones and opportunities to contribute to this work, see:
How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry
On behalf of:
Mike Squillace, IBM, ERT WG Co-Chair
Shadi Abou-Zahra, W3C, ERT WG Co-Chair
notes:
(above is @@ characters)
QA blog on translations & referncing docs
Pointers to WAI Overview documents - a note from SXSW and CSUN
One of the treats from <SXSW and <CSUN this year has been hearing other people presenting on <WAI-ARIA and <WCAG 2. Interest is growing, even though we've still got a long way to go on awareness, adoption, and implementation throughout the web development community.
One issue I noted is that the main pointer is different for beginners than for the presenters who work with the specification regularly. If you're new to these, start with the Overview pages (WCAG Overview and WAI-ARIA Overview). That's the URI that presenters should usually give out.
On a related note, with the publication of WCAG 2, we noted the need to clarify the system for links to different versions. Check out <Referencing and Linking to WAI Guidelines and Technical Documents to learn which URI to use for what, which have stable content, and which give you the latest version. This also applies to <WAI-ARIA, <ATAG, and <UAAG.
Another treat from the conferences was getting re-energized for education and outreach. Look for some new material in the coming weeks and let us know how we can support your efforts to @@
@@ pointing out how it's cool for developers and pwds
ATAG May 2009
W3C Home Page (and Newsletters):
Authoring Tool Accessibility Guidelines (ATAG) 2.0: Updated Working Draft
2009-05-21: The Authoring Tool Accessibility Guidelines Working Group has published an updated Working Draft of Authoring Tool Accessibility Guidelines (ATAG) 2.0 in preparation for the Last Call Working Draft. ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content Accessibility Guidelines (WCAG) 2.0. ATAG also defines how to make authoring tools accessible so that people with disabilities can use them. Read the invitation to review the ATAG 2.0 Working Draft and about the Web Accessibility Initiative.
WAI Highlight for home page & RSS feed:
For Review: ATAG 2.0 Updated Working Draft
An updated Authoring Tool Accessibility Guidelines (ATAG) 2.0 Working Draft was published 21 May 2009. The Working Group expects the next publication to be the Last Call Working Draft. ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content Accessibility Guidelines (WCAG) 2.0. ATAG also defines how to make authoring tools accessible so that people with disabilities can use them. WAI encourages you to review ATAG 2.0 and submit any comments. See:
- Call for Review: ATAG 2.0 Working Draft updated,
- Authoring Tool Accessibility Guidelines (ATAG) Overview.
- How WAI Develops Accessibility Guidelines through the W3C Process
Please send comments by 11 June 2009 so that the Working Group can review the comments at their face to face meeting on 15 June. (2009-05-21)
WAI IG email:
Call for Review: ATAG 2.0 Working Draft updated
Dear WAI Interest Group participants,
The Authoring Tool Accessibility Guidelines Working Group invites you to
comment on the updated Authoring Tool Accessibility Guidelines (ATAG) 2.0
Working Draft published 21 May 2009 at:
http://www.w3.org/TR/ATAG20/
The group expects the next publication to be the Last Call Working Draft, and therefore requests that all interested parties read this draft and submit comments by 11 June so that the comments can be reviewed at the working group face to face meeting on 15 June.
ATAG defines how authoring tools should help Web developers produce Web
content that is accessible and conforms to Web Content Accessibility Guidelines
(WCAG) 2.0. 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
This Working Draft includes substantial changes including:
* how automated tools should address alternative text (e.g. alt text for photo
repository sites)
* expanded examples of authoring tools in the Introduction
* a complete revision of the Glossary
Specific changes and questions for feedback are listed in the Status
section:
http://www.w3.org/TR/ATAG20/#status
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 by 11 June 2009
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/
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry and Judy Brewer
On behalf of:
Jutta Treviranus, Chair of AUWG, and Director of the Assistive Technology
Research Center, University of Toronto)
Jeanne Spellman, W3C Staff Contact for AUWG
notes:
(above is @@ characters)
Mobile-Accessible Overlap
W3C Home Page (and Newsletters):
Relationship Between Mobile Web and Web Content Accessibility Working Draft Published
2009-05-26: The Mobile Web Best Practices Working Group and the WAI Education and Outreach Working Group have published an updated Working Draft of Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG). This draft is complete and is provided as a last chance for public review and comment before publication as a W3C Working Group Note. See the announcement email.
The groups encourage people to start by reading Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices, which shows how design goals for accessibility and mobile access overlap. A third document, Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities, provides examples of barriers that people (without disabilities) face 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:
- previous blurb, first blurb
- more notes from before
- These documents describe the overlap between design goals and guidelines covering accessibility for people with disabilities and for mobile devices.
WAI Highlight for home page & RSS feed:
For Review: Accessible-Mobile Overlap Document
Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) Working Draft is ready for review. This draft is complete and is provided as a last chance for public review and comment before publishing it as a W3C Working Group Note. See:
- Call For Review: 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.
Please send comments by 16 June 2009. (2009-05-26)
WAI IG e-mail:
http://lists.w3.org/Archives/Public/w3c-wai-ig/2009AprJun/0127.html
MWI BPWG Blog &/or Q&A Post:
Shawn not doing
bcase2009june
emails:
messages to get across:
- this bcase update more clearly includes the impact of web accessibility on older users
- older people are a growing market and an important target group, thus an important aspect of many business cases
- update was done as part of the WAI-AGE project
previous question: this will be included in the WAI IG email, which is pointed to from the WAI highlight. does it have to be included in the WAI highlights as well? (slh would prefer not) [AA-probably] in the tweet? [AA-no]. [saz: I'm not sure if it essential but I'd certainly prefer it, as we also want to promote the WAI-AGE Project itself (to attract more end-user participation). I like the blurbs as they currently are, I think you weaved it in very well.] - this update also includes WCAG 2.0 references. WCAG 2.0 better addresses older users' needs
- suggestions for new appendix of case studies, statistics, etc.
- minor point: next update will include mobile
notes:
- Shawn would prefer waiting to do the W3C new blurb until after the Appendix is added; however willing to consider if it's felt important to do now. Please note that If we do it now, it probably won't be appropriate to do another one with the update in a few weeks that includes the Appendix, which is something I want people to see...
- Draft:
Developing a Web Accessibility Business Case for Your Organization - Update Published
2009-@@-@@: The WAI Education and Outreach Working Group (EOWG) published Developing a Web Accessibility Business Case for Your Organization, updated as part of the WAI-AGE Project. This update more thoroughly addresses the impact of Web accessibility on older users, an increasing market segment and an important target group for many organizations. It also includes references to the new WCAG 2. Read details on recent and upcoming updates to this business case and about the Web Accessibility Initiative (WAI).
WAI Highlight for home page & RSS feed:
Business Case Updated: Impact of Older Web Users Expanded
Developing a Web Accessibility Business Case for Your Organization is updated to more thoroughly address the impact of Web accessibility on older users, as part of the WAI-AGE Project.Older users are an increasing market segment and an important target group for many organizations. This update also includes references to the new WCAG 2. Get more details on recent and upcoming updates from the WAI IG e-mail. (2009-06-25)
notes:
title brainstorms:
- Older demographics enhance the Web accessibility business case
- Business Case Updated: Impact of Older Web Users
- Web Accessibility Business Case updated
- Older people are important for Web accessibility
- Older people are an important argument for Web accessibility
- Are older people in your target audience?
- Older population online - more reasons than ever to adopt Web accessibility
Is your grandma online? Older people enhance the business case for Web accessibility
body brainstorms:
- wai ig e-mail link options:
- Get more details on recent and upcoming updates from the WAI IG e-mail.
- Get more details on recent and upcoming updates from the Business Case updated with expanded coverage of older Web users and WCAG 2.0 e-mail.
- previous version: Developing a Web Accessibility Business Case for Your Organization is updated to more thoroughly address the impact of Web accessibility on older users, an increasing market segment and an important target group for many organizations. It also includes references to the new WCAG 2. Get more details on recent and upcoming updates from the WAI IG e-mail. (2009-06-25)
- If need to point to WAI-AGE:
- Developing a Web Accessibility Business Case for Your Organization is updated to more thoroughly address the impact of Web accessibility on older users, as part of the WAI-AGE Project.Older users are an increasing market segment and an important target group for many organizations. This update also includes references to the new WCAG 2. Get more details...
- Developing a Web Accessibility Business Case for Your Organization is updated to more thoroughly address the impact of Web accessibility on older users, an increasing market segment and an important target group for many organizations. This update, which is part of the WAI-AGE Project, also includes references to the new WCAG 2. Get more details...
- Developing a Web Accessibility Business Case for Your Organization is updated to more thoroughly address the impact of Web accessibility on older users, an increasing market segment and an important target group for many organizations. This update also includes references to the new WCAG 2, and is part of the WAI-AGE Project. Get more details...
- from Andrew: <a>Developing a Web Accessibility Business
Case for Your Organization</a>: updated to more clearly include the
benefits of Web accessibility for older people, an increasing market
segment and an important target group for many organisations.
See <a>(wai-ig email)</a> for further details.
WAI IG email:
Business Case updated with expanded coverage of older Web users and WCAG 2.0
Dear WAI Interest Group Participants,
"Developing a Web Accessibility Business Case for Your Organization" has
been updated at:
http://www.w3.org/WAI/bcase/Overview.html
It covers the social, technical, financial, and legal and policy factors in the
business case for Web accessibility. Each section presents different aspects of
Web accessibility along with guidance on developing a customized business
case.
Recent updates:
* Most of the updates are to more thoroughly address the overlap between making
websites accessible for people with disabilities and better for older users.
*Older users are an increasing market segment and an important target
group for many organizations.* For some, making their website better
for older users is a key aspect in their business case for Web
accessibility.
* The references are updated to WCAG 2.0. (http://www.w3.org/WAI/intro/wcag) WCAG 2.0 more clearly covers
the accessibility needs of older users.
* For those who would like to see what changed with this update, a
change-marked version is available at: http://www.w3.org/WAI/EO/Drafts/bcase/Overview.html
* This update is part of the Web Accessibility Initiative: Ageing Education and
Harmonisation (WAI-AGE) Project, supported by the European Union's 6th Research
Framework Programme (FP6), described at: http://www.w3.org/WAI/WAI-AGE/
Future updates:
* Expand discussion of the overlap between making a website accessible for
mobile phones and for people with disabilities, and how that impacts the
business case for accessibility. (http://www.w3.org/WAI/mobile/)
* Create an Appendix that lists case studies, articles, and other supporting
material.
"Developing a Web Accessibility Business Case for Your Organization" is developed within WAI's Education and Outreach Working Group (EOWG), whose home page is: http://www.w3.org/WAI/EO/
About WAI-AGE:
WAI-AGE is a European Commission IST Specific Support Action, with the goal of
increasing accessibility of the Web for older people as well as for people with
disabilities. http://www.w3.org/WAI/WAI-AGE/
Feel free to circulate this message to other lists; please avoid cross-postings
as possible.
Regards,
~Shawn Lawton Henry, EOWG Chair
Andrew Arch, for the WAI-AGE Project http://www.w3.org/WAI/WAI-AGE
notes:
- original announcement e-mail in 2005
- previous question:
On behalf of:
The WAI-AGE Project http://www.w3.org/WAI/WAI-AGE
[@@usually we put the WG Chairs here. I'm comfortable putting nothing, or "WAI-AGE Project", or individuals' names, or such, if you think its important.] - subject brainstorms:
- Business Case updated with expanded coverage of older web users and WCAG 2.0
- Web Accessibility Business Case updated
- WAI-AGE updates Web Accessibility Business Case
- Web Accessibility Business Case updated by WAI-AGE
Tweet (140 characters)
Web Accessibility Business Case http://www.w3.org/WAI/bcase/ updated to cover older users more & WCAG 2, see http://tinyurl.com/bcase0906
notes:
- tiny URI goes to WAI IG announcement, which provides details such as WAI-AGE Project
- brainstorms:
- Web Accessibility Business Case http://www.w3.org/WAI/bcase/ updated to cover older users
& benefits more, see http://tinyurl.com/bcase0906
(139) - Business Case for Web Accessibility updated to more thoroughly cover
older users and benefits of accessibility http://tinyurl.com/bcase0906
(139) - impact of older users included in updated business case for web
accessibility http://tinyurl.com/bcase0906
thanks to WAI-AGE project
(132) - original drafts:
NOTE: strict limit of 140 characters (including spaces)
comment: below say benefits for older people, but maybe want to better focus on benefits for business case?- Web Accessibility Business Case has been updated to clearly
include the benefits of Web accessibility for older people - http://tinyurl.com/bcase@@
(145+ characters) - Web Accessibility Business Case update more clearly describes the
benefits of Web accessibility for older people - http://tinyurl.com/bcase@@
(139+ characters)
- Web Accessibility Business Case has been updated to clearly
include the benefits of Web accessibility for older people - http://tinyurl.com/bcase@@
- Web Accessibility Business Case http://www.w3.org/WAI/bcase/ updated to cover older users
& benefits more, see http://tinyurl.com/bcase0906
W3C Q&A blog post:
[probably not doing now - maybe once we've got the Appendix set up and are open to ideas for resources for it]
Webstock Videos 2008
WAI Highlight (for home page & RSS feed):
W@@
R@@ are available online:
- @@
- Shawn Henry interview at Webstock 08 @@ with captions and text transcript
(2008-03-@@)
WAI IG e-mail:
W@@
Dear WAI Interest Group Participants,
Two videos with WAI staff were recently posted online that you might be interested in.
1. @@
2. @@
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.
Regards,
Judy ?? Shadi
...
notes
French WCAG 2 Authorized Translation
announcement planning: e-mail: Announcing WCAG 2.0 Authorized Translations revisited
W3C Home Page (and Newsletters):
First Authorized Translation of WCAG 2.0 Published
2009-06-26: W3C announces the French Authorized Translation of Web Content Accessibility Guidelines (WCAG) 2.0, Règles pour l'accessibilité des contenus Web (WCAG) 2.0. It is the first of several planned WCAG 2.0 Translations: Brazilian Portuguese, Catalan, Chinese, Czech, Danish, Dutch, German, Hindi, Hungarian, Italian, Japanese, Korean, Portuguese, Russian, Spanish, Swedish, and other languages. Translations are listed on the WCAG 2.0 Translations page and announced via the WAI Interest Group mailing list and WAI RSS feed. Learn more about translating W3C documents, Policy for Authorized W3C Translations, WCAG 2.0, and the Web Accessibility Initiative (WAI).
notes:
- we want the headline & blurb to focus on all WCAG 2.0 Authorized Translations, and not "French" (since we won't be doing a W3C blurb for other languages)
- Ian "I don't think we need a home page item per translation. I am ok
with
doing a home page item for the first, then indicating where others will
be announced (and which ones are expected)." - http://lists.w3.org/Archives/Team/w3t-comm/2009May/0098.html
title brainstorms:
Keywords: WCAG 2.0, French, Authorized Translation, First
- First Authorized W3C Translation of WCAG 2.0 Completed
First Authorized WCAG 2.0 Translation: FrenchFirst WCAG 2.0 Authorized Translation: FrenchFirst WCAG 2.0 Authorized Translation in FrenchFrench Authorized W3C Translation of WCAG 2.0French Authorized Translation of WCAG 2.0French Authorized WCAG 2.0 TranslationAuthorized WCAG 2.0 Translation in French
body brainstorms:
- [previous draft] 2009-06-02: W3C announces French Authorized Translation of Web Content Accessibility Guidelines (WCAG) 2.0. It is the first in a series of upcoming WCAG 2.0 Translations, following the Policy for Authorized W3C Translations. Learn more about WCAG 2.0 and the Web Accessibility Initiative (WAI).
WAI Highlight for home page & RSS feed:
WCAG 2.0 in French: Authorized Translation Published
Règles pour l'accessibilité des contenus Web (WCAG) 2.0, the French Authorized Translation of Web Content Accessibility Guidelines (WCAG) 2.0, is now available, following completion of the W3C Authorized Translations process. WAI encourages translating WAI documents in all languages. See:
- WCAG 2.0 Translations for a list of other completed and planned translations,
- @@@WCAG 2.0 French Authorized Translation Published e-mail.
(2009-06-26)
notes:
- For this one, we do want to focus on "French" (since we will do WAI blurb for each language)
title brainstorms:
- WCAG 2.0 is a French Authorized Translation
- First Authorized W3C Translation of WCAG 2.0 Completed
- First Authorized WCAG 2.0 Translation: French
- First WCAG 2.0 Authorized Translation: French
- First WCAG 2.0 Authorized Translation in French
- French Authorized W3C Translation of WCAG 2.0
- French Authorized Translation of WCAG 2.0
- French Authorized WCAG 2.0 Translation
- Authorized WCAG 2.0 Translation in French
- ideas for last sentence:
- See WCAG 2.0 Translations for a list of other completed and planned translations - is your language there?
- You can check for your language in the WCAG 2.0 Translations list of other completed and planned translations.
- See WCAG 2.0 Translations for a list of other completed and planned translations, including Brazilian Portuguese, Catalan, Chinese, Czech, Danish, Dutch, German, Hindi, Hungarian, Italian, Japanese, Korean, Portuguese, Russian, Spanish, Swedish, and others.
- [previous draft]
Web Content Accessibility Guidelines (WCAG) 2.0 is now accompanied by a French Authorized Translation of WCAG 2.0. It is the first in a series of upcoming WCAG 2.0 Translations, following the Policy for Authorized W3C Translations. WAI welcomes and encourages Translating WAI Documents in all languages.
WCAG 2.0 Translations lists completed and planned translations, and links to more information on W3C translations. (2009-Jun-02)
WAI IG email:
WCAG 2.0 French Authorized Translation Published
Dear WAI Interest Group Participants,
W3C WAI is pleased to announce publication of the first Authorized Translation of Web Content Accessibility Guidelines (WCAG) 2.0:
Règles pour l'accessibilité
des contenus Web (WCAG) 2.0 (French)
http://www.w3.org/Translations/WCAG20-fr
Authorized W3C Translations are reviewed by stakeholders following the
*Policy for Authorized W3C Translations* process at:
http://www.w3.org/2005/02/TranslationPolicy
*WCAG 2.0 Translations lists other completed and planned translations*
including Brazilian Portuguese, Catalan, Chinese, Czech, Danish, Dutch, German,
Hindi, Hungarian, Italian, Japanese, Korean, Portuguese, Russian, Spanish,
Swedish, and others, at:
http://www.w3.org/WAI/WCAG20/translations
W3C encourages translation of specifications and resources into all
languages. For information on translating documents and links to existing
translations, see W3C Translations at:
http://www.w3.org/Consortium/Translation/
WAI particularly encourages the development of W3C Authorized Translations
of WCAG 2.0 and other technical specifications to facilitate their adoption and
implementation internationally. For a list of translation priorities, see
Translating WAI Documents at:
http://www.w3.org/WAI/translation
Additional perspectives are in the "WCAG 2.0 in your mother tongue" blog
post at:
http://www.w3.org/QA/@@
Feel free to circulate this message to other lists; please avoid cross-postings as possible.
Regards,
Shawn Lawton Henry, W3C WAI Outreach Coordinator
Shadi Abou-Zahra, W3C WAI International Program Office Activity Lead
notes:
- QUESTION: should we say more, such as the LTO and link to other stakeholders? [Shadi: No, I don' think this is needed. ]
- @@link to blog post if it's done by then
Tweet (140 characters)
"Règles pour l'accessibilité des contenus Web (WCAG) 2.0" the WCAG 2.0
French Translation is published. See http://tinyurl.com/wcag20french
[will link to WAI IG email] (139 characters)
Shadi (http://www.w3.org/People/shadi)
blogged "WCAG 2.0 in your mother tongue" at http://tinyurl.com/wcag20tongue
[will link to blog post] (114 characters)
(above is 139 characters)
WCAG 2.0 in your mother tongue
I come from Egypt, live in Austria, work in France, and when I start speaking, some people think I'm American. I speak fluent German and English, but no matter what I do, some expressions and thoughts will always be easier for me in Arabic than in any other language. The expression "mother tongue" hits it rather well - it is the language where I feel most home and safe, despite it getting a little rusty over the years.
Come to think of it, the majority of the human population is probably more comfortable in a language other than English. It happens to be that English is the working language of W3C (and most international organizations) but that does not mean that other languages are not equally welcome at W3C. In fact, W3C encourages volunteers to contribute their valuable time and effort to translation of W3C standards and other resources.
I'm particularly proud of the Policy for Authorized W3C Translations which allows the production of translations that are recognized by W3C. This is especially useful for W3C standards such as Web Content Accessibility Guidelines (WCAG) 2.0, which are read and used by a large number of people. Besides Web developers, WCAG 2.0 is also used by decision makers, researchers, accessibility advocates, and people with disabilities from around the world.
Today the W3C Web Accessibility Initiative (WAI) announced the publication of the French Authorized Translation of WCAG 2.0. It is the first Authorized Translation of WCAG 2.0 and we expect others in Brazilian Portuguese, Catalan, Chinese, Czech, Danish, Dutch, German, Hindi, Hungarian, Italian, Japanese, Korean, Portuguese, Russian, Spanish, Swedish, and more to follow. There are also several unofficial translations available and in progress. The WCAG 2.0 Translations page lists completed and planned translations.
While this is an impressive list of translations, it is still only a small fraction of all existing languages. For instance, I am looking forward to being able to read WCAG 2.0 in Arabic. If we want to support the diversity of languages and cultures on the Web then we must continue to develop and promote such translations. Please engage and help us promote translations for W3C standards such as WCAG 2.0 in all languages of a truly World Wide Web.
notes:
title brainstorms:
- WCAG 2.0 in multiple languages
- WCAG 2.0 in your mother tongue
- WCAG 2.0 authorized in French and many more to come
- ...
body brainstorms:
- ...
MWBP-WCAG-2009-July
W3C Home Page (and Newsletters):
Relationship Between Mobile Web (MWBP) and Web Content Accessibility (WCAG) Note Published
2009-07-09: The Mobile Web Best Practices Working Group and the WAI Education and Outreach Working Group have published Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) as a W3C Working Group Note. The groups encourage people to start by reading Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices, which shows how design goals for accessibility and mobile access overlap. A third document, Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities, provides examples of barriers that people (without disabilities) face 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 (MWI) and the Web Accessibility Initiative (WAI).
notes:
WAI Highlight for home page & RSS feed:
Accessible and Mobile: WACG-MWBP Overlap Document Published
Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) is published as a W3C Working Group Note. See also:
- Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices introductory page,
- Shared Web
Experiences: Barriers Common to Mobile Device Users and People
with Disabilities.
(2009-07-09)
notes:
- longer option:
Relationship between Mobile Web Best Practices (MWBP) and Web Content Accessibility Guidelines (WCAG) is published as a W3C Working Group Note. See also:
- Web Content Accessibility and Mobile Web: Making a Web Site Accessible Both for People with Disabilities and for Mobile Devices for or an introduction to the overlap between design goals and guidelines covering accessibility for people with disabilities, and design goals and best practices for mobile devices.
- Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities for examples of barriers that people (without disabilities) face when interacting with Web content via mobile devices, and similar barriers for people with disabilities using desktop computers.
WAI IG email:
Overlap between Mobile Web (MWBP) and Accessibility (WCAG) Published
Dear WAI Interest Group participants,
The Mobile Web Best Practices Working Group and the WAI Education and Outreach
Working Group published the W3C Working Group Note:
*Relationship between Mobile Web Best Practices (MWBP) and Web Content
Accessibility Guidelines (WCAG)* at:
http://www.w3.org/TR/mwbp-wcag
For an introduction to the overlap between design goals and guidelines
covering accessibility for people with disabilities, and design goals and best
practices for mobile devices, see:
*Web Content Accessibility and Mobile Web*: Making a Web Site
Accessible Both for People with Disabilities and for Mobile Devices, at:
http://www.w3.org/WAI/mobile/
For examples of barriers that people (without disabilities) face when
interacting with Web content via mobile devices, and similar barriers for
people with disabilities using desktop computers, see:
*Shared Web Experiences*: Barriers Common to Mobile Device
Users and People with Disabilities, at:
http://www.w3.org/WAI/mobile/experiences
Information about the Working Groups is available from:
- Mobile Web Best Practices Working Group
http://www.w3.org/2005/MWI/BPWG/
- Web Accessibility Initiative (WAI) Education and Outreach Working Group
http://www.w3.org/WAI/EO/
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
Shawn Lawton Henry, WAI EOWG Chair
Jo Rabin, MWI BPWG Co-Chair
Daniel Appelquist, MWI BPWG Co-Chair
Tweet (MAXIMUM 140 characters)
to make your website accessible & mobile friendly at the same time see http://www.w3.org/WAI/mobile/ W3C Note http://www.w3.org/TR/mwbp-wcag
(above is exactly 140 characters)
UAAG 2.0 2009 July
W3C Home Page (and Newsletters):
User Agent Accessibility Guidelines (UAAG) 2.0: Updated Working Draft
2009-07-23: The User Agent Accessibility Guidelines Working Group has published an updated Working Draft of the User Agent Accessibility Guidelines (UAAG) 2.0. UAAG defines how browsers, media players, and other "user agents" should support accessibility for people with disabilities and work with assistive technologies. Read the invitation to review the UAAG 2.0 Working Draft and about the Web Accessibility Initiative (WAI).
WAI Highlight for home page & RSS feed:
For Review: UAAG 2.0 Updated Working Draft
WAI has published an updated User Agent Accessibility Guidelines (UAAG) 2.0 Working Draft with updated Operability and Glossary sections. UAAG defines how browsers, media players, and other "user agents" should support accessibility for people with disabilities and work with assistive technologies. WAI encourages you to review UAAG 2.0 and submit any comments. See:
- Call for Review: UAAG 2.0 Working Draft updated@@ e-mail,
- User Agent Accessibility Guidelines (UAAG) Overview.
Please send comments by 9 September 2009. (2009-07-23)
WAI IG email:
Call for Review: UAAG 2.0 Working Draft updated
Dear WAI Interest Group Participants,
The User Agent Accessibility Guidelines Working Group invites you to comment
on an updated Working Draft published 23 July 2009:
User Agent Accessibility Guidelines (UAAG) 2.0
http://www.w3.org/TR/UAAG20/
UAAG defines how browsers, media players, and other "user agents" should
support accessibility for people with disabilities and work with assistive
technologies. UAAG is introduced in:
UAAG Overview
http://www.w3.org/WAI/intro/uaag.php
Changes in this Working Draft include:
* Operability section updated in response to comments
* Glossary rewritten
The Working Group is looking for feedback on these changes along with the
specific questions listed in the Status section at:
http://www.w3.org/TR/UAAG20/#status
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), which are listed in:
WAI Guidelines and Techniques
http://www.w3.org/WAI/guid-tech.html
WAI encourages people with disabilities and developers of browsers,
assistive technologies, plug-ins, extensions, and accessibility APIs
(application programming interfaces) to provide feedback on this draft, and to
consider more active participation in developing UAAG 2.0. Please send comments
to the publicly-archived list:
public-uaag2-comments@w3.org
by 91 September 2009
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/
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Henry and Judy Brewer, W3C WAI
On behalf of UAAG Working Group Chairs
notes:
- ...
Tweet (MAXIMUM 140 characters)
help make browsers more accessible – comment on updated UAAG User Agent
Accessibility Guidelines 2.0 draft. see http://tinyurl.com/UAAG090723
(139) [http://tinyurl.com/UAAG0907 to go to WAI IG email]
notes & brainstorms:
- point to wai ig email? overview? tr doc? (Shawn thinks not only the TR doc)
- Want a more accessible browser? Help - comment on updated UAAG User Agent
Accessibility Guidelines 2.0 draft http://www.w3.org/TR/UAAG20/
(137) - Want a more accessible browser? Comment on the latest working draft of
the User Agent Accessibility Guidelines 2.0. http://www.w3.org/TR/UAAG20/
(144)
aria-update-aug09
WAI Highlight for home page & RSS feed:
WAI-ARIA Update August 2009
The W3C WAI Protocols and Formats Working Group (PFWG) is more than halfway through resolving comments on the WAI-ARIA Last Call Working Draft published earlier this year. See:
- Status Update on WAI-ARIA Last Call Comments e-mail for details on current status;
- WAI-ARIA Overview;
- How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.
(2009-08-06)
notes:
WAI IG email:
WAI-ARIA Update August 2009
Dear WAI Interest Group Participants,
The W3C WAI Protocols and Formats Working Group (PFWG) is more than halfway through resolving comments on the WAI-ARIA Last Call Working Draft published earlier this year.
Accessible Rich Internet Applications (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 (also known as AJAX), HTML, JavaScript, and related technologies. For an introduction to WAI-ARIA and links to related documents, please see the WAI-ARIA Overview at:
http://www.w3.org/WAI/intro/aria
The Working Group will address all comments before responding to directly reviewers with the resolutions of their comments. In the meantime, reviewers can check on the general status of comments in the database at:
http://www.w3.org/WAI/PF/comments/
The Working Group plans to publish a "stabilization draft" and then a second Last Call Working Draft with a new formal public review period, in order to ensure they did not created new issues when addressing the existing ones. As usual, the new review period will be announced on this WAI IG mailing list, the WAI home page <www.w3.org>, RSS feed <http://www.w3.org/WAI/highlights/rssfeed.rss>, and microblogs <http://twitter.com/w3c_wai>.
Please let us know if you have any questions.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry
On behalf of:
Janina Sajka, Chair of PFWG
Tweet (MAXIMUM 140 characters)
Update on WAI-ARIA for Accessible Rich Internet Applications at http://tinyurl.com/aria98updat@@ Resolving comments, responses forthcoming.
(137)(tinyurl to go to WAI IG email)
other ideas:
- Update on WAI-ARIA for Accessible Rich Internet Applications http://tinyurl.com/aria98updat Will respond to comments, provide updated draft.
(140) - Update on WAI-ARIA for Accessible Rich Internet Applications is at http://tinyurl.com/aria98updat Resolving comments, new draft forthcoming
(140)
Techshare Workshop
WAI IG email:
Tutorial: Web Applications Enabled, 16 September, London
Dear WAI Interest Group Participants:
WAI is leading "Web Applications Enabled" on 16 September 2009 in London, UK, as a Techshare pre-conference workshop.
This tutorial is for developers who want to learn more about creating accessible web applications. Participants will gain:
- An understanding of WCAG 2.0 and WAI-ARIA accessibility standards
- Practical examples of WCAG 2.0 and WAI-ARIA implementation
- Techniques for developing accessible websites and web applications
Detailed information about the tutorial is available from:
http://www.w3.org/WAI/presentations/2009/techshare
Registration is via the Techshare 2009 website:
http://www.techshare.org.uk/
The *registration deadline is 1 September 2009*.
This message may be circulated to other lists; however, please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry, WAI Education and Outreach
notes:
- ...
Tweet (MAXIMUM 140 characters)
Web Applications Enabled Tutorial, 16 September, London, led by Michael Cooper http://tinyurl.com/techshare09 (registration deadline 1 Sept)
(140)(tinyuri probably to wai page)
notes & brainstorms:
- Tutorial: Web Applications Enabled, 16 September, London, led by Michael Cooper http://tinyurl.com/techshare09 registration deadline 1 Sept
(139) - Tutorial: Web Applications Enabled, 16 September, London – http://tinyurl.com/techshare09 – an RNIB Techshare workshop led by Michael Cooper
(140) - Tutorial: Web Applications Enabled, 16 September, London, led by Michael Cooper http://tinyurl.com/techshare09 register by 1 Sept
(131) - previous tweets
neww3cpage
WAI Highlight for home page & RSS feed:
New: Perspectives on Web Accessibility
Along with the redesigned W3C website, we have a new Accessibility page that introduces the what, why, where, and how of web accessibility. Read what it says about how the impact of disabilities can be radically changed for people using the Web when websites, web technologies, and web tools are properly designed. (2009-10-14)
notes:
- ...
title brainstorms:
- New Perspectives on Web Accessibility
New: Perspectives on Web Accessibility
New: Perspectives on Accessibility
body brainstorms:
- Judy: "Read what it says about how the impact of disabilities can be radically changed for people using the Web when websites, web technologies, and web tools are properly designed.
was: " Read what it says about how the impact of disability can be radically changed on the Web when websites, web technologies, and web tools are properly designed.
WAI IG email:
New: Perspectives on Accessibility
Dear WAI Interest Group Participants,
Along with the redesigned W3C website, we have a new Accessibility page that introduces the what, why, where, and how of web accessibility. Read what it says about how the impact of disabilities can be radically changed for people using the Web when websites, web technologies, and web tools are properly designed. See:
Accessibility - W3C
http://www.w3.org/standards/webdesign/accessibility
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry
WAI Outreach Coordinator, Education and Outreach Working Group (EOWG) Chair
-----
Shawn Lawton Henry
W3C Web Accessibility Initiative (WAI)
e-mail: shawn@w3.org
phone: +1.617.395.7664
about: http://www.w3.org/People/Shawn/
notes:
- ...
Tweet (MAXIMUM 140 characters)
new W3C Accessibility page http://bit.ly/accessibility-w3c says the impact of disabilities can be radically changed for people using the Web
(140)
notes & brainstorms:
- ...
(139)
notes:
- ...
title brainstorms:
- ...
body brainstorms:
- ...
WMA FAQ
...
WAI Highlight for home page & RSS feed:
W3C Shares Multimedia Accessibility FAQ
In order to help the community provide accessible multimedia, W3C made public it's internal Multimedia Accessibility FAQ. The FAQ provides some practical advice on: What do I need to do to make audio and video accessible? How do I get a transcript for my media? How do I do captions? Where can I get more information?
W3C's formal guidance on accessible multimedia is provided in Web Content Accessibility Guidelines (WCAG) 2.0. (2009-10-08)
notes:
- ...
title brainstorms:
- w3c shares experience on mm ax
practical notes on mm ax now available - W3C Multimedia Accessibility FAQ Revealed
W3C Multimedia Accessibility FAQ Gone Public
W3C Multimedia Accessibility FAQ Now Public
W3C Multimedia Accessibility FAQ is Public - Making Multimedia Accessible: A W3C FAQ
body brainstorms:
-
Multimedia accessibility is easier than you might think. For example, for most W3C audio and video, all we need to do is provide a simple text transcript. Transcripts are relatively cheap and easy. Do your podcasts include transcripts?
W3C has made it's internal frequently-asked-questions page public. See W3C Multimedia Accessibility FAQ.
- ...All multimedia (audio or video) produced or published by W3C must be accessible at time of posting.
WAI IG email:
W3C Shares Multimedia Accessibility FAQ
Dear WAI Interest Group Participants,
In order to help the community provide accessible multimedia, W3C has made public it's internal frequently-asked-questions page:
*Multimedia Accessibility FAQ*
http://www.w3.org/2008/06/video-notes
The FAQ provides some practical advice on:
- What do I need to do to make audio and video accessible?
- How do I get a transcript for my media?
- How do I do audio description of visuals?
- How do I do captions?
- Where can I get more information?
W3C's formal guidance on accessible multimedia is provided in WCAG, see
Web Content Accessibility Guidelines (WCAG) Overview
http://www.w3.org/WAI/intro/wcag
To get a list of relevant WCAG 2.0 guidelines, success criteria, and techniques, see:
How to Meet WCAG 2.0, Time-based Media: Guideline 1.2 section
http://www.w3.org/WAI/WCAG20/quickref/#media-equiv
For more details on WCAG 2.0's coverage of accessible mulitmedia, follow the "Success Criteria for this Guideline" links at the bottom of:
Time-based Media: Understanding Guideline 1.2
http://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv.html
Please let us know if you have any questions or comments on the FAQ.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry
WAI Outreach Coordinator, Education and Outreach Working Group (EOWG) Chair
notes:
- ...
Tweet (MAXIMUM 140 characters)
W3C shares Multimedia Accessibility FAQ http://www.w3.org/2008/06/video-notes
(@@)
notes & brainstorms:
- ...
(139)
EARL 1.0 LC October 2009
W3C Home Page (and Newsletters):
Last Call: Evaluation and Report Language (EARL) 1.0
2009-10-29: The Evaluation and Repair Tools Working Group has published a Last Call Working Draft of the Evaluation and Report Language (EARL) 1.0 Schema, updated Working Drafts of HTTP Vocabulary in RDF 1.0, Representing Content in RDF 1.0, Pointer Methods in RDF 1.0, Evaluation and Report Language (EARL) 1.0 Requirements, and a First Public Working Draft of the Evaluation and Report Language (EARL) 1.0 Guide. EARL is a machine-readable format for expressing test results. The primary motivation for developing EARL is to facilitate the processing of test results, such as those generated by Web accessibility evaluation tools, using a vendor-neutral and platform-independent format. Read the invitation to review the EARL 1.0 Last Call Working Draft and about the Web Accessibility Initiative (WAI).
WAI Highlight for home page & RSS feed:
For Review: EARL 1.0 Last Call Working Draft
WAI has published a Last Call Working Draft of the Evaluation and Report Language (EARL) 1.0 Schema, updated Working Drafts of HTTP Vocabulary in RDF 1.0, Representing Content in RDF 1.0, Pointer Methods in RDF 1.0, Evaluation and Report Language (EARL) 1.0 Requirements, and a First Public Working Draft of the Evaluation and Report Language (EARL) 1.0 Guide. EARL provides a format for expressing test results, such as those generated by Web accessibility evaluation tools, using a vendor-neutral and platform-independent format. WAI encourages you to review EARL 1.0 documents and submit any comments. See:
- Call for Review: EARL 1.0 Last Call Working Draft e-mail,
- Evaluation and Report Language (EARL) Overview.
Please send comments by 30 November 2009. (2009-10-@@)
WAI IG email:
Call for Review: EARL 1.0 Last Call Working Draft
Dear WAI Interest Group Participants,
The Evaluation and Repair Tools Working Group invites you to comment on a
series of Working Draft documents published @@ October 2009:
* Evaluation and Report Language (EARL) 1.0 Schema - Last Call Working Draft
http://www.w3.org/TR/EARL10-Schema/
* Evaluation and Report Language (EARL) 1.0 Guide - First Public Working
Draft
http://www.w3.org/TR/EARL10-Guide/
* HTTP Vocabulary in RDF 1.0 - updated Working Draft
http://www.w3.org/TR/HTTP-in-RDF10/
* Representing Content in RDF 1.0 - updated Working Draft
http://www.w3.org/TR/Content-in-RDF10/
* Pointer Methods in RDF 1.0 - updated Working Draft
http://www.w3.org/TR/Pointers-in-RDF10/
* Requirements for the Evaluation and Report Language (EARL) 1.0 - updated
Working Draft
http://www.w3.org/TR/EARL10-Requirements/
EARL is a machine-readable format for expressing test results. It is an RDF
vocabulary, the terms of which are defined by the specifications listed above.
The primary motivation for developing EARL is to facilitate the processing of
test results, such as those generated by Web accessibility evaluation tools,
using a vendor-neutral and platform-independent format. EARL is introduced
in:
EARL Overview
http://www.w3.org/WAI/intro/earl.php
Only EARL 1.0 Schema is currently intended to become a W3C Recommendation,
the remaining five documents are planned to become W3C Notes. The difference
between W3C Recommendations and W3C Notes, and the development stages for these
publications is described in:
How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process
The Working Group believes is has addressed all comments received so far and
is looking for final feedback, especially on the EARL 1.0 Schema document before
promotion and publication as a Candidate Recommendation Working Draft. The
"Status of this Document" sections of the publications include specific
questions and guidance for providing comments. The main changes in this
publication include:
* updated conformance model for EARL
* revised EARL vocabulary definitions
* added an explanatory EARL 1.0 Guide
WAI encourages feedback from developers and researchers who are interested
in software-supported evaluation and validation of websites, and by those who
are interested in Semantic Web technologies for content description,
annotation, and adaptation. Please send comments to the publicly-archived
list:
public-earl10-comments@w3.org
by 30 November 2009
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Henry and Judy Brewer, W3C WAI
On behalf of Shadi Abou-Zahra, ERT WG
with thanks to Michael A Squillace
notes:
- ...
Tweet (MAXIMUM 140 characters)
Interested in processing results from different Web accessibility evaluation
tools? Please comment on EARL LCWD http://tinyurl.com/EARL0907@@
(139) [http://tinyurl.com/EARL0907 to go to WAI IG email]
Interested in Semantic Web technology for content description, annotation,
adaptation? Pls comment on EARL LCWD http://tinyurl.com/EARL0907@@
(139) [http://tinyurl.com/EARL0907 to go to WAI IG email]
notes & brainstorms:
- I suggest doing both -- with the idea that they will get to different audiences, esp. for RT (retweet, which is kinda like an email forward)
- previous draft:
W3C/WAI Evaluation and Report Language (EARL) 1.0 goes to Last Call - group addressed all comments so far. see http://tinyurl.com/EARL0907@@
(140?138) [http://tinyurl.com/EARL0907 to go to WAI IG email]
ATAG 2.0 Oct 2009
W3C Home Page (and Newsletters):
Authoring Tool Accessibility Guidelines (ATAG) 2.0: Updated Working Draft
The Authoring Tool Accessibility Guidelines Working Group has published an updated Working Draft of Authoring Tool Accessibility Guidelines (ATAG) 2.0. ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content Accessibility Guidelines (WCAG) 2.0. ATAG also defines how to make authoring tools accessible so that people with disabilities can use them. Read the invitation to review the ATAG 2.0 Working Draft and about the Web Accessibility Initiative.
WAI Highlight for home page & RSS feed:
For Review: ATAG 2.0 Updated Working Draft
An updated Authoring Tool Accessibility Guidelines (ATAG) 2.0 Working Draft was published 29 October 2009. It includes a revised supporting note "Implementing ATAG 2.0". ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content Accessibility Guidelines (WCAG) 2.0. ATAG also defines how to make authoring tools accessible so that people with disabilities can use them. WAI encourages you to review ATAG 2.0 and submit any comments. See:
- Call for Review: ATAG 2.0 Working Draft updated,
- Authoring Tool Accessibility Guidelines (ATAG) Overview.
Please send comments by 30 November 2009. (2009-10-29)
WAI IG email:
Call for Review: ATAG 2.0 Working Draft updated
Dear WAI Interest Group Participants,
The Authoring Tool Accessibility Guidelines Working Group invites you to comment on the updated Authoring Tool Accessibility Guidelines (ATAG) 2.0 Working Draft published 29 October 2009 at:
http://www.w3.org/TR/ATAG20/
The draft integrates revisions in response to the comments of the 21 May draft as well as a substantially revised document, Implementing ATAG 2.0 which replaces Techniques for ATAG 2.0.
Substantial changes in this working draft include:
* The working group revised how authoring tools should support authors in making choices that improve accessibility
* The working group revised the former Techniques document to better serve developers, changing its title to Implementing ATAG 2.0.
Specific changes and questions for feedback are listed in the Status section:
http://www.w3.org/TR/ATAG20/#status
ATAG defines how authoring tools should help Web developers produce Web content that is accessible and conforms to Web Content Accessibility Guidelines (WCAG) 2.0. 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 by 30 November 2009 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/
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry
On behalf of: Jutta Treviranus, Chair of AUWG, and Director of the Assistive Technology Research Center, University of Toronto
Jeanne Spellman, W3C Staff Contact for AUWG
Involving Users
last updated: $Date: 2011/02/14 15:42:16 $
W3C Home Page (and Newsletters):
Involve Users in Your Web Projects for Better, Easier Accessibility
2009-12-09: The WAI Education and Outreach Working Group today published Involving Users in Web Projects for Better, Easier Accessibility that provides guidance for project managers, designers, and developers of:
- websites and web applications
- browsers, media players, and assistive technologies
- authoring tools such as content management systems (CMS), blog software, and WYSIWYG editors
- standards and policies on accessibility
- web technologies and technical specifications
Learn more about this and the related document Involving Users in Evaluating Web Accessibility in the Involving Users announcement e-mail and the blog post Discover new ways of thinking about accessibility; and learn more about the Web Accessibility Initiative (WAI).
notes:
- ...
WAI Highlight for home page & RSS feed:
Want Better, Easier Accessibility? Involve Users in Your Web Projects
The new document Involving Users in Web Projects for Better, Easier Accessibility provides guidance for project managers, designers, and developers of:
- websites and web applications
- browsers, media players, and assistive technologies
- authoring tools such as content management systems (CMS), blog software, and WYSIWYG editors
- standards and policies on accessibility
- web technologies and technical specifications
Learn more about this and the related document Involving Users in Evaluating Web Accessibility in the Involving Users announcement e-mail and the blog post Discover new ways of thinking about accessibility. Watch for other documents from the WAI-AGE Project coming soon... (2009-12-09)
notes:
- I really want to keep this as short as possible; however it think it's important to put the audiences in a list so they're not missed. -- I just hope we don't need a lot of other text -- remember, highlights are just suppose to be teasers to entice people to the doc....
- involving users email thread
title brainstorms:
- Involve Users in Your Web Projects for Better, Easier Accessibility
body brainstorms:
- The new document Involving Users in Web Projects for Better, Easier Accessibility has been published as part of the WAI-AGE Project. It is for designers and developers of:....
- The new document Involving Users in Web Projects for Better, Easier Accessibility is for designers and developers of:...
Along with Involving Users in Evaluating Web Accessibility, it helps you include people with disabilities and older people with accessibility needs due to aging, throughout your projects. Read more about these documents in the Involving Users announcement e-mail and about the WAI-AGE Project. - Ever wonder when's the best time during the development process to involve users, and how to put together a good user involvement program in your web development business?
- Want to better understand accessibility issues and implement more effective accessibility solutions?
WAI IG email:
Involve Users in Your Web Projects for Better, Easier Accessibility
Dear WAI Interest Group Participants,
Want to better understand accessibility issues and implement more effective accessibility solutions?
The W3C WAI Web Accessibility Initiative (WAI) today published documents to help:
* Involving Users in Web Projects for Better, Easier Accessibility
http://www.w3.org/WAI/users/involving
* Involving Users in Evaluating Web Accessibility
http://www.w3.org/WAI/eval/users
The documents provide guidance on including real users, covering:
* How involving users early helps
* Getting a range of users
* Working with users
* Analyzing accessibility issues
* Drawing conclusions and reporting
* Note for usability professionals
* Combine user involvement with standards
We encourage project managers, designers, and developers of the following to read these documents:
* websites and web applications
*
browsers, media players, and assistive technologies
*
authoring tools such as content management systems (CMS), blog software, and WYSIWYG editors
*
standards and policies on accessibility
*
web technologies and technical specifications
See also the blog post:
*
Discover new ways of thinking about accessibility
http://www.w3.org/QA/2009/12/discover_new_ways_of_thinking.html
These documents were developed and updated by Education and Outreach Working Group (EOWG) <http://www.w3.org/WAI/EO/> as part of the WAI-AGE Project. WAI-AGE is a European Commission IST Specific Support Action, with the goal of increasing accessibility of the Web for older people as well as for people with disabilities. See: http://www.w3.org/WAI/WAI-AGE/
Please let us know if you have any questions or suggestions.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry, EOWG Chair
notes:
- ...
Tweet (MAXIMUM 140 characters)
Want to better understand accessibility issues and implement more effective accessibility solutions? see http://bit.ly/involve_users
(132)
project manager tip: http://bit.ly/involve_users developing websites, browsers, AT, tools, standards, technologies, technical specifications
(140)
notes & brainstorms:
- ...
W3C Q&A blog post:
Discover new ways of thinking about accessibility
As an employee of the W3C Web standards organization, you might think that I would say the most important thing to start with when addressing web accessibility is standards. I don't. I say the first step is learning how people with disabilities use the web. You might be surprised to learn that is the W3C's advice. We've now got it more clearly in writing, in the new document published today by the W3C Web Accessibility Initiative (WAI):
Involving Users in Web Projects for Better, Easier Accessibility
and the updated related document Involving Users in Evaluating Web Accessibility.
We're excited about these and other documents on the perspectives of users — specifically users with disabilities and older users — coming soon as part of WAI-AGE Project funded by the European Commission. People with disabilities have long known that direct experiences are a key input to the standardization process and to successful implementation of standards. Understanding the experiences of older users is becoming an important issue for many projects. These documents help project managers, developers, and designers better include users' experiences throughout their work.
When designers and developers see people with disabilities use products like theirs, most are highly motivated by a new understanding of accessibility. Rather than seeing accessibility as only a checklist item, the real-life experience shows the human side of accessibility. Designers and developers understand the opportunity for their work to impact lives.
It also broadens your perspective in a way that can lead you to discover new ways of thinking about your product that will make it work better for more people in more situations.
The Involving Users docs start with several ways that involving people with disabilities from the beginning of a project helps you better understand accessibility issues and implement more effective accessibility solutions. The docs provide pointers on:
- Finding a range of users
- Working with users
- Analyzing accessibility issues
- Drawing conclusions and reporting
- Notes for usability professionals
- Combining user involvement with standards <-note this important section in each document.
While the evaluation document is mostly for those developing websites, web applications, browsers, assistive technologies (AT), and authoring tools; the main Involving Users document also addresses those developing standards and policies for accessibility, and those developing any web technologies or technical specifications.
We hope that the Involving Users documents help you realize the benefits of involving people with disabilities in your web projects. Please share your experiences, and your suggestions for the documents: the WAI Interest Group (WAI IG) hosts a public discussion e-mail list; comments on specific documents are collected through the publicly-archived wai-eo-editors@w3.org list; and we'll watch for comments to this blog post. Thanks! ~Shawn
title brainstorms:
- Discover new ways of thinking about accessibility
- Broaden your perspective on accessibility
- Accessibility Shortcut: Get real users involved in your web projects
- Accessibility Step 1: More than Standards
- Accessibility "silver bullet": Get real users involved in your web projects
Accessibility "magic bullet": Get real users involved in your web projects
body brainstorms:
- Many people with disabilities have been involved in combining real-world experience with standards to optimize accessibility in the built environment. These new documents help developers in the web environment include the...
template@@
W3C Home Page (and Newsletters):
@@title
2009-@@-@@: The @@Working Group today published... ...[Learn more|Read] about [wai ig email] and the Web Accessibility Initiative (WAI).
notes:
- ...
title brainstorms:
- ...
body brainstorms:
- ...
notes:
- ...
title brainstorms:
- ...
body brainstorms:
- ...
WAI IG email:
Call for Review: @@
Dear WAI Interest Group Participants,
The W3C WAI @@ Working Group (@@WG) invites you to comment on...
Please let us know if you have any questions. Thank you in advance for your comments.
Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Regards,
~Shawn Lawton Henry
On behalf of:
@@
notes:
- ...
notes & brainstorms:
- ...
(139)
notes:
- ...
title brainstorms:
- ...
body brainstorms:
- ...