Planning Highlights on WAI Home Page and other announcements
Page Contents
Note: This Web page is an internal working draft and should not be referenced or quoted under any circumstances.
Drafts of upcoming highlights
WAI staff drafts [limited access]
Archive Draft Blurbs
to cut down on page & file size, archived notes were moved to:
- 2012 & 2013 are at planning-to-2013
- 2011 are at planning-to-2011
- 2010 are at planning-to-2010
- May 2008 - November 2009 were moved to planning-to-2009
- Through April 2008 were moved to planning-to-2008
NOTE: This information is an unapproved draft and should not be referenced or quoted under any circumstances.
Ordered with most recent at the top, oldest at the bottom:
IndieUIreq1
W3C Home Page (and Newsletters):
Requirements for IndieUI: Events 1.0 and IndieUI: User Context 1.0 First Public Working Draft Published
The Independent User Interface (Indie UI) Working Group today published the First Public Working Draft of Requirements for IndieUI: Events 1.0 and IndieUI: User Context 1.0. The document introduces use cases related to the IndieUI specifications and the technical requirements for meeting the use cases. IndieUI: Events defines a way for different user interactions to be translated into simple events and communicated to web applications. With IndieUI, web application developers will have a uniform way to design applications that work for multiple devices and contexts. It is introduced in the IndieUI Overview. One focus of IndieUI is enabling better user interaction in the mobile environment. This Requirements document provides an opportunity for early review of user needs to be addressed by the IndieUI specifications. Learn more about the Web Accessibility Initiative (WAI).
notes:
- ...
WAI Highlight for home page & RSS feed:
IndieUI Requirements First Draft
The First Public Working Draft of Requirements for IndieUI: Events 1.0 and IndieUI: User Context 1.0 is available for review. The document introduces use cases related to the IndieUI specifications and the technical requirements for meeting the use cases. IndieUI is introduced in the IndieUI Overview. One focus of IndieUI is enabling better user interaction in the mobile environment. This Requirements document provides an opportunity for early review of user needs to be addressed by the IndieUI specifications. Please send comments by 23 May 2014. (2014-04-22)
notes:
- This is an opportunity to make sure that user interaction needs are addressed in the mobile environment...
WAI IG email:
Call for Review: IndieUI Requirements
Dear WAI Interest Group Participants,
"IndieUI" - Independent User Interface - helps web applications work better with different devices (such as mobile phones and tablets), different assistive technologies (AT), and different user needs.
*Requirements for IndieUI: Events 1.0 and IndieUI: User Context 1.0* introduces use cases related to the IndieUI specifications and the technical requirements for meeting the use cases. The First Public Working Draft is available for review at:
http://www.w3.org/TR/indie-ui-requirements/
One focus of IndieUI is enabling better user interaction in the mobile environment. This Requirements document provides an opportunity for early review of user needs to be addressed by the two IndieUI specifications.
Please send any comments on this draft to the publicly-archived e-mail list:
public-indie-ui-comments@w3.org
by 23 May 2014
About IndieUI:
IndieUI: Events defines a way for different user interactions to be translated into simple events and communicated to web applications. With IndieUI, web application developers will have a uniform way to design applications that work for multiple devices and contexts.
To learn about IndieUI, see the Overview page at:
http://www.w3.org/WAI/intro/indieui
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 other work related to mobile accessibility, see:
http://www.w3.org/WAI/mobile/
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/2014/WD-indie-ui-requirements-20140422/> The difference between these URIs is 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:
- ...
notes & brainstorms:
- ...
Tutorials-intro
WAI Highlight for home page & RSS feed:
Web Accessibility Tutorials: Ready for Your Input
Draft Web Accessibility Tutorials are now ready for your input. See more info in the Web Accessibility Tutorials in Progress e-mail. (2014-03-17)
notes:
- (see notes under the WAI IG msg below)
WAI IG email:
Web Accessibility Tutorials in Progress
Dear WAI Interest Group Participants,
WAI invites you to provide input into our new Web Accessibility Tutorials at:
http://www.w3.org/WAI/tutorials/
We have a *draft framework* in place and welcome feedback on the navigation, visual design, etc.
The *Images tutorial* starting at <http://www.w3.org/WAI/tutorials/images/> is fairly complete and we welcome detailed feedback on the content. Specifically, we would like input on the use of the WAI-ARIA attributes aria-label and aria-labelledBy for images.
The *other draft tutorials* there (Tables, Forms, Sliders/ Carousel) are still rough, so you probably want to hold off on doing a detailed review.
Over the next few months, we'll be developing additional tutorials covering basic and advanced topics.
Please send any input to the publicly-archived mailing list:
<wai-eo-editors@w3.org>
or you can contibute directly via Github:
<https://github.com/w3c/wai-tutorials>
*For those at CSUN*, let's talk tutorials at:
The WAI to Web Accessibility: Education & Outreach Update 2014
Thursday 4:20pm
Gaslamp B, 2nd Floor, Seaport Tower
If you might be interested in actively contributing to the development of these tutorials as a participant in WAI's Education and Outreach Working Group (EOWG), please read Participating in WAI at <http://www.w3.org/WAI/participation> and Participating in the EOWG at <http://www.w3.org/WAI/EO/participation>, then contact Shawn Henry <http://www.w3.org/People/Shawn/>.
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:
- In-Progress? or in Progress? or In Progress?
or use different wording all together? - title brainstorms:
- Web Accessibility Tutorials: Ready for Your Input
- Web Accessibility Tutorials In Progress
Tweet (MAXIMUM 140 characters)
New Web Accessibility Tutorials will cover basic and advanced topics. Info: http://lists.w3.org/Archives/Public/w3c-wai-ig/2014JanMar/@@@@@ At #CSUN14 Thur 4:20 Gaslamp B #a11y
(@@)
notes & brainstorms:
- ...
WCAG2014Jan
W3C Home Page (and Newsletters):
For Review: Updated Techniques for Web Content Accessibility Guidelines (WCAG)
The Web Content Accessibility Guidelines Working Group (WCAG WG) requests review of draft updates to Notes that accompany WCAG 2.0: Techniques for WCAG 2.0 (Editors' Draft) and Understanding WCAG 2.0 (Editors' Draft). Comments are welcome through 14 February 2014. (This is not an update to WCAG 2.0, which is a stable document.) To learn more about the updates, see the Call for Review: WCAG 2.0 Techniques Draft Updates e-mail. Read about the Web Accessibility Initiative (WAI).
notes:
WAI Highlight for home page & RSS feed:
For Review: Updated WCAG 2.0 Techniques
WAI announces a Call for Review of draft updates to supporting documents for WCAG 2.0: Techniques for WCAG 2.0 (Editors' Draft) and Understanding WCAG 2.0 (Editors' Draft). (This is not an update to WCAG 2.0, which is a stable document.) To learn more about the updates, see Call for Review: WCAG 2.0 Techniques Draft Updates e-mail. Please submit comments by 14 February 2014. (2014-01-16)
notes:
WAI IG email:
Call for Review: WCAG 2.0 Techniques Draft Updates
Dear WAI Interest Group Participants,
The W3C WAI announces a Call for Review of updates to two supporting documents for Web Content Accessibility Guideline (WCAG) 2.0. *This is not an update to WCAG 2.0, which is a stable document*.
The supporting documents (W3C Working Group Notes) are updated periodically to reflect current practices and technologies. Previously they were updated about once a year. The WCAG Working Group plans to update them more frequently.
The existing Techniques and Understanding documents remain in place as W3C Notes while these separate draft updates are under review and the WCAG Working Group addresses comments.
The following draft updates are available for review as Editors' Drafts:
- Techniques for WCAG 2.0 Editors' Draft
http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/
- Understanding WCAG 2.0 Editors' Draft
http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/
The changes are highlighted in diff-marked versions at:
- http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/complete-diff.html
- http://www.w3.org/WAI/GL/2014/WD-UNDERSTANDING-WCAG20-20140107/complete-diff.html
Changes that apply to "How to Meet WCAG 2.0: A customizable quick reference..." are available in a draft at: <http://www.w3.org/WAI/WCAG20/quickref/20140107/>
Updates for review:
Most of the updates in this draft are new WAI-ARIA Techniques. The WCAG Working Group is still discussing appropriate ways to provide text alternatives for images -- specifically, is it OK to not provide an alt atribute and instead use ARIA attributes? We particularly request feedback about this issue and related techniques such as F65[1]. See the examples and details at:
- ARIA10: Using aria-labelledby to provide a text alternative for non-text content <http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/ARIA10>
Please send any comments on these Editors' Drafts by *14 February 2014*. Comments and contributions for additional WCAG 2.0 techniques can be sent via web form or e-mail, per:
- Instructions for Commenting on WCAG 2.0 Documents
http://www.w3.org/WAI/WCAG20/comments/
*Important notes about techniques*:
- The basis for determining conformance to WCAG 2.0 is the success criteria from the WCAG 2.0 standard -- not the techniques. W3C’s techniques are informative and are not intended to be required. Learn more from "Understanding Techniques for WCAG Success Criteria" at <http://www.w3.org/TR/UNDERSTANDING-WCAG20/understanding-techniques.html>
- 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. Developers need to be aware of the limitations of specific technologies and ensure that they provide content in a way that is accessible to all their potential users.
If you are interested in actively contributing to the development of additional WCAG 2.0 techniques and support material through the WCAG Working Group, please see:
- Participating in WAI< http://www.w3.org/WAI/participation> and contact Michael Cooper
For an introduction to the WCAG documents, see:
- WCAG Overview
http://www.w3.org/WAI/intro/wcag.php
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
Andrew Kirkpatrick, Adobe Systems Inc., WCAG WG Co-Chair
Joshue O Connor, WCAG WG Co-Chair
Michael Cooper, W3C, WCAG WG Staff Contact
---
[1] F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type "image" <http://www.w3.org/WAI/GL/2014/WD-WCAG20-TECHS-20140107/F65>
notes:
Tweet (MAXIMUM 140 characters)
#WCAG Techniques and Understanding WCAG draft updates for your review (by @@Month) http://lists.w3.org/Archives/Public/w3c-wai-ig/@@ -#a11y
(xx)
notes & brainstorms:
template @@doc date
WAI IG email:
CC: @@e-mail addresses for chairs, team contact, others in signature
Call for Review: @@
Dear WAI Interest Group Participants,
The W3C WAI @@ Working Group (@@WG) invites you to comment on...
Overview:
@@
Draft:
@@
Comments:
@@
Background:
@@
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/@@> 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
@@ WG Chair
@@ WG W3C Staff Contact
Judy Brewer, WAI Director
notes:
- @@ link to previous WAI IG e-mail from http://lists.w3.org/Archives/Public/w3c-wai-ig/
W3C Home Page (and Newsletters):
@@title
An updated Working Draft of [spec/doc] was published today by the @@Working Group ... [Learn more|Read] about [wai ig email] and the Web Accessibility Initiative (WAI).
notes:
- @@ link to previous W3C News
notes:
- @@ link to previous wai highlight in http://www.w3.org/WAI/highlights/archive
Tweet (MAXIMUM 140 characters)
...
(000)
notes & brainstorms:
- @@ link to previous tweet from https://twitter.com/w3c_wai (to get link to a specific tweet: click on Expand, then Details)
W3C Q&A blog post:
[not doing]
notes:
- ...