W3C logo Web Accessibility Initiative (WAI) logo

Planning Highlights on WAI Home Page and other announcements
2011 Archive

Note: This Web page is an internal working draft and should not be referenced or quoted under any circumstances.

[Planning Highlights main page]

Drafts of past highlights

Metrics Symposium Agenda and Registration

W3C Home Page (and Newsletters):

Website Accessibility Metrics - Online Symposium - 5 December

Registration is now open for the online symposium on website accessibility metrics to be held on 5 December 2011. The symposium is intended for researchers and practitioners who want to explore website accessibility metrics and help develop a roadmap for future research and development. For details and registration, see Website Accessibility Metrics - Online Symposium. Learn more about the Web Accessibility Initiative (WAI).

title brainstorms:

body brainstorms:

WAI Highlight for home page & RSS feed:

Online Symposium: Website Accessibility Metrics

Registration is now open for the online symposium on website accessibility metrics to be held on 5 December 2011. The symposium is intended for researchers and practitioners who want to explore website accessibility metrics and help develop a roadmap for future research and development. For details and registration, see Website Accessibility Metrics - Online Symposium.    (2011-11-17)

title brainstorms:

body brainstorms:

notes:

Tweet (MAXIMUM 140 characters)

Registration open for Website #Accessibility Metrics - Online Symposium - 5 December, space limited. See info at bit.ly/rdmetrics2 -#a11y

(@@)

notes & brainstorms:

W3C Q&A blog post:

not doing

notes:

title brainstorms:

body brainstorms:

WAI-ACT Project

W3C Home Page (and Newsletters):

WAI-ACT Web Accessibility Project

The Web Accessibility Initiative (WAI) has launched WAI-ACT - Cooperation Framework for Guidance on Advanced Technologies, Evaluation Methodologies, and Research Agenda Setting to Support eAccessibility, a European Commission (EC)-funded project. Learn more about the project and how to participate from the WAI-ACT Project announcement e-mail.

notes:

title brainstorms:

previous versions and drafts:

WAI Highlight for home page & RSS feed:

WAI-ACT: Cooperation, Implementation, Evaluation, Research

WAI invites you to participate in the new WAI-ACT Project to help develop:

  • An expanded framework for open cooperation among individuals and organizations,
  • Technical guidance on implementing web accessibility,
  • A harmonized methodology for evaluating website accessibility,
  • Coordinated contribution to an eAccessibility research agenda.

See WAI-ACT Project: Accessibility Cooperation, Implementation, Evaluation, and Research e-mail and WAI-ACT Project page to learn about this European Commission (EC)-funded project.   (2011-11-16)

if need to weave in EU-funded:

title brainstorms:

body brainstorms:

WAI IG email:

WAI-ACT Project: Accessibility Cooperation, Implementation, Evaluation, and Research

Dear WAI Interest Group Participants,

The W3C Web Accessibility Initiative (WAI) invites you to participate in a new project: WAI-ACT - "Cooperation Framework for Guidance on Advanced Technologies, Evaluation Methodologies, and Research Agenda Setting to Support eAccessibility". Information about the project, including current and upcoming work, is available from:
     http://www.w3.org/WAI/ACT/

WAI-ACT will provide advanced accessibility support by building upon past web accessibility work, harmonizing existing work, and helping to shape future work. Specifically, WAI-ACT will develop:
- An expanded framework for open cooperation among individuals and organizations,
- Technical guidance on implementing web accessibility,
- A harmonized methodology for evaluating website accessibility,
- Coordinated contribution to an eAccessibility research agenda.

Background: WAI-ACT is co-funded by the European Commission as a Specific Support Action under the IST 7th Framework Programme. It is lead by the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI), and includes project partners Stiching Bartimeus Accessibility (SBA), Fraunhofer Institute for Applied Information Technology (Fraunhofer), and Johannes Keppler University (JKU). WAI-ACT will seek active exchange with relevant networks in Europe, such as eAccess+, and will coordinate with standardisation activities, such as EC Mandate M/376.

