W3C logo Web Accessibility Initiative (WAI) logo

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]

Draft blurbs

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:

 

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:

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:

W3C Q&A blog post:

not doing

 

Archive Draft Blurbs

to cut down on page & file size, archived notes were moved to:

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:

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:

 

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:

 

notes:

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:

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 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.

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:

  • ...

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)

 

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

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

 

template@@ SLH only - others use draft announcements page (limited access)

W3C Home Page (and Newsletters):

@@title

The @@Working Group today published... ...[Learn more|Read] about [wai ig email] and the Web Accessibility Initiative (WAI).

notes:

title brainstorms:

body brainstorms:

WAI Highlight for home page & RSS feed:

@@title

woohoo we published. See:

  • ...,
  • ....

Please send comments by @@ Month 2011.    (2011-@@-@@)

notes:

title brainstorms:

body brainstorms:

WAI IG email:

Call for Review: @@

Dear WAI Interest Group Participants,

The W3C WAI @@ Working Group (@@WG) invites you to comment on...

Please let us know if you have any questions. Thank you in advance for your comments.

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

Regards,
~Shawn Lawton Henry
On behalf of:
@@

notes:

Tweet (MAXIMUM 140 characters)

...

(@@)

notes & brainstorms:

W3C Q&A blog post:

not doing

notes:

title brainstorms:

body brainstorms: