Planning Highlights on WAI Home Page and other announcements
2012-2013 Archive

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

WAI staff drafts [limited access]

Drafts of past highlights

EasyChecks1213

W3C Home Page (and Newsletters):

Easy Checks - A First Review of Web Accessibility Updated Draft

The Education and Outreach Working Group (EOWG) has published an updated draft of the WAI resource Easy Checks - A First Review of Web Accessibility. Easy Checks helps you assess if a Web page addresses accessibility. It provides simple steps for anyone who can use the Web; no accessibility knowledge or skill is required. The checks cover just a few accessibility issues and are designed to be quick and easy, rather than definitive. Learn about the Web Accessibility Initiative (WAI).

notes:

july 2013 blurb

WAI Highlight for home page & RSS feed:

Easy Checks - A First Review of Web Accessibility is updated for the holidays

Have you ever wondered: "Is this web page accessible?" Easy Checks - A First Review of Web Accessibility provides simple steps to start assessing web accessibility. It is designed for anyone who can use the Web; no accessibility knowledge or skill is required. The checks cover just a few accessibility issues and are intended to be quick and easy, rather than definitive. We welcome your suggestions and comments to the publicly-archived list wai-eo-editors@w3.org. (2013-12-20)

notes:

WAI IG email:

Easy Checks: A First Review of Web Accessibility is updated for the holidays

Dear WAI Interest Group Participants,

WAI's Education and Outreach Working Group (EOWG) has published an updated draft of:
Easy Checks - A First Review of Web Accessibility
http://www.w3.org/WAI/eval/preliminary

Easy Checks helps you answer the question, "Does this web page address accessibility?". It provides simple steps for anyone who can use the web; no accessibility knowledge or skill is required. The checks cover just a few accessibility issues and are designed to be quick and easy, rather than definitive.

Recent edits to Easy Checks are listed in the changelog at: <http://www.w3.org/WAI/EO/wiki/Easy_Checks_changelog>

With this update, EOWG feels the text content is fairly stable. We are now working on the illustrations.

Please send your suggestions and comments on this draft to the publicly-archived mailing list:
wai-eo-editors@w3.org

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.

notes:

Nov LC email

Tweet (MAXIMUM 140 characters)

Easy Checks - A First Review of Web Accessibility is updated in time for the holidays :-) http://bit.ly/EZchk Comments welcome. #a11y

(000)

notes & brainstorms:

W3C Q&A blog post:

not doing

ARIA UAIG lc2

W3C Home Page (and Newsletters):

Last Call: WAI-ARIA User Agent Implementation Guide

The Protocols and Formats Working Group (PFWG) today published the updated Last Call Working Draft of WAI-ARIA 1.0 User Agent Implementation Guide, which describes how browsers and other user agents should support WAI-ARIA (the Accessible Rich Internet Applications specification); specifically, how to expose WAI-ARIA features to platform accessibility APIs. Comments are welcome through 6 December. Learn more in the call for review e-mail and read about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

For Review: WAI-ARIA User Agent Implementation Guide - Last Call Working Draft

The updated Last Call Working Draft of WAI-ARIA 1.0 User Agent Implementation Guide is available for review. It describes how browsers and other user agents should support WAI-ARIA (the Accessible Rich Internet Applications specification); specifically, how to expose WAI-ARIA features to platform accessibility APIs. For more information, see the Call for Review: WAI-ARIA User Agent Implementation Guide - Last Call Working Draft e-mail. Please send any comments by 6 December 2013. (2013-11-05)

notes:

WAI IG email:

Call for Review: WAI-ARIA User Agent Implementation Guide - Last Call Working Draft

Dear WAI Interest Group Participants,

The W3C WAI Protocols and Formats Working Group (PFWG) invites you to review that Last Call Working Draft of:
WAI-ARIA 1.0 User Agent Implementation Guide
http://www.w3.org/TR/wai-aria-implementation/

It is part of the Accessible Rich Internet Applications (WAI-ARIA) suite described in:
WAI-ARIA Overview
http://www.w3.org/WAI/intro/aria.php

This User Agent Implementation Guide is for developers of web browsers and other user agents. It describes how user agents should support WAI-ARIA; specifically, how to expose WAI-ARIA features to platform accessibility APIs (application programming interfaces). For more information, see the Abstract at <http://www.w3.org/TR/wai-aria-implementation/#abstract>

Document stages: This Guide was previously published as a Last Call Working Draft, and then changes were made based on WAI-ARIA testing. It was then published as a Working Draft for review of those changes. Now that testing is nearly complete and the PFWG thinks the content is stable, we are publishing it as a Last Call Working Draft. We expect to advance this Guide to Candidate Recommendation soon. "Last Call", "Candidate Recommendation", and other document stages are explained in:
How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process

Comments: Please send any comments on this draft to the publicly-archived list:
public-pfwg-comments@w3.org
by *6 December 2013*

About the URI: The first link above goes to the latest version of the document. The "dated" version is: <http://www.w3.org/TR/2013/WD-wai-aria-implementation-20131105/>/ The difference between these links are explained in Referencing and Linking to WAI Guidelines and Technical Documents at <http://www.w3.org/WAI/intro/linking.html>

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.

notes:

previous: lc Jan 2012, August 2012

Tweet (MAXIMUM 140 characters)

WAI-ARIA User Agent Implementation Guide – browsers’ role in implementing #ARIA – Last Call Draft for Review: [@@wai-ig_link] -#a11y

(133ish)

notes:

W3C Q&A blog post:

not doing

RDWGcall2013Dec

W3C Home Page (and Newsletters):

Accessible E-Learning - Online Symposium - Call for Papers

The Research and Development Working Group (RDWG) will hold an online symposium to share e-learning experiences and research; discuss different approaches to address accessibility issues in e-learning contexts; and explore next steps to advance accessibility in e-learning environments, including Massive Open Online Courses (MOOCs). The Call for Papers is open until 15 November 2013. Learn more about the Symposium on Accessible E-Learning and the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

Call for Papers: Accessible E-Learning Symposium

[edited for final] The Research and Development Working Group (RDWG) will hold an online symposium to share e-learning experiences and research; discuss different approaches to address accessibility issues in e-learning contexts; and explore next steps to advance accessibility in e-learning environments, including Massive Open Online Courses (MOOCs). The Call for Papers is open until 15 November 2013. See Call for Papers: Accessible E-Learning - Online Symposium e-mail. (2012-03-05)

notes:

WAI IG email:

Call for Papers: Accessible E-Learning - Online Symposium

Dear WAI Interest Group Participants,

The W3C WAI Research and Development Working Group (RDWG) invites you to share your experiences with accessible e-learning for an online symposium to be conducted on 16 December 2013. See:
       Accessible E-Learning Online Symposium
       http://www.w3.org/WAI/RD/2013/e-learning/

The primary objective of this symposium is to share e-learning experiences and research; discuss different approaches to address accessibility issues in e-learning contexts; and explore next steps to advance accessibility in e-learning environments, including Massive Open Online Courses (MOOCs). In particular, the objective is to investigate:
* Relationships and integration between content accessibility and interface accessibility.
* Evaluating accessibility of e-learning environments.
* Accessibility of e-learning environments used in non-conventional contexts and/or by means of non-conventional devices (i.e. m-learning, t-learning).
* Privacy issues in profiling learners and e-learning environments users.
* Experiences and examples of accessible MOOCs.
* Comparisons and analysis of e-learning standards related to accessibility.
* Experiences and examples of standards implementations in e-learning environments.
* Different standards, compliance and integration.

RDWG Symposia bring together researchers, practitioners, and users with disabilities interested in a particular aspect of web accessibility to advance research and development in that area. The online symposia include a panel with the authors of accepted papers, and provide an opportunity for participants to ask questions. Symposia proceedings, transcript, and a report are available publicly online afterward.

*If you are interested in contributing to this Symposium*, please submit your paper by:
       *15 November 2013*
via the instructions at:
       http://www.w3.org/WAI/RD/2013/e-learning/cfp.html

Background on 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 your ideas for future RDWG work. Please send comments to the publicly-archived mailing list: public-wai-rd@w3.org

This Symposium is developed with support of the EC-funded WAI-ACT Project (IST 287725) described at: http://www.w3.org/WAI/ACT/

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: http://bit.ly/rdmobile1 [@@ slh remember to set it up @@@@@@@@@@@@@@@@@@]

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

notes:

previous one

Tweet (MAXIMUM 140 characters)

Share your #E-Learning #Accessibility info! Call for Papers for online R&D Symposium: http://bit.ly/rdmobile1 - deadline 15 Nov #a11y

(136)

notes & brainstorms:

previous one

5imgDESC2013-03

DRAFT W3C Home Page (and Newsletters):

HTML Image Description Extension Draft Published

The HTML Working Group today published HTML Image Description Extension as First Public Working Draft. This specification ("HTML-longdesc") enables web authors to provide longer text descriptions for complex images. It defines the "longdesc" attribute to link descriptions with images in HTML5 content. HTML-longdesc is an extension specification that is part of the HTML5 family of specifications, which enables it to evolve independently and be finalized more rapidly. It is developed by the HTML Accessibility Task Force in coordination with the HTML WG and the WAI Protocols and Formats Working Group (PFWG). HTML-longdesc is part of W3C's work to ensure that the Open Web Platform is accessible to people with disabilities. Please see important additional information in the call for review e-mail. Learn more about HTML Activity and the Web Accessibility Initiative (WAI).

notes:

DRAFT WAI Highlight for home page & RSS feed:

longdesc: HTML Image Description Extension Draft Published

HTML Image Description Extension was published today as a First Public Working Draft. This specification ("HTML-longdesc") enables web authors to provide longer text descriptions for complex images. It defines the "longdesc" attribute to link descriptions with images in HTML5 content. HTML-longdesc is an extension specification that is part of the HTML5 family of specifications, which enables it to evolve independently and be finalized more rapidly. Please see important additional information in the Call for Review: HTML Image Description Extension e-mail. (2013-03-12)

notes:

DRAFT WAI IG email:

Call for Review: HTML Image Description Extension (longdesc)

Dear WAI Interest Group Participants,

The W3C HTML Working Group today published the First Public Working Draft of:
HTML Image Description Extension
http://www.w3.org/TR/html-longdesc

This specification ("HTML-longdesc") enables web authors to provide longer text descriptions for complex images. It defines the "longdesc" attribute to link descriptions with images in HTML5 content.

HTML-longdesc is an extension specification that is part of the HTML5 family of specifications [1], which enables it to evolve independently and be finalized more rapidly. HTML-longdesc is part of W3C's work to ensure that the Open Web Platform [2] is accessible to people with disabilities [3].

Based on this publication, the following changes will be implemented in the coming weeks:
* W3C validator [4] will validate longdesc as conforming HTML5.
* longdesc will be removed from the HTML obsolete features list.

Comments: Please send any comments on this Draft to the publicly archived HTML Accessibility Task Force mailing list:
public-html-a11y@w3.org
by 10 April 2013

Working Groups: HTML-longdesc was developed by the HTML Accessibility Task Force under the WAI Protocols and Formats Working Group (PFWG) and the HTML Working Group (HTML WG). [5]

About the URI: The first URI above goes to the latest version of the specification. The "dated" version of this Working Draft is: <http://www.w3.org/TR/2013/WD-html-longdesc-20130312/> The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: <http://www.w3.org/WAI/intro/linking>

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, WAI Outreach
HTML Accessibility Task Force Co-Facilitators: Steve Faulkner, Charles McCathie-Neville, Janina Sajka
HTML WG Chairs: Paul Cotton, Sam Ruby, Maciej Stachowiak
PFWG Chair: Janina Sajka
W3C Staff: Judy Brewer, Michael Cooper, Philippe Le Hégaret, Michael Smith

[1] Blog about extension specifications <http://www.w3.org/QA/2012/09/getting_html5_to_recommendatio>
[2] Open Web Platform standards <http://www.w3.org/standards/> @@ better link for this? request: https://lists.w3.org/Archives/Team/w3t-comm/2013Mar/0226.html @@
[3] Accessibility - W3C <http://www.w3.org/standards/webdesign/accessibility>
[4] HTML Validator (W3C Markup Validation Service) <http://validator.w3.org/>
[5] HTML Accessibility Task Force <http://www.w3.org/WAI/PF/html-accessibility-tf>
W3C WAI PFWG <http://www.w3.org/WAI/PF/>
W3C HTML WG <http://www.w3.org/html/wg/>

notes:

DRAFT Tweet (MAXIMUM 140 characters)

#longdesc for #HTML5. Please see important info in http://bit.ly/longdesc1 on HTML Image Description Extension #wai #a11y

(1@@)

notes & brainstorms:

W3C Q&A blog post:

[would be good to do, but not enough time I think]

notes:

RoleAttR

W3C Home Page (and Newsletters):

Role Attribute 1.0 is a W3C Recommendation

The Protocols and Formats Working Group (PFWG) today published an Role Attribute 1.0 as a Web Standard "W3C Recommendation". Role Attribute allows authors to annotate markup languages with machine-extractable semantic information about the purpose of an element. Role Attribute is a critical requirement for WAI-ARIA (Accessible Rich Internet Applications) to make the web more accessible to people with disabilities. Learn more about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

Web Standard: Role Attribute

Role Attribute 1.0 was published on 14 March 2013 as a Web Standard "W3C Recommendation". Role Attribute allows authors to annotate markup languages with machine-extractable semantic information about the purpose of an element. Role Attribute is a critical requirement for WAI-ARIA (Accessible Rich Internet Applications). (2013-03-14)

notes:

WAI IG email:

Role Attribute is published Web Standard

Dear WAI Interest Group Participants,

W3C WAI announces the publication of Role Attribute 1.0 as a Web Standard "W3C Recommendation" on 14 March, at:
http://www.w3.org/TR/role-attribute/

Role Attribute allows authors to annotate markup languages with machine-extractable semantic information about the purpose of an element. Role Attribute is a critical requirement for WAI-ARIA (Accessible Rich Internet Applications), which is introduced at <http://www.w3.org/WAI/intro/aria.php>

About the URI: The first URI above goes to the latest version of the document. The "dated" version of this CR version is: <http://www.w3.org/TR/@@/>
The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: <http://www.w3.org/WAI/intro/linking>

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

notes:

Dec 2012 PR e-mail

Tweet (MAXIMUM 140 characters)

Role Attribute published Web Standard. It supports WAI-ARIA (Accessible Rich Internet Applications) http://bit.ly/wai-ariaO - #a11y #aria

(137)

notes & brainstorms:

W3C Q&A blog post:

[ @@ Michael might draft @@ ]

notes:

title brainstorms:

...

body brainstorms:

NOTE: This information is an unapproved draft and should not be referenced or quoted under any circumstances.

aria-ap-2013mar

W3C Home Page (and Newsletters):

WAI-ARIA 1.0 Authoring Practices Draft with Updated Guidance

The Protocols and Formats Working Group (PFWG) today published an updated Working Draft of WAI-ARIA 1.0 Authoring Practices: An author's guide to understanding and implementing Accessible Rich Internet Applications. It provides detailed advice and examples to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. It is primarily for web application developers, and is also useful for user agent and assistive technology developers. Please send comments by 5 April 2013. Learn more from the call for review e-mail and read about the Web Accessibility Initiative (WAI).

notes:

title ideas:
- WAI-ARIA 1.0 Authoring Practices Draft with Updated Best Practice
- WAI-ARIA 1.0 Authoring Practices Draft Updated State of the Art
- Call for Review: WAI-ARIA 1.0 Authoring Practices Draft with updated Best Practice

WAI Highlight for home page & RSS feed:

WAI-ARIA Authoring Practices: Updated Guidance

The Working Draft of WAI-ARIA 1.0 Authoring Practices: An author's guide to understanding and implementing Accessible Rich Internet Applications is now updated to provide the current state of the art in WAI-ARIA implementation. It provides detailed advice and examples to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. It is primarily for web application developers, and is also useful for user agent and assistive technology developers. See @@Call for Review: WAI-ARIA Authoring Practices e-mail. Please send comments by 5 April 2013. (2013-03-07)

notes:

title ideas:
- WAI-ARIA Authoring Practices: Updated Guidance for Implementation
- WAI-ARIA Authoring Practices: Updated State of the Art
- For Review: WAI-ARIA Authoring Practices
Other wording options:

The Working Draft of WAI-ARIA 1.0 Authoring Practices: An author's guide to understanding and implementing Accessible Rich Internet Applications is now updated to provide the current state of the art in WAI-ARIA implementation

WAI IG email:

WAI-ARIA Authoring Practices: Updated Guidance

Dear WAI Interest Group Participants,

Guidance on the the current state of the art in WAI-ARIA implementation is available in the updated Working Draft of:
WAI-ARIA 1.0 Authoring Practices: An author's guide to understanding and implementing Accessible Rich Internet Applications
http://www.w3.org/TR/wai-aria-practices/

Overview:
WAI-ARIA Authoring Practices is a supporting document for the WAI-ARIA (Accessible Rich Internet Applications) technical specification, which is introduced at: <http://www.w3.org/WAI/intro/aria>.
WAI-ARIA Authoring Practices provides detailed advice and examples to make widgets, navigation, and behaviors accessible using WAI-ARIA roles, states, and properties. It is primarily for web application developers, and is also useful for user agent and assistive technology developers.

Draft:
This Draft has important updates since the previous publication. It is still being developed and does not yet address all known issues. To see a history of changes, responses to previous comments, and a list of review questions for this Draft, see the Status section at: <http://www.w3.org/TR/wai-aria-practices/#sotd>

Comments:
Please submit any comments on this draft by *5 April 2013*, via Comment Form or e-mail as described in:
Comment Instructions for PFWG Documents
http://www.w3.org/WAI/PF/comments/instructions

Editors' Draft in progress:
If you would like to see in-progress updates before the next version is published, you can read the unapproved Editors' Draft at: <http://www.w3.org/WAI/PF/aria-practices/>

Background:
WAI-ARIA documents are developed by the W3C WAI Protocols and Formats Working Group (PFWG), <http://www.w3.org/WAI/PF/>.

Not to be confused with ATAG:
WAI-ARIA Authoring Practices is different from Authoring Tool Accessibility Guidelines (ATAG), which defines what *tools* need to do for accessibility. WAI-ARIA, ATAG, and other standards are listed in WAI Guidelines and Techniques at: <http://www.w3.org/WAI/guid-tech.html>

About the URI:
The first URI above goes to the latest version of the document. The "dated" version of this Working Draft is: <http://www.w3.org/TR/2013/WD-wai-aria-practices-20130307/>
The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: <http://www.w3.org/WAI/intro/linking>

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.

notes:

Michael remember to update <http://www.w3.org/WAI/PF/comments/instructions>
(see above for other title/subject line options)

Tweet (MAXIMUM 140 characters)

WAI-ARIA Authoring Practices updated - Understanding & Implementing Accessible Rich Internet Applications http://bit.ly/aap33 -#a11y #aria

(137)

notes & brainstorms:

URI to go to WAI IG e-mail

Train2013Feb

W3C Home Page (and Newsletters):

Developing Web Accessibility Presentations and Training Resource Material

The Education and Outreach Working Group (EOWG) today published Developing Web Accessibility Presentations and Training, which provides materials for speakers, lecturers, educators, and other presenters to help their participants understand more about web accessibility. It includes a range of information from introductory slides for those new to accessibility, to updated statistics and demos for experienced trainers. To share your tips, guidance, and suggestions, see the WAI IG e-mail for links to the WAI-Engage wiki. Learn more about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

Developing Web Accessibility Presentations and Training: Resource Material

Developing Web Accessibility Presentations and Training provides materials for speakers, lecturers, educators, and other presenters to help their participants understand more about web accessibility. It includes a range of information from introductory slides for those new to accessibility, to updated statistics and demos for experienced trainers. To share your tips, guidance, and suggestions, see the WAI IG e-mail for links to the WAI-Engage wiki. (2013-02-21)

notes:

...
Helps you develop presentations and training on web accessibility.

WAI IG email:

Developing Web Accessibility Presentations and Training - resource material

Dear WAI Interest Group Participants,

Developing Web Accessibility Presentations and Training is updated at:
<http://www.w3.org/WAI/training/>

It provides materials for speakers, lecturers, educators, and other presenters to help their participants understand more about web accessibility. It is a multi-page resource that includes a range of information from introductory slides for those new to accessibility, to updated statistics and demos for experienced trainers.

We encourage you to share your tips, guidance, and suggestions in the Presentations and Training WAI-Engage wiki page at:
<http://www.w3.org/community/wai-engage/wiki/Presentations_and_Training_on_Web_Accessibility>
To learn more about the WAI-Engage Web Accessibility Community Group, see:
<http://www.w3.org/community/wai-engage/>

For those attending CSUN next week, we'd love to see you at the Training Resource Suite for Web Accessibility session:
Wednesday, February 27 at 8:00am
Madeleine AB, 3rd Floor

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

notes:

Tweet (MAXIMUM 140 characters)

Guidance for Developing Web #Accessibility Presentations and Training updated. Share your ideas. Links in: http://bit.ly/wapt32 --#a11y

(135)

notes & brainstorms:

W3C Q&A blog post:

not doing

IndieUI-2013-Jan-22

W3C Home Page (and Newsletters):

IndieUI: Events - New Work for Mobile and More

The IndieUI Working Group today published a First Public Working Draft of IndieUI: Events 1.0 - Events for User Interface Independence. IndieUI defines a way for different user interactions to be translated into simple events and communicated to web applications. (For example, if a user wants to scroll down a page, they might use their finger on a touch screen, or click a scroll bar with a mouse, or use a scroll wheel, or say "scroll down" with a voice command. With IndieUI, these are all sent to the web app as simply: scroll down.) IndieUI will make it easier for web applications to work in a wide range of contexts — different devices (such as mobile phones and tablets), different assistive technologies (AT), different user needs. With IndieUI, web application developers will have a uniform way to design applications that work for multiple devices and contexts. Comments on this Draft are encouraged by 22 February 2013. Learn more from the IndieUI Overview and the IndieUI: Events expands user interface interactions blog post; read about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

For Review: IndieUI Events for Mobile and More

IndieUI defines a way for different user interactions to be translated into simple events and communicated to web applications. (For example, if a user wants to scroll down a page, they might use their finger on a touch screen, or click a scroll bar with a mouse, or use a scroll wheel, or say "scroll down" with a voice command. With IndieUI, these are all sent to the web app as simply: scroll down.)

IndieUI will make it easier for web applications to work in a wide range of contexts — different devices (such as mobile phones and tablets), different assistive technologies (AT), different user needs. With IndieUI, web application developers will have a uniform way to design applications that work for multiple devices and contexts.

We published the First Public Working Draft of IndieUI: Events today. See:

IndieUI Overview for a short introduction,
IndieUI: Events expands user interface interactions blog post (also invites participation),
IndieUI: Events 1.0 - Events for User Interface Independence - technical specification,
Mobile Accessibility to learn about related work.

Please send comments on this Draft by 22 February 2013. (2013-01-22)

title brainstorms:

IndieUI Events for Mobile and More: For Review
IndieUI Events: New for Review
IndieUI Events: Cool New Work for Review

WAI IG email:

Exciting New Work for Mobile and More -- IndieUI: Events Call for Review