If you have any questions after reading the project page <http://www.w3.org/WAI/ACT/>, contact Shadi Abou-Zahra: shadi@w3.org

Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Short URI to this archived e-mail: @@

Regards,
Shawn Lawton Henry, WAI Outreach
Shadi Abou-Zahra, WAI-ACT Scientific Coordinator

previous versions:

Tweet (MAXIMUM 140 characters)

New WAI-ACT project to develop #accessibility guidance on advanced technologies, evaluation methods, & research http://bit.ly/wai-act1 #a11y

(140)
(link goes to wai ig email)

notes & brainstorms:

W3C Q&A blog post:

not doing

RDWG teleconference seminar

W3C Home Page (and Newsletters):

Symposium on Web Accessibility Metrics

The Research and Development Working Group (RDWG) will hold an online symposium for researchers and practitioners to explore web accessibility metrics and develop a roadmap for future research and development. The Call for Papers is open until 1 November 2011. Learn more about the Symposium on Web Accessibility Metrics and the Web Accessibility Initiative (WAI).

notes:

title brainstorms:

body brainstorms:

WAI Highlight for home page & RSS feed:

Symposium: Web Accessibility Metrics

The Research and Development Working Group (RDWG) is exploring metrics for measuring web accessibility and welcomes your input. The Call for Papers is open until 1 November 2011. See Call for Papers: Web Accessibility Metrics - Online Symposium e-mail.   (2011-@@-@@)

notes:

title brainstorms:

body brainstorms:

WAI IG email:

Call for Papers: Web Accessibility Metrics - Online Symposium

Dear WAI Interest Group Participants,

The W3C WAI Research and Development Working Group (RDWG) invites you to share your experiences with metrics for measuring web accessibility beyond basic conformance to standards. In particular, RDWG is looking for valid, reliable, and practical metrics to measure the impact of accessibility issues on people with disabilities. These will be discussed in an online Symposium on 5 December 2011. More information will be available from:
http://www.w3.org/WAI/RD/2011/metrics/

RDWG Symposia bring together researchers and practioners interested in a particular aspect of web accessibility to advance research in that area. With this Symposium, we will collect current research, synthesize ideas in a teleconference, and provide a roadmap for future work on web accessibility metrics. The Symposium proceedings and report will be available publicly online afterward.

*If you might like to contribute to this Symposium*, please see the *Call for Papers* at:
http://www.w3.org/WAI/RD/2011/metrics/cfp

Background about RDWG:
The Research and Development Working Group (RDWG) helps
- increase accessibility considerations in research on web technologies, including mainstream research,
- suggest research questions that may contribute to web accessibility research projects,
- inform development of web accessibility solutions,
- decrease the number of potential barriers in future web-related technologies.

See the RDWG home page <http://www.w3.org/WAI/RD/> for links to an FAQ and a wiki that includes potential topics for future Symposia.

We welcome your ideas on this topic and for future RDWG work. Please send comments to the publicly-archived mailing list:
public-wai-rd@w3.org

If you have any questions, contact Shadi Abou-Zahra: shadi@w3.org

Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Short URI to this archived e-mail: @@

Regards,
Shawn Lawton Henry, WAI Outreach
Simon Harper, RDWG Co-Chair
Shadi Abou-Zahra, RDWG W3C Team Contact

notes:

Tweet (MAXIMUM 140 characters)

How do you measure web #accessibility? #WAI is exploring metrics in an upcoming symposium. Find out more from http://bit.ly/rdmetrics1 #a11y

(140)
(link goes to wai ig email)

notes & brainstorms:

W3C Q&A blog post:

not doing

UAAG, July 2011

W3C Home Page (and Newsletters):

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. The Working Group also published an updated Working Draft of Implementing UAAG 2.0. Read the invitation to review the UAAG 2.0 Working Draft and about the Web Accessibility Initiative (WAI).

Eval TF, July 2011

W3C Home Page (and Newsletters):

not doing

.

WAI Highlight for home page & RSS feed:

Eval Task Force: Guidance on evaluating web accessibility

