partial regrets... put Breadcrumbs off til 5pm

Partial regrets.

I have to meet a client at 3:30 and will rush back as soon a I'm done. I
expect to be back on the second half of the call. Can the issue about
breadcrumbs wait to the last 30 minutes of the meeting.

David MacDonald

access empowers people...
        ...barriers disable them...
 
www.eramp.com 



-----Original Message-----
From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Loretta Guarino Reid
Sent: Friday, April 03, 2009 3:53 PM
To: WCAG
Subject: Reminder: review WAI-ARIA documents by April 9

Please review the WAI-ARIA documents before our meeting next Thursday.


---------- Forwarded message ----------
From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Thu, Mar 26, 2009 at 2:41 PM
Subject: Reminder: review WAI-ARIA documents by April 9
To: WCAG <w3c-wai-gl@w3.org>


Please review the WAI-ARIA last call documents before our next
teleconference, on April 9. We will discuss what comments, if any, to
submit to PF.

Thanks, Loretta


---------- Forwarded message ----------
From: Shawn Henry <shawn@w3.org>
Date: Thu, Mar 5, 2009 at 8:27 PM
Subject: [updated deadline] Call for Review: WAI-ARIA Last Call and
New Document  for Browsers
To: WAI Interest Group <w3c-wai-ig@w3.org>


Dear WAI Interest Group Participants,

[The deadline for comments is corrected to 17 April 2009.]

The Protocols and Formats Working Group invites you to review the
following documents published 24 February 2009:
* Accessible Rich Internet Applications (WAI-ARIA) 1.0 - Last Call Working
Draft
 http://www.w3.org/TR/wai-aria/
* WAI-ARIA User Agent Implementation Guide - First Public Working Draft
 http://www.w3.org/TR/wai-aria-implementation/
* WAI-ARIA Best Practices - updated Working Draft
 http://www.w3.org/TR/wai-aria-practices/

WAI-ARIA defines a way to make Web content and Web applications more
accessible to people with disabilities. It especially helps with
dynamic content and advanced user interface controls developed with
Ajax (also known as AJAX), HTML, JavaScript, and related technologies.

The WAI-ARIA User Agent Implementation Guide provides guidance on how
browsers and other user agents should expose WAI-ARIA features to
platform accessibility APIs.

WAI-ARIA Best Practices describes how Web content developers can
develop accessible rich internet applications using WAI-ARIA.

For an introduction to WAI-ARIA and links to related documents, please see:
* WAI-ARIA Overview
 http://www.w3.org/WAI/intro/aria
* WAI-ARIA FAQ
 http://www.w3.org/WAI/aria/faq

*Last Call Status*:
The main WAI-ARIA technical specification is provided as a Last Call
Working Draft for public review of the document now that it has all
resolutions from previous comments incorporated. The Working Group
hopes that it has resolved all substantive issues with this draft, and
looks forward to progressing to the next stages in completing
WAI-ARIA. The next stages are described in:
* How WAI Develops Accessibility Guidelines through the W3C Process
 http://www.w3.org/WAI/intro/w3c-process

Please send any comments
* by 17 April 2009 to
 public-pfwg-comments@w3.org

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

Thank you in advance for your comments.

Regards,
Shawn Henry and Judy Brewer, W3C WAI
On behalf of:
Janina Sajka, Chair of PFWG
Michael Cooper, W3C WAI Staff Contact for PFWG


-----
Shawn Lawton Henry
W3C Web Accessibility Initiative (WAI)
e-mail: shawn@w3.org
phone: +1.617.395.7664
about: http://www.w3.org/People/Shawn/

Received on Thursday, 16 April 2009 18:03:21 UTC