Dear WAI Interest Group Participants,

In 2012, W3C WAI started work on "IndieUI" - Independent User Interface - to help web applications work better with different devices (such as mobile phones and tablets), different assistive technologies (AT), and different user needs.

To learn about IndieUI, see the Overview page at:
http://www.w3.org/WAI/intro/indieui

Today we published the First Public Working Draft of IndieUI: Events technical specification at:
http://www.w3.org/TR/2013/WD-indie-ui-events-20130122/
We would like comments on this Draft by 22 February 2013 to the publicly-archived e-mail list:
public-indie-ui-comments@w3.org

To learn more about this work and how you can get involved, see "IndieUI: Events expands user interface interactions" blog post at:
http://www.w3.org/QA/2013/01/indie-ui_events_fpwd

To learn about WAI's work on mobile accessibility, see:
http://www.w3.org/WAI/mobile/

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.

notes:

title ideas:
- Call for Review: IndieUI Events -- Exciting New Work for Mobile and More

Tweet (MAXIMUM 140 characters)

Cool new work for mobile, assistive technologies, & more. IndieUI! Overview: http://bit.ly/IndieUIo ; blog: http://bit.ly/@@@@@@; #a11y

(135)

notes & brainstorms:

... (@@)

W3C Q&A blog post:

[Michael drafted]

WCAG2ICT-r2d2

W3C Home Page (and Newsletters):

Guidance on Applying WCAG 2.0 to Non-Web ICT: Updated Draft Published

The Web Content Accessibility Guidelines Working Group (WCAG WG) today published an updated Working Draft of Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT). It is a draft of an informative (that is, not normative) W3C Working Group Note that will clarify how Web Content Accessibility Guidelines (WCAG) 2.0 can be applied to non-Web ICT. Please see important information in the Call for Review e-mail. Comments are welcome through 15 February 2013. Read about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

Guidance on Applying WCAG 2.0 to Non-Web ICT: Updated Draft Published

An updated Working Draft of Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) is now available for review. Please see important information in the Call for Review: Guidance on Applying WCAG 2.0 to Non-Web ICT e-mail. Comments are welcome through 15 February 2013. (2012-12-13)

notes:

WAI IG email:

Call for Review: Guidance on Applying WCAG 2.0 to Non-Web ICT

Dear WAI Interest Group,

WAI invites you to comment on the updated Working Draft of Guidance on Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) that is available at:
http://www.w3.org/TR/wcag2ict/

It is an informative supporting document for WCAG 2.0. It is not normative, does not set requirements, and does not change the scope of WCAG 2.0 itself. It is planned to be a W3C Working Group Note.

This document includes existing wording from WCAG 2.0 -- the principles, guidelines, success criteria -- and the Intent sections from Understanding WCAG 2.0. It provides additional guidance on applying each success criteria to non-Web documents and software.

Status and Comment Replies:
This updated draft includes many changes in response to comments received on the previous Working Draft. The Task Force is continuing to process comments, and will respond to commenters after completing the comments processing.

While the structure and approach of this draft is complete, there are some sections yet to be written (which are indicated with "The WCAG2ICT Task Force has not yet produced additional guidance..."), and we expect additional edits based on review comments.

Review:
We particularly seek comments on the Key Terms defined in this draft and the "Additional Guidance" sections.

Please send comments on this draft to the publicly-archived mailing list:
public-wcag2ict-comments@w3.org
*by 15 February 2013*

About the related documents:
* The focus of this review is the Additional Guidance sections (not the wording taken from other documents).
* Understanding WCAG 2.0 is being updated. It will continue to focus on web technologies and not be changed to specifically address non-web ICT.
* WCAG 2.0 itself is a stable Web Standard that will not change.
* If you have comments on the wording taken from WCAG 2.0 or Understanding WCAG 2.0, please read the Instructions for Commenting on WCAG 2.0 Documents at: http://www.w3.org/WAI/WCAG20/comments/

About the URI:
The first URI in this e-mail goes to the latest version of the document. The "dated" version of this draft is: <http://www.w3.org/TR/2012/WD-wcag2ict-20121213/>
The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: <http://www.w3.org/WAI/intro/linking.html>

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, W3C, WAI Outreach
Loretta Guarino Reid, Google Inc., WCAG WG Co-Chair
Gregg Vanderheiden, Trace R&D Center, WCAG WG Co-Chair
Andi Snow-Weaver, IBM Corporation, WCAG2ICT TF Co-Facilitator
Mike Pluke, Castle Consulting, WCAG2ICT TF Co-Facilitator
Michael Cooper, W3C, WCAG WG and WCAG2ICT TF Staff Contact
Judy Brewer, W3C, WAI Director

notes:

RoleAt12 Role Attribute

W3C Home Page (and Newsletters):

Role Attribute Proposed Recommendation Published

The Protocols and Formats Working Group (PFWG) published a Proposed Recommendation of Role Attribute, an XML attribute that allows authors to add semantic information to documents. Role Attribute supports WAI-ARIA, the Accessible Rich Internet Applications technical specification for making dynamic, interactive web content accessible to people with disabilities. Comments are welcome through 1 February 2013. Read the Role Attribute Proposed Recommendation e-mail announcement for more information, and about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

Role Attribute is a Proposed Recommendation

Role Attribute 1.0 is published as a Proposed Recommendation. The next stage is final publication, as explained in How WAI Develops Accessibility Guidelines through the W3C Process. Role Attribute allows authors to add semantic information to documents, which is a requirement of WAI-ARIA. For additional information, see the Role Attribute 1.0 is a Propose Recommendation e-mail. (2012-12-13)

notes:

WAI IG email:

Role Attribute is a W3C Proposed Recommendation

Dear WAI Interest Group,

W3C WAI announces the publication of Role Attribute 1.0 as a W3C Proposed Recommendation on 13 December, at:
http://www.w3.org/TR/role-attribute/

Proposed Recommendation (PR) is the last stage before final publication as a Web Standard "W3C Recommendation". The W3C Process stages are described in:
How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process

Please submit any comments via the instructions at:
http://www.w3.org/WAI/PF/comments/instructions
before *1 February 2013*

About the URI: The first URI above goes to the latest version of the document. The "dated" version of this CR version is: http://www.w3.org/TR/2012/PR-role-attribute-20121213/
The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: http://www.w3.org/WAI/intro/linking.html

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, WAI Outreach
Janina Sajka. PFWG Chair
Michael Cooper, PFWG W3C Staff Contact
Judy Brewer, WAI Director

notes:

WCAG-EM 20 Sep 2012

W3C Home Page (and Newsletters):

For Review: Website Accessibility Conformance Evaluation Methodology (WCAG-EM)

An updated Working Draft of Website Accessibility Conformance Evaluation Methodology (WCAG-EM) was published today by the Web Content Accessibility Guidelines Working Group (WCAG WG) and Evaluation and Repair Tools Working Group (ERT WG), through the joint WCAG 2.0 Evaluation Methodology Task Force (Eval TF). WCAG-EM describes an approach for evaluating how websites — including web applications and websites for mobile devices — conform to WCAG 2.0. Learn more from the call for review e-mail and about the Web Accessibility Initiative (WAI).

notes:

usually start with the name of the WG; however, given it's 2 WGs through 1 TF, maybe too complex. w3t-comm folks: feel free to edit this part.
revised from previous draft:
- added "(WCAG-EM)" to headline
- edited last sentence

WAI Highlight for home page & RSS feed:

For Review: Website Accessibility Conformance Evaluation Methodology (WCAG-EM)

WAI invites you to review the updated Working Draft of Website Accessibility Conformance Evaluation Methodology (WCAG-EM). For more information, see the Call for Review: Website Accessibility Conformance Evaluation Methodology (WCAG-EM) e-mail. Please send any comments on this draft by 20 October 2012. (2012-09-20)

notes:

changes from previous draft:
- added "(WCAG-EM)" to headline
- delete "that was published today"

WAI IG email:

Call for Review: Website Accessibility Conformance Evaluation Methodology (WCAG-EM)

Dear WAI Interest Group Participants,

WAI invites you to comment on the updated Working Draft of Website Accessibility Conformance Evaluation Methodology (WCAG-EM) at:
http://www.w3.org/TR/WCAG-EM/

Overview:
WCAG-EM describes an approach for evaluating how websites -- including web applications and websites for mobile devices -- conform to Web Content Accessibility Guidelines (WCAG) 2.0. It covers different situations, including self-assessment and third-party evaluation. It is independent of particular evaluation tools, web browsers, and assistive technologies.

Draft:
This draft has proposed content for all sections. Now is a good time to review it. We are particularly looking for feedback on the applicability of this methodology in practice and for input on refining and expanding the guidance provided. Specific questions are indicated with "Review Note" in the draft.

@@added - heh@@
Comments:
Please send comments on this draft document to the publicly archived mailing list:
public-wai-evaltf@w3.org
by *20 October 2012*

Background:
WCAG-EM is developed by the WCAG 2.0 Evaluation Methodology Task Force (Eval TF), a joint task force of the Web Content Accessibility Guidelines Working Group (WCAG WG) and Evaluation and Repair Tools Working Group (ERT WG). The Eval TF is introduced at: <http://www.w3.org/WAI/ER/2011/eval/eval-tf>
It is a supporting resource for WCAG 2.0 and does not replace or supersede it in any way. For an overview of WCAG, see <http://www.w3.org/WAI/intro/wcag>
This work is developed with support of the EC-funded WAI-ACT Project (IST 287725) described at: <http://www.w3.org/WAI/ACT/>
It is part of W3C WAI activities on web accessibility evaluation and testing introduced at: <http://www.w3.org/WAI/ER/2011/eval/>

URI:
The first URI above goes to the latest version of the document. The "dated" version of this draft is: <http://www.w3.org/TR/2012/WD-WCAG-EM-20120920/>
The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: <http://www.w3.org/WAI/intro/linking.html>

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, WAI Outreach
Eric Velleman, Eval TF Facilitator
Shadi Abou-Zahra, W3C/WAI Staff Contact

notes:

previous draft had:
"Draft:
This updated draft is based on the same approach and expands the previous first public working draft of 27 March 2012. It addresses the comments received since and highlights areas where input is particularly requested. The group is particularly looking for feedback on the applicability of this methodology in practice and for input on refining and expanding the guidance provided."

Tweet (MAXIMUM 140 characters)

...

(@@)

notes & brainstorms:

...
(139)

W3C Q&A blog post:

not doing

mobile2012-Sept

W3C Home Page (and Newsletters):

Mobile Accessibility Resources Updated

The Education and Outreach Working Group (EOWG) published updated resources related to mobile accessibility. They cover how mobile accessibility is addressed in existing W3C standards/guidelines, and how the overlap between mobile web design/development and accessibility strengthens the business case. Learn more from the Mobile Accessibility Resources e-mail and read about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

Mobile Accessibility: Resources Updated

See the Mobile Accessibility Resources e-mail for links to updated information on how mobile web accessibility is addressed in existing W3C standards/guidelines, and how the overlap between mobile web design/development and accessibility strengthens the business case. (2012-09-10)

notes:

WAI IG email:

Mobile Accessibility Resources

Dear WAI Interest Group Participants,

New and updated information related to mobile accessibility is now available online.

A new WAI page that summarizes existing and developing resources related to mobile accessibility — that is, making websites and applications more accessible to people with disabilities when they are using mobile phones and a broad range of other devices:
* Mobile Accessibility
http://www.w3.org/WAI/mobile/Overview.html

Updated WAI pages:
* Web Content Accessibility and Mobile Web: Making a Website Accessible Both for People with Disabilities and for Mobile Devices
    http://www.w3.org/WAI/mobile/overlap.html