WAI is starting a WCAG 2.0 Evaluation Methodology Task Force to develop more comprehensive guidance on evaluating web accessibility. The Evaluation Task Force will develop an internationally harmonized methodology for evaluating websites' conformance to WCAG 2.0. Learn more about it from the Web Accessibility Evaluation and Testing e-mail.   (2011-07-13)

notes:

WAI IG email:

Web Accessibility Evaluation and Testing

Dear WAI Interest Group Participants,

WAI is starting a WCAG 2.0 Evaluation Methodology Task Force to develop more comprehensive guidance on evaluating web accessibility.

The Evaluation Task Force will develop an internationally harmonized methodology for evaluating websites' conformance to WCAG 2.0. The methodology will provide provides a step-by-step procedure for evaluating websites, including guidance on sampling individual web pages, evaluating them according to WCAG 2.0, and aggregating the results into a conformance statement. To learn more about the scope of work and anticipated timeline, see the WCAG 2.0 Evaluation Methodology Task Force (Eval TF) Work Statement at:
http://www.w3.org/WAI/ER/2011/eval/eval-tf

The methdology is part of a wider W3C/WAI effort on web accessibility evaluation and testing, which includes the development of test suites for all WAI guidelines and specifications. For more information, see W3C/WAI Web Accessibility Evaluation and Testing Activities at:
http://www.w3.org/WAI/ER/2011/eval/

If you would like to get announcements when drafts of the methodology are available, you can subscribe to WAI's RSS feed, Twitter, or other venues listed at:
http://www.w3.org/WAI/about/announcements

If you might be interested in actively participating in this work, please read Participating in WAI at:
http://www.w3.org/WAI/participation
and then contact Shadi Abou-Zahra, see http://www.w3.org/People/shadi/

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
& Shadi Abou-Zahra

notes:

Tweet (MAXIMUM 140 characters)

WAI’s new Eval Task Force is developing more comprehensive guidance on #evaluating web #accessibility- learn more from http://bit.ly/EvalTF #a11y
(140)

notes & brainstorms:

W3C Q&A blog post:

not doing

 

WCAG2Techs2011June

W3C Home Page (and Newsletters):

For Review: Updated Techniques for Web Content Accessibility Guidelines (WCAG)

The Web Content Accessibility Guidelines Working Group today requests review of draft updates to Notes that accompany WCAG 2.0: Techniques for WCAG 2.0 (Editors' Draft) and Understanding WCAG 2.0 (Editors' Draft). Comments are welcome through 26 August 2011. (This is not an update to WCAG 2.0, which is a stable document.) To learn more about the updates, see the Call for Review: WCAG 2.0 Techniques Draft Updates e-mail. Read about the Web Accessibility Initiative (WAI).

notes:

 

WAI Highlight for home page & RSS feed:

For Review: Updated WCAG 2.0 Techniques

WAI announces a Call for Review of draft updates to supporting documents for WCAG 2.0: Techniques for WCAG 2.0 (Editors' Draft) and Understanding WCAG 2.0 (Editors' Draft). (This is not an update to WCAG 2.0, which is a stable document.) To learn more about the updates, see Call for Review: WCAG 2.0 Techniques Draft Updates e-mail. Please submit comments by 26 August 2011.    (2011-06-21)

notes:

 

WAI IG email:

Call for Review: WCAG 2.0 Techniques Draft Updates

Dear WAI Interest Group Participants,

The W3C WAI announces a Call for Review of updates to two supporting documents for Web Content Accessibility Guideline (WCAG) 2.0. *This is not an update to WCAG 2.0, which is a stable document*.

The supporting documents (W3C Notes) are updated periodically to reflect current practices and technologies. *The existing Techniques and Understanding documents remain in place as W3C Notes* while the separate draft updates are under review and the WCAG Working Group addresses comments.

The following draft updates are available for review as Editors' Drafts:
- Techniques for WCAG 2.0 Editors' Draft
http://www.w3.org/WAI/GL/2011/WD-WCAG20-TECHS-20110621/
- Understanding WCAG 2.0 Editors' Draft
http://www.w3.org/WAI/GL/2011/WD-UNDERSTANDING-WCAG20-20110621/

