W3C home > Mailing lists > Public > w3c-wai-au@w3.org > July to September 2012

RE: AUWG Teleconference on 23 July 2012 3:00pm-4:00pm ET

From: Richards, Jan <jrichards@ocadu.ca>
Date: Fri, 20 Jul 2012 20:28:20 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <0B1EB1C972BCB740B522ACBCD5F48DEB03AC1C8C@ocadmail-maildb.ocad.ca>
Oops, I didn't include the relevant link for item 1:
http://www.w3.org/WAI/AU/2012/ATAG20tests/ATAG2-10April2012PublicWD-Tests-rev20120711

(Mr) Jan Richards, M.Sc.
jrichards@ocadu.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844 
Inclusive Design Research Centre (IDRC) | http://idrc.ocad.ca/ 
Faculty of Design | OCAD University

> -----Original Message-----
> From: Richards, Jan [mailto:jrichards@ocadu.ca]
> Sent: July-20-12 4:22 PM
> To: w3c-wai-au@w3.org
> Subject: AUWG Teleconference on 23 July 2012 3:00pm-4:00pm ET
> 
> There will be an AUWG teleconference on Monday 23 July 2012 at 3:00 pm-
> 4:00 pm ET:
> Call: (617) 761-6200 ext. 2894#
> Zakim: +1.617.761.6200       (Boston)
> IRC: server: irc.w3.org, port: 6665, channel: #au
> 
> If people think they will arrive more than 15 minutes late, please send me an
> email beforehand.
> 
> Last Call Drafts
> ===========
> http://www.w3.org/TR/ATAG20/
> http://www.w3.org/TR/IMPLEMENTING-ATAG20/
> 
> Agenda
> ======
> 
> 1. AUWG test development to prepare for entering CR:
> - As discussed last week, everyone (besides the few that spoke up about
> conflicts) were going to try to write at least one test.
> 
> 2. SC's that we might flag as a result of test writing. So far:
> - B.4.1.3 Feature Availability Information: If the authoring tool supports
> production of any web content technologies for publishing for which the
> authoring tool does not provide support for the production of accessible web
> content (WCAG), then this is documented. (Level AA)
> - Note: This success criterion concerns the presence or absence of support
> features, such as accessibility checkers, not any intrinsic property of web
> content technologies.
> @ISSUE: This is tricky because the SC just says "support for production", not
> that the production of the other format needs to meet ATAG 2.0. This makes
> some sense because if it did imply ATAG 2.0 conformance then to do an
> ATAG 2.0 conformance check on any format for a tool would actually require
> doing one on all of them. But, what, then, does "support" mean? One (weak)
> possibility is [the test I wrote]... that accessible content be possible. Another
> (stronger) possibility is that a "supported" format has to have checking (even
> if it is manual checking). If that's what we mean...I think we should fix the SC
> to say that.
> (http://lists.w3.org/Archives/Public/w3c-wai-au/2012JulSep/0013.html)
> 
> 3. Selecting new tests to write (each member will choose at least one SC to
> write tests for the next week)
> 
> 
> 
> Cheers,
> Jan
> 
> (MR) JAN RICHARDS
> PROJECT MANAGER
> INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
> 
> T 416 977 6000 x3957
> F 416 977 9844
> E jrichards@ocadu.ca
> 
> Twitter @OCAD
> Facebook www.facebook.com/OCADUniversity
> 
> OCAD UNIVERSITY
> 205 Richmond Street West, 2nd Floor, Toronto, Canada  M5V 1V3
> www.ocadu.ca idrc.ocadu.ca
Received on Friday, 20 July 2012 20:28:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 20 July 2012 20:28:43 GMT