* Shared Web Experiences: Barriers Common to Mobile Device Users and People with Disabilities
    http://www.w3.org/WAI/mobile/experiences.html
* Developing a Web Accessibility Business Case for Your Organization
    http://www.w3.org/WAI/bcase/Overview.html

Related information:
* Promoting accessibility through the mobile overlap - Social Networking Application Business Case
http://www.w3.org/community/wai-engage/wiki/Social_Networking_Application_Business_Case

Please let us know if you have any questions.

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

notes:

Tweet (MAXIMUM 140 characters)

Mobile #Accessibility - making mobile web & apps work for people with disabilities http://bit.ly/maWAI (plus business case updates) #ally

(139)

notes & brainstorms:

W3C Q&A blog post:

not doing just because of time

RDWGcall-e2r

W3C Home Page (and Newsletters):

Easy-to-Read on the Web - Online Symposium - Call for Papers

The Research and Development Working Group (RDWG) will hold an online symposium to explore easy-to-read language to meet the needs of people with cognitive disabilities or low language skills. The Call for Papers is open until 12 October 2012. Learn more about the Easy-to-Read on the Web Symposium and the Web Accessibility Initiative (WAI).

notes:

mobile one, metrics one

WAI Highlight for home page & RSS feed:

Call for Papers: Easy-to-Read on the Web Symposium

The Research and Development Working Group (RDWG) will hold an online symposium to explore the needs of easy-to-read language for people with cognitive disabilities or low language skills. See the Easy to Read on the Web Symposium page. The Call for Papers is open until 12 October 2012. (2012-08-28)

notes:

mobile CfP, metrics CfP, metrics announcement of symposium

WAI IG email:

Call for Papers: Easy-to-Read on the Web - Online Symposium

Dear WAI Interest Group:

The W3C WAI Research and Development Working Group (RDWG) invites you to contribute to the online symposium on Easy-to-Read on the Web.
Submission date: 12 October 2012
Symposium date: 3 December 2012

This symposium brings together researchers, practitioners, content authors, designers, and developers, and users with disabilities to explore the needs of people with cognitive disabilities or low language skills. It is intended to encourage the development of better guidance, support, and tools for developers, designers, and users, and to inform researchers, standards developers, and policy makers on how to better address easy-to-read on the Web.

We invite research and position papers of about 1,000 words. Submissions will be peer-reviewed.

Accepted papers will be published online in an attributable form as part of the symposium proceedings. Authors of accepted papers will be invited to participate in the symposium panel.

*For more information about the symposium and submissions, please see*:
- Easy-to-Read on the Web main page: <http://www.w3.org/WAI/RD/2012/easy-to-read/>
- Call for Papers: <http://www.w3.org/WAI/RD/2012/easy-to-read/cfp.html>

If you are interested in contributing to this Symposium, please submit your paper by:
*12 October 2012*

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

---------
RDWG Background:

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.

RDWG Symposia bring together researchers, practitioners, and users with disabilities interested in a particular aspect of web accessibility to advance research and development in that area. The online Symposia include a panel with the authors of accepted papers, and provide an opportunity for participants to ask questions. Symposia proceedings, transcript, and a report are available publicly online afterward.

For more information, see the RDWG FAQ: <http://www.w3.org/WAI/RD/process>

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

This Symposium is developed with support of the EC-funded WAI-ACT Project (IST 287725) described at: <http://www.w3.org/WAI/ACT/>

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

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

notes:

mobile one, metrics one

Tweet (MAXIMUM 140 characters)

#CfP Easy to Read on the Web exploring needs of people w/ cognitive disabilities or low language http://bit.ly/RDe2r1 Due 12 October #a11y

(000)

notes:

mobile one, metrics one

MetricsFPWD

W3C Home Page (and Newsletters):

Web Accessibility Metrics Research Report Draft Published

The Research and Development Working Group (RDWG) today published the First Public Working Draft of the Research Report on Web Accessibility Metrics, a W3C Working Group Note that was developed from the Web Accessibility Metrics Symposium. Comments are welcome through 30 September 2012. Learn more from the Call for Review announcement, and read about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

For Review: Web Accessibility Metrics Research Report

The First Public Working Draft of Research Report on Web Accessibility Metrics, a W3C Working Group Note, is now available for review. See the Call for Review: Web Accessibility Metrics Research Report e-mail for more information. Comments are welcome through 30 September 2012. (2012-08-30)

notes:

body brainstorms:

The Research Report on Web Accessibility Metrics is now available for review. It is the First Public Working Draft of a W3C Working Group Note that was developed by the Research and Development Working Group (RDWG), based on the Web Accessibility Metrics Symposium. See Call for Review: Web Accessibility Metrics Research Report e-mail for more information. Comments are welcome through 23 July 2012. (2012-06-@@)

WAI IG email:

Call for Review: Web Accessibility Metrics Research Report

Dear WAI Interest Group Participants,

The W3C WAI Research and Development Working Group (RDWG) invites you to comment on the First Public Working Draft of the Research Report on Web Accessibility Metrics, a W3C Working Group Note, available at:
http://www.w3.org/TR/accessibility-metrics-report/

Accessibility metrics can extend the existing WCAG 2.0 conformance model to provide scores for the accessibility level of websites in more depth and detail. This Report provides considerations for validity, reliability, sensitivity, adequacy, and complexity as the main qualities of measuring web accessibility. The Report is a consolidated view of the outcomes of the Website Accessibility Metrics Online Symposium; information about the Symposium is at: http://www.w3.org/WAI/RD/2011/metrics/

For this draft, RDWG is looking for feedback on:
* Summaries of the extended abstracts contributed to the online symposium
* Discussion on the state-of-the-art and conclusions drawn in the document
* Related resources that may be useful to the discussion within the document

Please send comments on this draft document to the publicly archived mailing list
public-wai-rd-comments@w3.org
*by 30 September 2012*

Background on 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 your ideas for future RDWG work. Please send comments to the publicly-archived mailing list: public-wai-rd@w3.org

This research report is developed with support of the EC-funded WAI-ACT Project (IST 287725) described at: http://www.w3.org/WAI/ACT/

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

notes:

Tweet (MAXIMUM 140 characters)

...

(@@)

notes & brainstorms:

RDWGcall2012May

NOTE: announcements postponed until related Easy-to-Read Symposium more developed

W3C Home Page (and Newsletters):

Text Customization for Readability - Online Symposium - Call for Papers

The Research and Development Working Group (RDWG) will hold an online symposium to explore the needs of people with low vision, dyslexia, and other conditions and situations that impact reading. The Call for Papers is open until 24 September 2012. Learn more about the Text Customization for Readability Symposium and the Web Accessibility Initiative (WAI).

notes:

mobile one, metrics one

WAI Highlight for home page & RSS feed:

Call for Papers: Text Customization for Readability Symposium

The Research and Development Working Group (RDWG) will hold an online symposium to explore the needs of people with low vision, dyslexia, and other conditions and situations that impact reading. See the Text Customization for Readability Symposium page. The Call for Papers is open until 24 September 2012. (2012-04-05)

notes:

mobile CfP, metrics CfP, metrics announcement of symposium

WAI IG email:

Call for Papers: Text Customization for Readability - Online Symposium

Dear WAI Interest Group:

The W3C WAI Research and Development Working Group (RDWG) invites you to contribute to the online symposium on Text Customization for Readability.
Submission date: 24 September 2012
Symposium date: 19 November 2012

This symposium brings together researchers, practitioners, and users with disabilities to explore the needs of people with low vision, dyslexia, and other conditions and situations that impact reading.

We invite research and position papers of about 1,000 words. We encourage you to submit new research, ongoing research, and analysis of past research related to text customization for readability. Submissions will be peer-reviewed.

Accepted papers will be published online in an attributable form as part of the symposium proceedings. Authors of accepted papers will be invited to participate in the symposium panel.

*For more information about the symposium and submissions, please see*:
- Text Customization for Readability Symposium main page: <http://www.w3.org/WAI/RD/2012/text-customization/>
- Call for Papers: <http://www.w3.org/WAI/RD/2012/text-customization/cfp.html>

If you are interested in contributing to this Symposium, please submit your paper by:
*24 September 2012*

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

---------
RDWG Background:

For more information, see the RDWG FAQ: <http://www.w3.org/WAI/RD/process>

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

This Symposium is developed with support of the EC-funded WAI-ACT Project (IST 287725) described at: <http://www.w3.org/WAI/ACT/>

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

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

notes:

mobile one, metrics one

Tweet (MAXIMUM 140 characters)

#CfP: Text Customization for #Readability – exploring low vision, #dyslexia, & more. See bit.ly/tc4r1 Papers due 24 Sept. #a11y

(000)

notes:

mobile one, metrics one

IndieUI

W3C Home Page (and Newsletters):

W3C Launches Indie UI Working Group

Today W3C Launched the new Independent User Interface (Indie UI) Working Group that will collaborate with the Web Events WG to develop a way for user actions to be communicated to web applications. Indie UI will develop an intermediate layer between device- and modality-specific events and the functionality needed by web applications, e.g., scrolling the view, placing focus on an object, etc. Indie UI will define a way for different user actions (e.g., scrolling via touch screen, via mouse wheel, or via voice commend) to be translated into a simple event. Then web application developers can get these events from different devices without having to recognize how the user performed the action. Learn more from the announcement e-mail and read about the Web Accessibility Initiative (WAI).

body drafts:

Shawn's Tue morning draft:
Today W3C Launched the new Independent User Interface (Indie UI) Working Group to develop a way for user actions to be communicated to web applications. This will make it easier for web applications to work with a wide range of devices, including assistive technologies (AT). Indie UI will develop an intermediate layer between device- and modality-specific events and the functionality needed by web applications, e.g., scrolling the view, placing focus on an object, etc. Indie UI will define a way for different user actions (e.g., scrolling via touch screen, via mouse wheel, or via voice commend) to be translated into a simple event. Then web application developers can get these events from different devices without having to recognize how the user performed the action. With IndieUI, AT and other devices will have a simple set of events to control web applications, and web applications will have a uniform way to design applications that work for multiple devices and contexts. The Indie UI WG will collaborate with the Web Events WG. Learn more from the announcement e-mail and read about the Web Accessibility Initiative (WAI).
Michael's Tuesday morning draft:
Today W3C Launched the new Independent User Interface (Indie UI) Working Group to develop a set of events to represent user intent in interaction with Web applications, regardless of device-specific interaction. Per its charter, the group will create an intermediate layer between device- and modality-specific events and the functionality needed by Web applications. It will define actions which are prevalent among GUI and Web applications at this time, such as scrolling the view, canceling an action, changing the value of a user input widget, selecting a range, placing focus on an object, etc. These are basic user interface gestures that are common to most platforms but are actuated in various ways depending on hardware features, system design, and user interaction modality, yet via Indie UI can be exposed in a simple and universal manner to Web applications. This work will be expressed in two technical specifications: Indie UI: Events, and Indie UI: User Context; along with requirements, tests, and other supporting materials. The Indie UI WG will collaborate with the Web Events WG on these deliverables.

WAI Highlight for home page & RSS feed:

Indie UI: New Independent User Interface Working Group

Today W3C WAI launched the new Independent User Interface (Indie UI) Working Group to develop a way for user actions to be communicated to web applications. This will make it easier for web applications to work with a wide range of devices, including assistive technologies (AT). To learn more, see the Indie UI e-mail. (2012-05-22)

notes:

The e-mail has an example that we encourage people to read to help understand the work of the group.

WAI IG email:

Indie UI: New Independent User Interface Working Group

Dear WAI Interest Group Participants,

The W3C WAI today launched the new Independent User Interface (Indie UI) Working Group to develop a way for user actions to be communicated to web applications. This will make it easier for web applications to work with a wide range of devices, including assistive technologies (AT).