*What is updated*: Draft updates include addition of PDF and Silverlight techniques, and changes in response to public comments. The changes are highlighted in diff-marked versions at:
- http://www.w3.org/WAI/GL/2011/WD-WCAG20-TECHS-20110621/complete-diff.html
- http://www.w3.org/WAI/GL/2011/WD-UNDERSTANDING-WCAG20-20110621/complete-diff.html

The following blog post provides information on updating WCAG 2.0 supporting documents and states that *publication of techniques for a specific technology does not imply that the technology can be used in all cases to create accessible content*:
- New and Improved WCAG 2.0 Techniques
http://www.w3.org/QA/2010/10/new_and_improved_wcag_20_techn.html

Please send any comments on these Editors' Drafts by *26 August 2011*. Comments and contributions for additional WCAG 2.0 techniques can be sent via web form or e-mail, per:
- Instructions for Commenting on WCAG 2.0 Documents
http://www.w3.org/WAI/WCAG20/comments/

If you are interested in actively contributing to the development of additional WCAG 2.0 techniques and support material through the WCAG Working Group, please see:
- Participating in WAI http://www.w3.org/WAI/participation and contact Michael Cooper

For an introduction to the WCAG documents, see:
- WCAG Overview http://www.w3.org/WAI/intro/wcag.php

Feel free to circulate this message to other lists; please avoid cross-postings where possible.

Regards,
~Shawn Henry, WAI Outreach
Gregg Vanderheiden and Loretta Guarino Reid, WCAG Co-Chairs
Michael Cooper, W3C Staff Contact

notes:

Tweet (MAXIMUM 140 characters)

WCAG 2.0 Techniques draft updates for your review, by 26 August. See details in email: http://bit.ly/wcag201106 Thanks! #a11y #accessibility

(140)

notes & brainstorms:

W3C Q&A blog post:

[not doing - pointing to New and Improved WCAG 2.0 Techniques in WAI IG e-mail]

 

RDWG2011May

W3C Home Page (and Newsletters):

not doing

 

WAI Highlight for home page & RSS feed:

RDWG Update: Research and Development Working Group

W3C WAI's Research and Development Working Group (RDWG) will soon resume work to help identify new trends in web accessibility and inform the development of solutions. See the RDWG Update: Research and Development Working Group e-mail and RDWG home page.    (2011-05-20)

notes:

WAI IG email:

RDWG Update: Research and Development Working Group

Dear WAI Interest Group Participants,

The W3C WAI Research and Development Working Group (RDWG) will soon resume work to help:
* increase accessibility considerations in research on web technologies, including mainstream research
* suggest research questions that may contribute to web accessibility research projects
* inform development of web accessibility solutions
* decrease the number of potential barriers in future web-related technologies

RDWG was developed from the previous Interest Group to provide a more structured core group of participants for on-going work. To learn more about the Working Group, please see the RDWG home page:
     http://www.w3.org/WAI/RD/

If you are interested in participating in RDWG, please review the home page linked above, and the RDWG Charter at:
     http://www.w3.org/WAI/RD/charter3
Information on how to join RDWG is in Participating in the Research and Development Working Group (RDWG) at:
     http://www.w3.org/WAI/RD/participation

If you have any questions, contact the RDWG staff contact, Shadi Abou-Zahra <shadi@w3.org>

Feel free to circulate this message to other lists; please avoid cross-postings where possible.
Short URI to this archived e-mail: http://bit.ly/rdwg20115

Regards,
~Shawn Lawton Henry, WAI Outreach
Simon Harper, RDWG Co-Chair
Shadi Abou-Zahra, RDWG Team Contact

notes:

Tweet (MAXIMUM 140 characters)

Web Accessibility Research & Development Working Group (RDWG) getting going at #W3C #WAI see http://bit.ly/rdwg20115 - #a11y #accessibility

(139)

notes & brainstorms:

W3C Q&A blog post:

not doing

EARL 2011 May

W3C Home Page (and Newsletters):

Last Call: Evaluation and Report Language (EARL) 1.0

The Evaluation and Repair Tools Working Group has published a Last Call Working Draft of the Evaluation and Report Language (EARL) 1.0 Schema, and updated Working Drafts of Developer Guide for Evaluation and Report Language (EARL) 1.0, HTTP Vocabulary in RDF 1.0, Representing Content in RDF 1.0, and Pointer Methods in RDF 1.0. EARL is a machine-readable format for expressing test results, such as results from web accessibility evaluation tools. Read the invitation to review the EARL 1.0 Last Call Working Draft and about the Web Accessibility Initiative (WAI).

body ideas:

WAI Highlight for home page & RSS feed:

For Review: EARL 1.0 Last Call Working Draft

The Last Call Working Draft of Evaluation and Report Language (EARL) 1.0 Schema is ready for your review, along with updated Working Drafts of the EARL Developer Guide and related documents. EARL supports combining test results from different software tools, for example, to compare results from web accessibility evaluation tools. See:

Please send any comments on this Last Call Working Draft by 10 June 2011. (2011-05-10)

body brainstorms:

WAI IG email:

Call for Review: EARL 1.0 Last Call Working Draft

Dear WAI Interest Group (IG) Participants,

WAI invites you to comment on the Last Call Working Draft of EARL and related documents published 10 May 2011:
     * Evaluation and Report Language (EARL) 1.0 Schema - Last Call Working Draft
      http://www.w3.org/TR/EARL10-Schema/
     * Developer Guide for Evaluation and Report Language (EARL) 1.0 - updated 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/

EARL provides a way to combine results from different web accessibility evaluation tools, and to share results between tools. For example, with EARL an authoring tool can get accessibility information from an evaluation tool. EARL is a machine-readable format for expressing test results in a vendor-neutral and platform-independent format. It is introduced in:
     EARL Overview
     http://www.w3.org/WAI/intro/earl

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 *10 June 2011*

Status of documents:

EARL 1.0 Schema is intended to become a W3C Recommendation. The other four documents are currently planned to become W3C Notes. The difference between W3C Recommendations and W3C Notes -- and Last Call, Candidate Recommendation, and other development stages -- 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 feedback, especially on EARL 1.0 Schema before it progresses to Candidate Recommendation Working Draft. The "Status of this Document" sections of the publications include specific questions and guidance for providing comments.

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.
Short URI to this archived e-mail: http://bit.ly/earl20115

Regards,
~Shawn Henry, WAI Outreach
Shadi Abou-Zahra, ERT Chair

notes:

Tweet (MAXIMUM 140 characters)

 

(@@)

notes & brainstorms:

W3C Q&A blog post:

not doing

ATAG 2011 April

W3C Home Page (and Newsletters):

Authoring Tool Accessibility Guidelines (ATAG) 2.0 and Implementing ATAG 2.0 Working Drafts Updated

The Authoring Tool Accessibility Guidelines Working Group has published updated Working Drafts of Authoring Tool Accessibility Guidelines (ATAG) 2.0 and the companion document Implementing ATAG 2.0. ATAG defines how authoring tools should help developers produce accessible web content that 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 them. Comments are welcome through 24 May 2011. Please see the invitation to review the ATAG 2.0 Working Draft for more information. Learn more about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

For Review: ATAG 2.0 and Implementing ATAG 2.0 Working Drafts Updated

Authoring Tool Accessibility Guidelines (ATAG) 2.0 is relevant to you if you use blogs, wikis, social networking websites, content management systems (CMS), HTML editors, or other such tools. ATAG defines how these tools should help you make your blog posts, websites, and other web content accessible — and how the tools themselves should be accessible so that people with disabilities can use them. Please review the updated Working Drafts and let us know how they can be improved to better meet the needs of developers and of people with disabilities. For more info see Call for Review: ATAG 2.0 Updated Working Drafts. Please send comments by 24 May 2011.    (2011-04-26)

notes:

WAI IG email:

Call for Review: ATAG 2.0 Updated Working Drafts

Dear WAI Interest Group Participants,

W3C WAI invites you to review the updated Working Drafts of Authoring Tool Accessibility Guidelines (ATAG) 2.0 and Implementing ATAG 2.0 published 21 April 2011 at:
     http://www.w3.org/TR/ATAG20/
     http://www.w3.org/TR/IMPLEMENTING-ATAG20/