For example, if a user wants to scroll down a page, they might use their finger on a touch screen, or click a scroll bar with a mouse, or say "scroll down" with a voice command. Indie UI will define a way for those different interactions to be translated into a simple event - scroll down.

Indie UI will allow web application developers to get these events from different devices without having to recognize how the user performed the action. With IndieUI, AT will have a simple set of events to control web applications, and web applications will have a uniform way to design applications that work for multiple devices and contexts.

To learn more about Indie UI, see:
* Indie UI Working Group page http://www.w3.org/WAI/IndieUI/
* Indie UI Chater http://www.w3.org/2012/05/indie-ui-charter

We invite user agent developers, web application developers, and other interested in this work to participate. For options ranging from joining the Working Group to following the e-mail list, see:
* Participating in the Indie UI Working Group http://www.w3.org/WAI/IndieUI/participation

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 message: @@@@@@@

Regards,
Shawn Lawton Henry, WAI Outreach
Janina Sajka, IndieUI Chair
Michael Cooper, W3C Staff Contact

other ideas:

alt subject: W3C WAI launches Independent User Interface (Indie UI) Working Group
[first paragraph, alt second sentnece:] This will allow a wide range of devices, including assistive technologies, to better interact with web applications.

Tweet (MAXIMUM 140 characters)

Indie UI will make web applications work better with different devices, inc. assistive technologies. See http://bitly/IndieUI #a11y #w3c

(137)

notes & brainstorms:

Indie UI will make web applications work better with different devices, including assistive technologies. See http://bitly/IndieUI #a11y
(137)

W3C Q&A blog post:

not doing

notes:

...Indie UI WG is to develop event models for APIs that facilitate interaction in Web applications that are input method independent, and hence accessible to people with disabilities. These events allow the use of alternate input devices such as assistive technologies, while providing a simple model for authors to develop interaction for a wide array of devices.
make it independent of
way for authors to be able to create web applications that respond to users' intended action without careing about the specific way users perform that action
developing set [dom events] ... specification that defines these functions (such as scolling...).. ways of expressing those sorts of actions to web applications... allowing the device to map them to specific user input
tech: dynamic web apps now if the app wants to do X (allow you to scorll), not standard way of doing it, so the app has to listen to touch events series (close in location & time -- determine vertical scroll events
apps listen for complicated events
AT can't send meaningful event -- cause even ti sidff on diff platforms
INdieUI "vertical scroll" - simple thing
device does the translation - I saw a swip, I'll call that a scroll
eg scoolr down noe page voice input, device translate "scroll event" and send to application
not worry about simulating user input that very device specific

ARIA-UA-Aug12

W3C Home Page (and Newsletters):

WAI-ARIA User Agent Implementation Guide Working Draft Published

The Protocols and Formats Working Group (PFWG) today published an updated Working Draft of WAI-ARIA 1.0 User Agent Implementation Guide, which describes how browsers and other user agents should support WAI-ARIA (the Accessible Rich Internet Applications specification); specifically, how to expose WAI-ARIA features to platform accessibility APIs. Comments are welcome through 21 September. Learn more in the call for review e-mail and read about the Web Accessibility Initiative (WAI).

notes:

Do we want a short one more like above? or more information, like below?
Jan 2012 news: The Protocols and Formats Working Group has published a Last Call Working Draft of WAI-ARIA 1.0 User Agent Implementation Guide. This document describes how user agents should support keyboard navigation and respond to roles, states, and properties provided in Web content via WAI-ARIA. These features are used by authors creating accessible rich internet applications. Users often access the content using assistive technologies that rely on platform accessibility APIs to obtain and interact with information from the page. The WAI-ARIA User Agent Implementation Guide defines how implementations should expose content to accessibility APIs, helping to ensure that this information appears in a manner consistent with author intent. This document is part of the WAI-ARIA suite described in the WAI-ARIA Overview. Comments are welcome through 17 February. Learn more about the WAI Technical Activity.
NOTE: Shawn doesn't know where all this wording came from -- the news blurb is significantly different from what was drafted.

WAI Highlight for home page & RSS feed:

For Review: WAI-ARIA 1.0 User Agent Implementation Guide

We invite you to review an updated Working Draft of WAI-ARIA 1.0 User Agent Implementation Guide, which describes how browsers and other user agents should support WAI-ARIA (the Accessible Rich Internet Applications specification); specifically, how to expose WAI-ARIA features to platform accessibility APIs. See the Call for Review: WAI-ARIA 1.0 User Agent Implementation Guide e-mail for more information. Please send comments by 21 September 2012. (2012-08-16)

notes:

Jan 2012 highlight

WAI IG email:

Call for Review: WAI-ARIA User Agent Implementation Guide

Dear WAI Interest Group Participants,

The W3C WAI Protocols and Formats Working Group (PFWG) invites you to comment on an updated Working Draft of:
WAI-ARIA 1.0 User Agent Implementation Guide
http://www.w3.org/TR/wai-aria-implementation/

This Guide is part of the Accessible Rich Internet Applications (WAI-ARIA) suite described in:
WAI-ARIA Overview
http://www.w3.org/WAI/intro/aria.php

This WAI-ARIA 1.0 User Agent Implementation Guide is for developers of web browsers and other user agents. It describes how user agents should support WAI-ARIA; specifically, how to expose WAI-ARIA features to platform accessibility APIs (application programming interfaces). For more information, see the Abstract at http://www.w3.org/TR/wai-aria-implementation/#abstract

The accessibility API mappings in this Guide will be used to test WAI-ARIA through the "Candidate Recommendation" phase. To learn more about Last Call and Candidate Recommendation, see:
How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process

Note about Working Draft status: The Guide was published as a Last Call Working Draft in January 2012. The Protocols and Formats Working Group (PFWG) decided to return to Working Draft stage based on the changes since the last Draft. The Working Group expects to publish the second Last Call Working Draft in the coming months and plans to continue the Guide to completion soon after, and therefore requests that any comments be made on this current draft.

For review questions, a history of changes, and information on testing with WAI-ARIA, see the Status section at http://www.w3.org/TR/wai-aria-implementation/#sotd

Please send comments by *21 September 2012* to the publicly-archived list via the comment form available by following the instructions from:
http://www.w3.org/WAI/PF/comments/instructions
Alternatively, you can e-mail comments to public-pfwg-comments@w3.org

About the URI: The first link above goes to the latest version of the document. The "dated" version is: <http://www.w3.org/TR/2012/WD-wai-aria-implementation-20120816/>/ The difference between these links are explained in Referencing and Linking to WAI Guidelines and Technical Documents at <http://www.w3.org/WAI/intro/linking.html>

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.

notes:

Jan 2012 msg

Tweet (MAXIMUM 140 characters)

...

(@@)

notes & brainstorms:

...
(139)

W3C Q&A blog post:

not doing

WCAG2ICT FPWD

W3C Home Page (and Newsletters):

Applying WCAG 2.0 to Non-Web ICT - First Draft Published

The Web Content Accessibility Guidelines Working Group (WCAG WG) today published the First Public Working Draft of Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT). It is a draft of an informative (that is, not normative) W3C Working Group Note that will clarify how Web Content Accessibility Guidelines (WCAG) 2.0 can be applied to non-Web ICT. Please see important background information in the Call for Review e-mail. Comments are welcome through 7 September 2012. Read about the Web Accessibility Initiative (WAI).

title ideas:

Applying WCAG 2.0 to Non-Web ICT First Draft Published
Applying WCAG 2.0 to Non-Web ICT: First Draft Published
First Draft of Applying WCAG 2.0 to Non-Web ICT Published
First Public Draft of Applying WCAG 2.0 to Non-Web ICT
First Draft of Applying WCAG 2.0 to Non-Web ICT

notes:

first version: The Web Content Accessibility Guidelines Working Group (WCAG WG) today published the First Public Working Draft of Applying WCAG 2.0 to Non-Web Information and Communications Technologies, a W3C Working Group Note to support uniform adoption of the Web Content Accessibility Guidelines (WCAG) 2.0. Comments are welcome through @Day@ @Month@ 2012. Read about the Web Accessibility Initiative (WAI).
- do we really want to say "to support uniform adoption of WCAG"? that sounds like are asserting that we think WCAG should be adopted [in policies] for non-Web-ICTs.
...

WAI Highlight for home page & RSS feed:

Applying WCAG 2.0 to Non-Web ICT: First Draft Published

The First Public Working Draft of Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) is now available for review. Please see important background information in the Call for Review: Applying WCAG 2.0 to Non-Web ICT e-mail. Comments are welcome through 7 September 2012. (2012-07-07)

(see above for title ideas)

notes:

previous draft: The First Public Working Draft of Applying WCAG 2.0 to Non-Web Information and Communications Technologies, a W3C Working Group Note, is now available for review. See Call for Review: Applying WCAG 2.0 to Non-Web ICT e-mail for more information. Comments are welcome through @Day@ @Month@ 2012. (2012-07-07)

WAI IG email:

Call for Review: Applying WCAG to Non-Web ICT

Dear WAI Interest Group Participants,

WAI invites you to comment on the First Public Working Draft of Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT) that is available at:
http://www.w3.org/TR/wcag2ict/

About this document:
This draft document provides guidance on how Web Content Accessibility Guidelines (WCAG) 2.0 can be applied to non-web information and communications technologies (ICT), specifically documents and software. It does not discuss whether or not WCAG 2.0 should be applied to non-Web ICT.
This draft is an informative supporting document for WCAG 2.0. It is not normative, does not set requirements, and does not change the scope of WCAG 2.0 itself. It is planned to be a W3C Working Group Note.

Status:
The WCAG WG believes the structure and approach of this document is complete. It includes existing wording from WCAG 2.0 -- the principles, guidelines, success criteria -- and the Intent sections from Understanding WCAG 2.0. It provides additional guidance on applying each success criteria to electronic documents and software, including the software aspects of products.
In this draft, there are some sections yet to be written (which are indicated with "The WCAG2ICT Task Force has not yet produced additional guidance..."), there are some questions and editor's notes to be addressed, and we expect additional edits based on review comments.

Review and comments:

For this draft, we particularly seek comments on:
* The overall approach of the document.
* The "Additional Guidance" in this draft.
* Additional key terms to be defined in this document.
* Is it necessary or helpful to provide guidance on applying the principles and/or guidelines? (This draft currently provides guidance only for success criteria.) Note that only the success criteria are used for determining conformance to WCAG 2.0.

Comments are welcome on this draft document via the publicly-archived mailing list:
public-comments-wcag20@w3.org
*by 7 September 2012*

About the URI:
The first URI in this e-mail goes to the latest version of the document. The "dated" version of this draft is: http://www.w3.org/TR/2012/WD-wcag2ict-20120727/
The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: http://www.w3.org/WAI/intro/linking.html

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.

notes:

other good wording:
It is intended to help clarify how to use WCAG 2.0 to make non-web ICT more accessible to people with disabilities.
previous draft:

WAI invites you to comment on the First Public Working Draft of Applying WCAG 2.0 to Non-Web Information and Communications Technologies (WCAG2ICT), a W3C Working Group Note, available at:
     http://www.w3.org/TR/WCAG2ICT/

*About this document*:
This draft document provides guidance on how Web Content Accessibility Guidelines (WCAG) 2.0 *can* be applied to non-web information and communications technologies (ICT), specifically documents and software. It does not discuss whether or not WCAG 2.0 *should* be applied to non-Web ICT.

This draft is an informative supporting document for WCAG 2.0. It is not normative, does not set requirements, and does not change the scope of WCAG 2.0 itself.

This document includes existing wording from WCAG 2.0 -- the principles, guidelines, success criteria -- and the Intent sections from Understanding WCAG 2.0. It provides additional guidance on applying each success criteria to electronic documents and software, including the software aspects of products.

*Review and comments*:
See the Status section for specific review questions. Note that the main focus of this review is the Additional Guidance sections. WCAG 2.0 itself is a stable document that will not change. Understanding WCAG 2.0 is currently being updated (per the e-mail archived at @@), although it will not be changed to specifically address non-web ICT.

Please send comments on the Additional Guidance sections of this draft document to the publicly-archived mailing list:
     public-comments-wcag20@w3.org
     *by 7 September 2012*

If you have comments on the wording taken from WCAG 2.0 or Understanding WCAG 2.0, please submit those comments via web form or e-mail, per the Instructions for Commenting on WCAG 2.0 Documents at: http://www.w3.org/WAI/WCAG20/comments/

About the URI:
The first URI above goes to the latest version of the document. The "dated" version of this draft is: http://www.w3.org/TR/2012/@@
The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: http://www.w3.org/WAI/intro/linking.html

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.
first draft:
The W3C WAI Web Content Accessibility Guidelines Working Group (WCAG WG) invites you to comment on the First Public Working Draft of Applying WCAG 2.0 to Non-Web Information and Communications Technologies, a W3C Working Group Note, available at:
http://www.w3.org/TR/WCAG2ICT/

This documents supports a uniform adoption of WCAG 2.0 by describing how its principles, guidelines, success criteria and conformance model can be applied to non-Web ICT, including non-web documents and software. It is an informative supporting document for WCAG 2.0 and does not change the scope or meaning of WCAG 2.0 itself. The document also does not provide techniques for implementing WCAG 2.0 in non-Web ICT and does not discuss whether or not WCAG 2.0 or any of its provisions should be applied to non-Web ICT.

For this draft, WCAG WG is looking for feedback on:
* @@@
- do we really want to say "to support uniform adoption of WCAG"? that sounds like are asserting that we think WCAG should be adopted [in policies] for non-Web-ICTs.
...

Tweet (MAXIMUM 140 characters)

WCAG2ICT draft helps clarify how to use WCAG 2.0 to make non-web ICT, docs & software, more accessible http://bit.ly/wcag2ict1 #a11y #ict

(137)

notes & brainstorms:

short URI to goes to the WAI IG e-mail
WCAG2ICT draft published with informative guidance on how WCAG can apply to non-web ICT, docs & software http://bit.ly/wcag2ict1 #a11y #ict
(139)

W3C Q&A blog post:

guess we're not doing 'cause not enough time, but I think would have been good to do in order to provide important clarifications in a way that is easier to read than the Intro...

WCAG-Understanding-July2012

W3C Home Page (and Newsletters):

Shawn suggests not doing W3C Home Page news since this is Editor's Draft one of two. Probably do W3C Home Page when we have the final draft.

notes:

similar 21 June 2011 announcement

WAI Highlight for home page & RSS feed:

Understanding WCAG 2.0: Updates in progress

The WCAG Working Group is updating a supporting document for WCAG 2.0 and a draft is available for review: 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 Understanding WCAG 2.0: Updates in progress e-mail. (2012-07-27)

notes:

similar 21 June 2011 announcement

title brainstorms:

For Review: Updating Understanding WCAG 2.0

WAI IG email:

Understanding WCAG 2.0: Updates in progress

Dear WAI Interest Group Participants,

The WCAG Working Group is currently updating a supporting document for WCAG 2.0: Understanding WCAG 2.0. (This is not an update to WCAG 2.0, which is a stable document.) The supporting documents (W3C Working Group Notes) are updated periodically to reflect current practices and technologies. The existing Understanding WCAG 2.0 document remains in place as a Note while the separate Editors' Draft is updated and reviewed, and the Working Group addresses comments.

An updated Editors' Draft is available from:
http://www.w3.org/WAI/GL/2012/WD-UNDERSTANDING-WCAG20-20120726/

Most of the updates in this Editors' Draft are clarifying the Intent of success criteria. Changes since the January 2012 published version are highlighted in a diff-marked version at:
http://www.w3.org/WAI/GL/2012/WD-UNDERSTANDING-WCAG20-20120726/complete-diff.html

The Working Group expects to provide another updated Editors' Draft for review in the coming months, and early comments on these updates are welcome. Please send any comments on Understanding WCAG 2.0 via web form or e-mail, per the Instructions for Commenting on WCAG 2.0 Documents at:
http://www.w3.org/WAI/WCAG20/comments/

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

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, WAI Outreach
Gregg Vanderheiden and Loretta Guarino Reid, WCAG Co-Chairs
Michael Cooper, W3C Staff Contact

notes:

similar 21 June 2012 e-mail

Tweet (MAXIMUM 140 characters)

Understanding WCAG 2.0 updates in progress. Draft for review available. See http://bit.ly/wcag2ub #a11y #wcag

W3C Q&A blog post:

not doing

RDWG-mobile-reg

W3C Home Page (and Newsletters):

Online Symposium: Mobile Accessibility

Registration is now open for the online symposium on mobile accessibility to be held on 25 June 2012. The symposium is intended for researchers and practitioners who want to explore mobile accessibility challenges and solutions, and help develop a roadmap for future research and development. For details and registration, see Mobile Accessibility - Online Symposium. Learn more about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

Online Symposium: Mobile Accessibility

notes:

WAI IG email:

Registration Open: Mobile Accessibility - Online Symposium - 25 June 2012

Dear WAI Interest Group Participants,

The W3C WAI Research and Development Working Group (RDWG) invites you to participate in the online symposium on mobile accessibility on 25 June 2012 at 15:00-17:00 UTC. Agenda, logistics, and registration information is available from:
Mobile Accessibility Online Symposium
http://www.w3.org/WAI/RD/2012/mobile/

This symposium is intended for researchers and practitioners who want to explore mobile accessibility challenges and solutions, and help develop a roadmap for future research and development. It not include a general introduction to web accessibility. Space is limited; we recommend that you register soon to reserve a space.

About RDWG Symposia:
RDWG Symposia bring together researchers, practitioners, and users with disabilities interested in a particular aspect of web accessibility to advance research and development in that area. The online Symposia include a panel with the authors of accepted papers, and provide an opportunity for participants to ask questions. Symposia proceedings, transcript, and a report are available publicly online afterward.

Background on 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 your ideas for future RDWG work. Please send comments to the publicly-archived mailing list: public-wai-rd@w3.org

This Symposium is developed with support of the EC-funded WAI-ACT Project (IST 287725) described at: http://www.w3.org/WAI/ACT/

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: http://bit.ly/RDmobileR@@@

notes:

Tweet (MAXIMUM 140 characters)

Registration open for #Mobile #Accessibility - Online Symposium – 25 June. Space limited. Info at http://bit.ly/RDmobileR #a11y #ux

(131)

notes & brainstorms:

shortlink will go to http://www.w3.org/WAI/RD/2012/mobile/

ATAG2012Feb

W3C Home Page (and Newsletters):

Last Call: Authoring Tool Accessibility Guidelines (ATAG) 2.0 and Implementing ATAG 2.0

The Authoring Tool Accessibility Guidelines Working Group has published an updated Last Call Working Draft of Authoring Tool Accessibility Guidelines (ATAG) 2.0 and a Working Draft of 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. Comment deadline is 5 June 2012. Learn more in the announcement e-mail and read about the Web Accessibility Initiative (WAI).

notes:

low profile

title brainstorms:

...

body brainstorms:

WAI Highlight for home page & RSS feed:

Calling All Authoring Tool Developers: ATAG 2 for You

WAI encourages developers of web authoring tools (content management systems, HTML editors, social networking apps, and more), to start using ATAG 2.0 Working Draft. It's in Last Call Working Draft stage, which means we think it's stable, yet it might change somewhat based on feedback and implementation experience. See:

ATAG *Last Call* Working Draft,
ATAG Overview,
How WAI Develops Accessibility Guidelines through the W3C Process: Milestones and Opportunities to Contribute.

Please send any comments on this Last Call Working Draft by 5 June 2012. (2012-04-10)

notes:

title brainstorms:

...

body brainstorms:

WAI IG email:

Subject: ATAG 2.0 Last Call Working Draft published

Dear WAI Interest Group Participants,

WAI has published an updated Last Call Working Drafts of the Authoring Tool Accessibility Guidelines (ATAG) 2.0 at:
http://www.w3.org/TR/ATAG20/
and an updated Working Draft of Implementing ATAG 2.0 at:
http://www.w3.org/TR/IMPLEMENTING-ATAG20/

Last Call:
This third ATAG 2.0 Last Call Working Draft is provided for public review now that all resolutions from previous comments are incorporated. The Authoring Tool Accessibility Guidelines Working Group (AUWG) hopes that it has resolved all substantive issues with this draft, and looks forward to progressing to the next stages in completing ATAG 2.0. Last Call and the other development stages are described in: How WAI Develops Accessibility Guidelines through the W3C Process at http://www.w3.org/WAI/intro/w3c-process

Test Drive Today:
WAI encourages developers of web authoring tools (content management systems, HTML editors, social networking, and more[1]), to try using the ATAG 2.0 Working Draft now. (While we think it is stable, it might change some based on public feedback and implementation experience.) We are looking forward to learning about your experience implementing ATAG 2.0 in your tools. In the coming months, we'll be asking for tools that meet ATAG 2.0. *Will your tool be an example?*

Recent updates:
For a list of changes since the last draft, see the Status section: http://www.w3.org/TR/ATAG20/#status

Comments:
If there are any issues that you think could present a barrier to future adoption and implementation of ATAG 2.0, please submit comments to the publicly-archived list: public-atag2-comments@w3.org by *5 June 2012*

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/

URI:
The first URIs above go to the latest version of the documents. The "dated" version of these drafts are: http://www.w3.org/TR/2012/WD-ATAG20-20120410/ and http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410//
The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: http://www.w3.org/WAI/intro/linking.html

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)

If you develop web authoring tools (CMS, LMS, web editors, etc), see ATAG 2.0 Last Call Working Draft http://bit.ly/ATAG-LCa #a11y

(@@)

notes & brainstorms:

... (000)

W3C Q&A blog post:

not doing

RDWGcall2012March

W3C Home Page (and Newsletters):

Mobile Accessibility - Online Symposium - Call for Papers

The Research and Development Working Group (RDWG) will hold an online symposium to explore mobile accessibility challenges, existing resources, and areas for future research and development. The Call for Papers is open until 7 May 2012. Learn more about the Symposium on Mobile Accessibility and the Web Accessibility Initiative (WAI).

notes:

previous one
previous draft: The Research and Development Working Group (RDWG) will hold an online symposium for researchers, practitioners, and users with disabilities to explore mobile accessibility challenges, existing resources, and [areas|needs|opportunities] for future research and development. The Call for Papers is open until 7 May 2012. Learn more about the Symposium on Mobile Accessibility and the Web Accessibility Initiative (WAI).
title ideas:
- W3C Announces Online Symposium on Mobile Accessibility

WAI Highlight for home page & RSS feed:

Call for Papers: Mobile Accessibility Symposium

The Research and Development Working Group (RDWG) will hold an online symposium to explore mobile accessibility challenges, existing resources, and areas for future research and development. The Call for Papers is open until 7 May 2012. See Call for Papers: Mobile Accessibility - Online Symposium e-mail. (2012-03-05)

notes:

previous CfP, previous announcement of symposium
title ideas:
- Symposium: Mobile Accessibility

WAI IG email:

Call for Papers: Mobile Accessibility - Online Symposium

Dear WAI Interest Group Participants,

The W3C WAI Research and Development Working Group (RDWG) invites you to share your experiences with mobile accessibility for an online Symposium to be conducted on 25 June 2012. See:
       Mobile Accessibility Online Symposium
       http://www.w3.org/WAI/RD/2012/mobile/