To people with disabilities:
We especially encourage people with disabilities and accessibility specialists to review this draft of ATAG 2.0 and let us know how it can be improved to better meet the needs of people with disabilities. ATAG is particularly relevant to you if you use blogs, wikis, social networking websites, content management systems (CMS), HTML editors, or other such tools[1]. ATAG defines how these tools should help you make your blog posts, websites, etc. accessible — and how the tools themselves should be accessible so that people with disabilities can use them.

To tool developers:
We invite authoring tool developers to prepare to implement ATAG 2.0, with the caution that the guidelines might change. In the coming months, we'll be asking for tools that meet ATAG 2.0. Will your tool be an example? If you are considering implementing ATAG 2.0 soon, please e-mail Jeanne@w3.org

Note about Working Draft status:
ATAG 2.0 was published as a Last Call Working Draft on 8 July 2010. Due to substantial changes made in response to over 250 comments on that draft, the Working Group decided to return to Working Draft stage to collect feedback on these changes. The Working Group expects to publish another Last Call Working Draft in a few months. Last Call and other development stages are described in: How WAI Develops Accessibility Guidelines through the W3C Process at:
     http://www.w3.org/WAI/intro/w3c-process

Recent updates:
For a list of significant changes since the last drafts and specific questions for feedback, see the Status sections:
     http://www.w3.org/TR/ATAG20/#status
     http://www.w3.org/TR/IMPLEMENTING-ATAG20/#status

Comments:
Please submit comments on how ATAG 2.0 can be improved to better meet the needs of people with disabilities to the publicly-archived list:
     public-atag2-comments@w3.org
     by *24 May 2011*

Background:
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
ATAG is developed by the 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.

[1] Examples of authoring tools: http://www.w3.org/WAI/intro/atag.php#for

Regards,
Shawn Henry, WAI Outreach
Jutta Treviranus, AUWG Chair
Jeanne Spellman, AUWG W3C Staff Contact

notes:

Tweet (MAXIMUM 140 characters)

Want blogs, CMSs, HTML editors, and other web authoring tools to be #accessible? See email: http://bit.ly/atag20114 -- #a11y #accessibility

(139)

 

BAD M 2010

W3C Home Page (and Newsletters):

BAD to Good: Demo shows web accessibility barriers fixed

The Web Accessibility Initiative (WAI) Education and Outreach Working Group (EOWG) has updated the Before and After Demonstration (BAD). BAD shows an inaccessible website and a retrofitted version of the same website with the accessibility barriers fixed. Read the call for review e-mail, learn about Accessibility, and visit the WAI home page.

notes:

title brainstorms:

body brainstorms:

WAI Highlight for home page & RSS feed:

BAD to Good: Demo shows web accessibility barriers fixed

The Before and After Demonstration (BAD) shows an inaccessible website and a retrofitted version of the same website with the accessibility barriers fixed. BAD is especially useful for presentations. See more in the Call for Review: Before and After Demonstration (BAD) e-mail.    (2011-10-13)

notes:

title brainstorms:

body brainstorms:

WAI IG email:

Call for Review: Before and After Demonstration (BAD)

Dear WAI Interest Group Participants,

The W3C WAI Education and Outreach Working Group (EOWG) invites you to comment on:
Before and After Demonstration (BAD)
http://www.w3.org/WAI/demos/bad/

BAD shows an inaccessible website and a retrofitted version of the same website with the accessibility barriers fixed. BAD has in-line notes ("annotations") for you to get more information. It also includes evaluation reports that list the accessibility problems for each page.

BAD is useful for presentations, for learning about specific web accessibility barriers and their implications, and as an example of conformance evaluation reports.

We would like to know how this updated WAI resource works for you and how we can improve it. (Adding video, scripting, and WAI-ARIA are already on the list of enhancements that we would like to implement in BAD.)
Please send comments to the publicly-archived list:
wai-eo-editors@w3.org