The primary objective of this symposium is to gather, analyze, and discuss practical experience with mobile web accessibility. In particular, the objective is to investigate:
* the technical challenges in terms of API, platform, browser, applications, and web content accessibility;
* the coverage of mobile accessibility by existing standards such as UAAG, WCAG, MWBP, and MWABP;
* new interaction models such as touch interfaces and their accessibility.

RDWG Symposia bring together researchers, practitioners, and users with disabilities interested in a particular aspect of web accessibility to advance research and development in that area. The online Symposia include a panel with the authors of accepted papers, and provide an opportunity for participants to ask questions. Symposia proceedings, transcript, and a report are available publicly online afterward.

*If you are interested in contributing to this Symposium*, please submit your paper by:
       *7 May 2012*
via the instructions at:
       http://www.w3.org/WAI/RD/2012/mobile/cfp.html

Background on 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 your ideas for future RDWG work. Please send comments to the publicly-archived mailing list: public-wai-rd@w3.org

This Symposium is developed with support of the EC-funded WAI-ACT Project (IST 287725) described at: http://www.w3.org/WAI/ACT/

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

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

notes:

previous one

Tweet (MAXIMUM 140 characters)

Share your #Mobile #Accessibility info! Call for Papers for online R&D Symposium: http://bit.ly/rdmobile1 - deadline 7 May #a11y

(136)

notes & brainstorms:

previous one

Eval TF Mar 2012

W3C Home Page (and Newsletters):

Website Accessibility Conformance Evaluation Methodology (WCAG-EM) Draft Published

The First Public Working Draft of Website Accessibility Conformance Evaluation Methodology (WCAG-EM) was published today by the Web Content Accessibility Guidelines Working Group (WCAG WG) and Evaluation and Repair Tools Working Group (ERT WG), through the joint WCAG 2.0 Evaluation Methodology Task Force (Eval TF). WCAG-EM provides an approach for evaluating how websites — including web applications and websites for mobile devices — conform to WCAG 2.0. Learn more about WCAG-EM Website Accessibility Conformance Evaluation Methodology Draft Published and the Web Accessibility Initiative (WAI).

notes:

I think technically TFs don't publish things, only the WGs do. I assume we want to list the TF though. I know we usually put the WG names first to make it active voice; however, draft below is a lot to wade through before getting to the "meat" (the document itself). Happy to consider other approaches. ~shawn
Shadi's first draft:
The WCAG 2.0 Evaluation Methodology Task Force (Eval TF), a joint task force of the Web Content Accessibility Guidelines Working Group (WCAG WG) and Evaluation and Repair Tools Working Group (ERT WG), today published a First Public Working Draft of Website Accessibility Conformance Evaluation Methodology 1.0. The document [outlines|explains|provides] an approach for evaluating existing websites to WCAG 2.0 in different contexts, including self-assessment and third-party evaluation. Learn more about First Publication of Website Accessibility Conformance Evaluation Methodology 1.0 and the Web Accessibility Initiative (WAI).

WAI Highlight for home page & RSS feed:

Accessibility Evaluation Methodology First Draft

WAI invites you to review the First Public Working Draft of Website Accessibility Conformance Evaluation Methodology (WCAG-EM) that was published today. For more information, see the WCAG-EM Website Accessibility Conformance Evaluation Methodology Draft Published e-mail. Please send any comments on this early draft by 27 April 2012. (2012-03-27)

notes:

TF announcement http://www.w3.org/WAI/highlights/archive#x20110713a

title brainstorms:

Accessibility Evaluation Methodology First Draft
First Draft of Accessibility Evaluation Methodology
New Work on Website Evaluation
Call for Review: Accessibility Evaluation Methodology (assume not want to stress "call for review" really yet)

body brainstorms:

Shadi first draft:
New Work on Website Evaluation
A First Public Working Draft of Website Accessibility Conformance Evaluation Methodology 1.0 was published today for review by anyone interested in website evaluation. It [outlines|explains|provides] an approach for evaluating existing websites to WCAG 2.0 in different contexts, including self-assessment and third-party evaluation. See:
- First Publication of Website Accessibility Conformance Evaluation Methodology 1.0,
Please send comments by 27 April 2012. (2012-@@-@@)

WAI IG email:

WCAG-EM Website Accessibility Conformance Evaluation Methodology Draft Published

Dear WAI Interest Group Participants,

WAI invites you to comment on the First Public Working Draft of Website Accessibility Conformance Evaluation Methodology (WCAG-EM) at:
http://www.w3.org/TR/WCAG-EM/

Overview:
WCAG-EM provides an approach for evaluating how websites -- including web applications and websites for mobile devices -- conform to Web Content Accessibility Guidelines (WCAG) 2.0. It covers different situations, including self-assessment and third-party evaluation. It is independent of particular evaluation tools, web browsers, and assistive technologies.

Draft:
This early draft provides an initial outline for the evaluation methodology in order to gather feedback on the general direction and approach, in particular on its Scope of Applicability (Section 2.1). Some sections are empty in this draft and will be completed in future revisions, partly based on the feedback received on this draft.

Background:
WCAG-EM is developed by the WCAG 2.0 Evaluation Methodology Task Force (Eval TF), a joint task force of the Web Content Accessibility Guidelines Working Group (WCAG WG) and Evaluation and Repair Tools Working Group (ERT WG). The Eval TF is introduced at: http://www.w3.org/WAI/ER/2011/eval/eval-tf
It is a supporting resource for WCAG 2.0 and does not replace or supersede it in any way. For an overview of WCAG, see http://www.w3.org/WAI/intro/wcag
This work is developed with support of the EC-funded WAI-ACT Project (IST 287725) described at: http://www.w3.org/WAI/ACT/
It is part of W3C WAI activities on web accessibility evaluation and testing introduced at: http://www.w3.org/WAI/ER/2011/eval/

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, WAI Outreach
Eric Velleman, Eval TF Facilitator
Shadi Abou-Zahra, W3C/WAI Staff Contact

notes:

shadi's first draft

Tweet (MAXIMUM 140 characters)

#WCAG-EM Website #Accessibility Conformance Evaluation Methodology draft published (for apps & mobile too) http://bit.ly/wcag-em1 #a11y

(135)

notes & brainstorms:

shadi's first draft: W3C/WAI website accessibility evaluation methodology published as first draft!

W3C Q&A blog post:

not doing

Presentations 20Feb2012

W3C Home Page (and Newsletters):

How to Make Your Presentations Accessible to All is updated

The Web Accessibility Initiative (WAI) Education and Outreach Working Group (EOWG) has updated How to Make Presentations Accessible to All. This WAI resource helps you make presentations, meetings, training, conferences, etc. accessible to all of your potential audience, including people with disabilities and others. It covers planning, preparing slides, considerations during your presentation, providing accessible material, and other topics for conference organizers and presenters. Learn more in the blog post Make Your Presentations Accessible to All updated - share the news and visit the WAI home page.

notes:

June 2010 blurb

BAD2012a

W3C Home Page (and Newsletters):

BAD to Good Updated: 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 update e-mail and learn about Accessibility.

notes:

13 Oct 2011 blurb

WAI Highlight for home page & RSS feed:

BAD to Good Updated: 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 Update: Before and After Demonstration (BAD) e-mail. (2012-@@-@@)

notes:

13 Oct 2011 blurb

WAI IG email:

in wiki

notes:

Tweet (MAXIMUM 140 characters)

BAD to Good: Demo shows example website with #accessibility barriers and fixes http://bit.ly/BADshare Useful for presentations. #a11y

(@@)

notes & brainstorms:

other ideas in wiki
13 Oct 2011 tweet

W3C Q&A blog post:

not doing

wcag2011Dec

W3C Home Page (and Newsletters):

Updated Techniques for Web Content Accessibility Guidelines (WCAG) 2.0

The Web Content Accessibility Guidelines Working Group today published updates of two Notes that accompany WCAG 2.0: Techniques for WCAG 2.0 and Understanding WCAG 2.0. (This is not an update to WCAG 2.0, which is a stable document.) To learn more about WCAG Techniques and about contributing to future updates, see the WCAG Techniques Updated - Learn about the informative guidance blog post. Read about the Web Accessibility Initiative (WAI).

notes:

Oct 2010 news

WAI Highlight for home page & RSS feed:

More WCAG 2.0 Techniques

WAI continues to develop techniques for Web Content Accessibility Guidelines (WCAG) 2.0 and expand guidance on understanding and implementing WCAG 2.0. To learn about WCAG Techniques and about contributing to on-going work on WCAG support material, see the WCAG Techniques Updated - Learn about the informative guidance blog post. (2011-12-15)

notes:

Oct 2010 highlight

WAI IG email:

Updated WCAG 2.0 Techniques Published - Learn More...

Dear WAI Interest Group Participants,

W3C WAI today published updates to two supporting documents for Web Content Accessibility Guideline (WCAG) 2.0:
- Techniques for WCAG 2.0 http://www.w3.org/TR/WCAG20-TECHS/
- Understanding WCAG 2.0 http://www.w3.org/TR/UNDERSTANDING-WCAG20/

These supporting documents (called W3C Working Group Notes) are updated periodically to reflect current practices and technologies. This is not an update to WCAG 2.0, which is a stable document.

*Please read important information about WCAG Techniques in the following blog post*:
- WCAG Techniques Updated - Learn about the informative guidance
http://www.w3.org/QA/2012/01/wcag_techniques_learn_more.html

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

(Note: The first links above go to the latest version of the documents. The "dated" versions are:
- http://www.w3.org/TR/2012/NOTE-WCAG20-TECHS-20120103/
- http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/
The difference between these links are explained in Referencing and Linking to WAI Guidelines and Technical Documents at http://www.w3.org/WAI/intro/linking.html)

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

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

notes:

Oct 2010 e-mail

Tweet (MAXIMUM 140 characters)

New and Improved WCAG 2.0 Techniques for web #accessibility. Read about using techniques & how you can help at http://bit.ly/wcag1201 #a11y
(139)

notes & brainstorms:

Oct 2010 tweet
link will go to the blog post
... (139)

W3C Q&A blog post:

WCAG Techniques Updated - Learn about the informative guidance

Today W3C WAI published updated Techniques for WCAG 2.0 and Understanding WCAG 2.0, following a public review period. For background on the stable WCAG standard and this updated supporting material, read the October 2010 blog post.

About the Techniques

First, understand that the basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard — not the techniques. The Techniques document provides guidance that is "informative". You do not have to use the sufficient techniques to meet WCAG. Web content can use other ways to meet the WCAG success criteria. Web content could even fail a particular technique test, yet still meet WCAG a different way. Also, content that uses the published techniques does not necessarily meet all WCAG success criteria.

To learn more about the techniques, please see:

About the Techniques section of How to Meet WCAG 2.0: A customizable quick reference...
Sufficient and Advisory Techniques section of Understanding WCAG 2.0

About this Update

The updated documents published today include more coverage of non-W3C technologies (Flash, PDF, Silverlight), which will help developers who are using those technologies make their content more accessible. However, publication of techniques for a specific technology does not imply that the technology can be used in all cases to create accessible content that meets WCAG 2.0. (For example, the Flash Techniques for WCAG 2.0 say: "Flash accessibility support for assistive technology relies on use in Windows operating systems, using Internet Explorer 6 or later (with Flash Player 6 or later) or Mozilla Firefox 3 or later (with Flash Player 9 or later).") Developers need to be aware of the limitations of specific technologies and ensure that they create content in a way that is accessible to all their potential users.

Changes in this update are highlighted in diff-marked versions at: Techniques for WCAG 2.0 (Diff), Understanding WCAG (Diff).

(Note: The first links above go to the latest version of the documents. The "dated" versions of this update are: Techniques for WCAG 2.0 (dated URI), Understanding WCAG (dated URI) The difference between these links are explained in Referencing and Linking to WAI Guidelines and Technical Documents.)

Help Develop Techniques

Updating and expanding these WCAG supporting documents is on-going work, and we welcome your contributions.

You can send in your ideas for new techniques via the Techniques for WCAG 2.0 submission form.
You can comment on what's already there via the web form or e-mail listed in the Instructions for Commenting on WCAG 2.0 Documents.
You can actively participate in the WCAG Working Group, writing and reviewing new techniques.

And finally, a big thanks to the WCAG Working Group and everyone who is contributing to providing updated WCAG 2.0 Techniques!

notes:

Oct 2010 blog post: New and Improved WCAG 2.0 Techniques
About the Techniques is trying to clear up misunderstandings:
1) they think sufficient is required
2) only sufficient can be used
3) they think the tests in the techniques indicate failure of WCAG (and not just the technique)
Deleted:
We encourage you to read About the Techniques below.