Background: BAD was first developed with support of the EC-funded WAI-TIES Project. It was updated for Web Content Accessibility Guidelines (WCAG) 2.0 and to better cover accessibility issues of older users as part of the EC-funded WAI-AGE Project. Information on these past projects is available at:
http://www.w3.org/WAI/TIES/
http://www.w3.org/WAI/WAI-AGE/

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.
Short URI to this archived e-mail: http://bit.ly/bad1110

Regards,
~Shawn Lawton Henry, EOWG Chair
and Shadi Abou-Zahra, BAD Task Force facilitator

notes:

Tweet (MAXIMUM 140 characters)

BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/bad1110 Useful for presentations. #a11y
(132 characters)

notes & brainstorms:

W3C Q&A blog post:

not doing

wai-nav-beta

W3C Home Page (and Newsletters):

not doing now. possibly later once kinks are worked out.

 

WAI Highlight for home page & RSS feed:

Look around: Updated WAI website navigation

The WAI website navigation is updated, and points to some new drafts in development. We'll be doing more testing and working out some aspects throughout March. We look forward to your input! Please send any feedback to:

  • wai-eo-editors@w3.org if you want your message publicly archived.
  • wai@w3.org if you want your message to go only to WAI staff. Please indicate if we may forward it to a public list anonymously, with your name and contact information removed.

(2011-03-11)

notes:

title brainstorms:

body brainstorms:

WAI IG email:

not doing now. maybe week of 21 March if determine kinks are worked out

 

Tweet (MAXIMUM 140 characters)

not doing now. maybe week of 21 March if determine kinks are worked out

 

W3C Q&A blog post:

not doing now. probably week of 21 March if determine kinks are worked out

WCAG2transfeb2011

W3C Home Page (and Newsletters):

Web Content Accessibility Guidelines (WCAG 2.0) Authorized Translations now in six languages

Today two more Authorized Translations of WCAG 2.0 were published, bringing the total to six languages. These were developed through the Policy for Authorized W3C Translations and they can be used for official purposes. W3C encourages translation of specifications and resources into all languages; see W3C Translations. The Web Accessibility Initiative (WAI) particularly encourages the development of W3C Authorized Translations of WCAG 2.0 and other technical specifications to facilitate their adoption and implementation internationally; see Translating WAI Documents. To find out if WCAG is available in your language, see the WCAG 2.0 Translations list, which also lists unofficial translations. Additional perspectives are in the "WCAG 2.0 in your mother tongue" blog post. Read about the Web Accessibility Initiative (WAI).

body brainstorms:

[longer version]
Today three more Authorized Translations of WCAG 2.0 were published, bringing the total to seven languages. Authorized W3C Translations are reviewed by stakeholders following the Policy for Authorized W3C Translations and they can be used for official purposes. W3C encourages translation of specifications and resources into all languages. For information on translating documents and for links to existing translations, see W3C Translations. The Web Accessibility Initiative (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. To find out if WCAG is available in your language, see the WCAG 2.0 Translations list. Additional perspectives are in the "WCAG 2.0 in your mother tongue" blog post. Read about the Web Accessibility Initiative (WAI).

[bullet version]
Today three more Authorized Translations of WCAG 2.0 were published, bringing the total to seven languages. Authorized W3C Translations can be used for official purposes. To learn more, see:

WAI Highlight for home page & RSS feed:

WCAG 2.0 in Finnish: Authorized Translation Published

Verkkosisällön saavutettavuusohjeet (WCAG) 2.0, the Finnish 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:

(2011-02-16)

WCAG 2.0 in Danish: Authorized Translation Published

Retningslinjer for tilgængeligt webindhold (WCAG) 2.0, the Danish 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:

(2011-02-16)

WCAG 2.0 in Danish and Finnish: Authorized Translations Published

Following completion of the W3C Authorized Translations process, Web Content Accessibility Guidelines (WCAG) 2.0 is now available in Danish and Finnish Authorized Translations. WAI encourages translating WAI documents in all languages. See:

(2011-02-16)

notes:

...

WAI IG email:

[will use boilerplate - one e-mail for each language]

Tweet (MAXIMUM 140 characters)

[will use boilerplate - one tweet for each language]