Background: WCAG Standard and Supporting Material

Web Content Accessibility Guidelines (WCAG) 2.0 is a W3C standard that is designed to be stable and relevant even as technology changes. One of the benefits of WCAG 2.0 is that it applies to more advanced technologies, including current, future, and non-W3C technologies. WCAG 2.0 is broadly applicable and technology independent.

Detailed guidance, including technology-specific guidance, on meeting WCAG 2.0 is provided in the following supporting documents:
- Techniques for WCAG 2.0 - guidance for developers with general and technology-specific examples, including for HTML/XHTML, CSS, scripting, multimedia, Flash, PDF, Silverlight, and WAI-ARIA.
- Understanding WCAG 2.0 - includes the intent of the guideline or success criterion; how it helps people with different disabilities, browser and assistive technology support notes, examples, and resources.
These supporting documents are designed to be expanded and updated periodically to cover current practices and technologies. The first publication of these supporting documents covered the sufficient techniques and other basics, although they did not document all known techniques (some were marked as "future link") nor cover all technologies. Today's publication demonstrates WAI's continuing commitment to update the WCAG 2.0 supporting documents.

media2011Dec

W3C Home Page (and Newsletters):

First Draft of Media Accessibility User Requirements

The Protocols and Formats Working Group (PFWG) today published a First Public Working Draft of Media Accessibility User Requirements that describes the accessibility requirements of people with disabilities with respect to audio and video on the Web, particularly in the context of HTML5. Learn more from the call for review email and about the Web Accessibility Initiative (WAI).

notes:

WAI Highlight for home page & RSS feed:

First Draft of Media Accessibility User Requirements

We invite you to comment on the First Public Working Draft of Media Accessibility User Requirements that describes the accessibility requirements of people with disabilities with respect to audio and video on the Web, particularly in the context of HTML5. Learn more from the call for review email. Please send comments by 10 February 2012. (2012-01-03)

notes:

title brainstorms:

...

body brainstorms:

WAI IG email:

Call for Review: Media Accessibility User Requirements

Dear WAI Interest Group Participants,

The W3C WAI Protocols and Formats Working Group (PFWG) invites you to comment on the Working Draft of:
Media Accessibility User Requirements
http://www.w3.org/TR/media-accessibility-reqs

This document describes the accessibility requirements of people with disabilities with respect to audio and video on the Web, particularly in the context of HTML5. It explains alternative content technologies that people use to get audio and video content, and how these fit in the larger picture of accessibility, both technically within a web user agent and from a production process point of view. Additional information is in the document's Abstract and Status sections.

This is a First Public Working draft that will continue to be developed. PFWG plans to eventually publish it as a W3C Working Group Note.

WAI encourages you to provide feedback on this draft, particularly:
* Are the use cases for media accessibility clear and complete?
* Do the features to enhance media accessibility meet the use cases?
* Are the technical requirements for media accessibility complete and achievable?

Please send comments by *10 February 2012* to the publicly-archived list via:
* Comment form http://www.w3.org/WAI/PF/comments/instructions
Alternatively, you can e-mail comments to public-pfwg-comments@w3.org

(Note: The first link above goes to the latest version of the document. The "dated" version is:
http://www.w3.org/TR/2012/WD-media-accessibility-reqs-20120103/
The difference between these links are explained in Referencing and Linking to WAI Guidelines and Technical Documents at http://www.w3.org/WAI/intro/linking.html)

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, WAI Education and Outreach
Janina Sajka. PFWG Chair
Michael Cooper, PFWG W3C Staff Contact

notes:

Tweet (MAXIMUM 140 characters)

Media #Accessibility User Requirements for audio and video on the Web, particularly in context of #HTML5 - see http://bit.ly/mdia1 #a11y

(136)

notes & brainstorms:

... (139)

W3C Q&A blog post:

not doing

UIAG2012Jan

W3C Home Page (and Newsletters):

Last Call: WAI-ARIA 1.0 User Agent Implementation Guide

The Protocols and Formats Working Group (PFWG) today published the Last Call Working Draft of WAI-ARIA 1.0 User Agent Implementation Guide, which describes how browsers and other user agents should support WAI-ARIA (the Accessible Rich Internet Applications specification); specifically, how to expose WAI-ARIA features to platform accessibility APIs. Learn more in the call for review e-mail and read about the Web Accessibility Initiative (WAI).

WAI Highlight for home page & RSS feed:

For Review: WAI-ARIA 1.0 User Agent Implementation Guide - Last Call Working Draft

We invite you to review the Last Call Working Draft of WAI-ARIA 1.0 User Agent Implementation Guide, which describes how browsers and other user agents should support WAI-ARIA (the Accessible Rich Internet Applications specification); specifically, how to expose WAI-ARIA features to platform accessibility APIs. See the Call for Review: WAI-ARIA 1.0 User Agent Implementation Guide e-mail for more information. Please send comments by 17 February 2012. (2012-01-10)

WAI IG email:

Call for Review: WAI-ARIA 1.0 User Agent Implementation Guide - Last Call Working Draft

Dear WAI Interest Group Participants,

The W3C WAI Protocols and Formats Working Group (PFWG) invites you to comment on the Last Call Working Draft of:
WAI-ARIA 1.0 User Agent Implementation Guide
http://www.w3.org/TR/wai-aria-implementation/

This Guide is part of the Accessible Rich Internet Applications (WAI-ARIA) suite described in:
WAI-ARIA Overview
http://www.w3.org/WAI/intro/aria.php

This WAI-ARIA 1.0 User Agent Implementation Guide is for developers of web browsers and other user agents. It describes how user agents should support WAI-ARIA; specifically, how to expose WAI-ARIA features to platform accessibility APIs (application programming interfaces). For more details, see the Abstract at http://www.w3.org/TR/wai-aria-implementation/#abstract

The accessibility API mappings in this Guide will be used to test WAI-ARIA through the "Candidate Recommendation" phase. To learn more about Last Call and Candidate Recommendation, see:
How WAI Develops Accessibility Guidelines through the W3C Process
http://www.w3.org/WAI/intro/w3c-process

For review questions, a history of changes, and information on testing with WAI-ARIA, see the Status section at http://www.w3.org/TR/wai-aria-implementation/#sotd

Please send comments by *17 February 2012* to the publicly-archived list via the comment form available by following the instructions from:
http://www.w3.org/WAI/PF/comments/instructions
Alternatively, you can e-mail comments to public-pfwg-comments@w3.org

(Note: The first link above goes to the latest version of the document. The "dated" version is: http://www.w3.org/TR/2012/WD-wai-aria-implementation-20120110/ The difference between these links are explained in Referencing and Linking to WAI Guidelines and Technical Documents at http://www.w3.org/WAI/intro/linking.html)

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, WAI Education and Outreach
Janina Sajka, PFWG Chair
Michael Cooper, PFWG W3C Staff Contact

notes:

other draft wording not to lose yet:
- helps understand and implement Accessible Rich Internet Applications (WAI-ARIA). It describes how user agents should support keyboard navigation and respond to roles, states, and properties provided through WAI-ARIA. The Guide defines how implementations should expose content to accessibility APIs (application programming interfaces)

Tweet (MAXIMUM 140 characters)

WAI-ARIA User Agent Implementation Guide – browsers’ role in implementing Accessible Rich Internet Applications - http://bit.ly/auaig #a11y

(139)

W3C Q&A blog post:

not doing

First WAI-ACT Open Meeting

W3C Home Page (and Newsletters):

Not doing

WAI Highlight for home page & RSS feed:

Not doing

WAI IG email:

Registration Open: First WAI-ACT Open Meeting on 14 February 2012 in Brussels, Belgium

Dear WAI Interest Group Participants,

The WAI-ACT Project invites you to participate in its first open meeting on 14 February 2012 in Brussels, Belgium. Agenda, logistics, and registration information is available from:
http://www.w3.org/WAI/ACT/meeting1

This meeting is intended for web accessibility practitioners, researchers, and users to:
     - Learn more about the WAI-ACT Project
     - Provide input into project developments
     - Explore opportunities for collaboration

We encourage you to participate if you are interested in:
     - Authoritative guidance on the implementation of accessibility in advanced web technologies
     - Internationally harmonized methodologies to support evaluation of websites for accessibility
     - Common visions and contribution to a coordinated eAccessibility research agenda

We particularly invite participants involved in relevant projects, initiatives, and activities with interest in expanded cooperation in Europe and internationally on the development of accessibility solutions.

Background on the WAI-ACT Project:
The WAI-ACT Project is designed to build upon and expand W3C/WAI cooperation mechanisms to help address the need for expanded European and international cooperation on the development of accessibility solutions for people with disabilities. See more information about the WAI-ACT Project and its deliverables:
http://www.w3.org/WAI/ACT/

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: http://bit.ly/waiact1 @@@@@@@@@@@@@@@@@@@@@@@

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

Tweet (MAXIMUM 140 characters)

Registration open for First WAI-ACT Open Meeting on 14 February 2012 in Brussels, Belgium. See info at bit.ly/waiact1 -#a11y

(@@)

W3C Q&A blog post:

not doing

Planning Highlights on WAI Home Page and other announcements 2012-2013 Archive

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

Easy Checks - A First Review of Web Accessibility is updated for the holidays

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Q&A blog post:

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

For Review: WAI-ARIA User Agent Implementation Guide - Last Call Working Draft

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Q&A blog post:

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

Call for Papers: Accessible E-Learning Symposium

WAI IG email:

Tweet (MAXIMUM 140 characters)

DRAFT W3C Home Page (and Newsletters):

DRAFT WAI Highlight for home page & RSS feed:

longdesc: HTML Image Description Extension Draft Published

DRAFT WAI IG email:

DRAFT Tweet (MAXIMUM 140 characters)

W3C Q&A blog post:

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

Web Standard: Role Attribute

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Q&A blog post:

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

WAI-ARIA Authoring Practices: Updated Guidance

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

Developing Web Accessibility Presentations and Training: Resource Material

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Q&A blog post:

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

For Review: IndieUI Events for Mobile and More

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Q&A blog post:

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

Guidance on Applying WCAG 2.0 to Non-Web ICT: Updated Draft Published

WAI IG email:

RoleAt12 Role Attribute

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

Role Attribute is a Proposed Recommendation

WAI IG email:

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

For Review: Website Accessibility Conformance Evaluation Methodology (WCAG-EM)

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Q&A blog post:

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

Mobile Accessibility: Resources Updated

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Q&A blog post:

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

Call for Papers: Easy-to-Read on the Web Symposium

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

For Review: Web Accessibility Metrics Research Report

WAI IG email:

Tweet (MAXIMUM 140 characters)

W3C Home Page (and Newsletters):

WAI Highlight for home page & RSS feed:

Planning Highlights on WAI Home Page and other announcements
2012-2013 Archive