W3C home > Mailing lists > Public > w3c-wai-au@w3.org > January to March 2013

Minutes from AUWG Teleconference on 7 January 2013 3:00pm-4:00pm ET

From: Richards, Jan <jrichards@ocadu.ca>
Date: Mon, 7 Jan 2013 21:35:46 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <0B1EB1C972BCB740B522ACBCD5F48DEB03B9D63C@ocadmail-maildb.ocad.ca>
http://www.w3.org/2013/01/07-au-minutes.html

Full text:
WAI AU

07 Jan 2013

Agenda

See also: IRC log

Attendees

Present
[IPcaller], Jeanne, +1.571.765.aaaa, Greg, Jutta, +1.202.368.aabb, Tim
Regrets
Tim_B., Cherie_E., Sueann_N., Alex_L.
Chair
Jutta Treviranus
Scribe
Jan
Contents

Topics
1. Review of answers to the surveys re: tests
Summary of Action Items
<scribe> Scribe: Jan
1. Review of answers to the surveys re: tests

https://www.w3.org/2002/09/wbs/35520/20130107/results
JR: If we decide on any reasonable ideas lets puut them in an email.
JT: OK lets get started
A.2.1.1 Text Alternatives for Rendered Non-Text Content: If an editing-view renders non-text content, then any programmatically associated text alternatives for the non-text content can be programmatically determined. (Level A)
GP: Remeber this is an authoring tool for multimedia, either audio or video and as such, the alternatives may not be available because this is raw content. Needs some kind of qualifier that doesn't automatically assume that an alternative is already in existance. Your not going to have a closed caption transcript for video ready until the video has been edited. No one is going to bother...
... producing alternatives for content that ends up on the cutting room floor. Chicken, meet egg. Egg say hello to chicken.
JR: Agree maybe we can scope it at the top of each test
... New note at the top of the test - if the media alternatives for the format are in a different (non-included) format then the requirem,ent is not applicable and select, SKIP.
A.2.1.2 Alternatives for Rendered Time-Based Media
https://www.w3.org/2002/09/wbs/35520/20130107-2/results
A.3.1.5 Customize Keyboard Access: If the authoring tool includes keyboard commands, then those keyboard commands can be customized. (Level AAA)
https://www.w3.org/2002/09/wbs/35520/20130107-2/results#xq7
JR: Check whether the authoring tool has any mechanism by which any of the keyboard commands can be customized (e.g.. ???)
... And remove the fail loop
JT: OK
JS: OK
<scribe> ACTION: Jan to To write an email to the list with changes to tests agreed today [recorded in http://www.w3.org/2013/01/07-au-minutes.html#action01]
<trackbot> Created ACTION-383 - Write an email to the list with changes to tests agreed today [on Jan Richards - due 2013-01-14].
A.3.4.2 Navigate by Programmatic Relationships: If editing-views allow editing of programmatic relationships within web content, then mechanisms are provided that support navigation between the related content. (Level AAA) Note: Depending on the web content technology and the nature of the authoring tool, relationships may include, but are not limited to, element nesting, headings, labeling,...
scribe: programmatic definitions, and ID relationships.
GP: Not quite sure what this is saying. The way this is written "navigate between pieces of web content (elements, functions, etc.) where there is a programmatic relationship" implies you can navigate the code. Isn't the point to exploit the relationships and "flip flop" between elements where there is an established relationship?
JR: Agrees that 2 should be tightened up.
JT: Agree that JR will put in suggested fail conditions where they were missing.
A.3.6.1 Independence of Display: If the authoring tool includes display settings for editing-views, then the authoring tool allows authors to adjust these settings without modifying the web content being edited. (Level A)
GP: 4.2 isn't that the point the author makes a change, then the end use experience should change. I gather the point here is to separate authoring view from rendered view. The assertion might be clearer if written "Authors can adjust display settings of editing views without affecting the display of the final content."
JR: OK with "Authors can adjust display settings of editing views without affecting the display of the final content."
JT: OK
https://www.w3.org/2002/09/wbs/35520/20130107-4/results
B.1.2.3 Optimizations Preserve Accessibility: If the authoring tool provides optimizing web content transformations, then any accessibility information (WCAG) in the input is preserved in the output. (Level A).
GP: Some accessibility information need not be preserved in the optimization because it doesn't apply to the optimization - the example cited for example - unless it's a preview of the "pretty print" but why would you necessarily preserve alt text for content meant exclusively for hard copy?
... Will withdraw comment
B.1.2.4 Text Alternatives for Non-Text Content are Preserved: If the authoring tool provides web content transformations that preserve non-text content in the output, then any text alternatives for that non-text content are also preserved, if equivalent mechanisms exist in the web content technology of the output. (Level A). Note: This success criterion only applies when the output technology is "
included" for conformance.
GP: Will withdraw comment
https://www.w3.org/2002/09/wbs/35520/20130107-3/results
B.4.2.1 Model Practice (WCAG): A range of examples in the documentation (e.g., markup, screen shots of WYSIWYG editing-views) demonstrate accessible authoring practices (WCAG). (Level A to meet WCAG 2.0 Level A success criteria; Level AA to meet WCAG 2.0 Level A and AA success criteria; Level AAA to meet all WCAG 2.0 success criteria)
documentation
Any information that supports the use of an authoring tool. This information may be provided electronically or otherwise and includes help, manuals, installation instructions, sample work flows, tutorials, etc.
GP: OK with B.2.4.1
... OK with B.2.4.2
B.4.2.3 Tutorial: The authoring tool provides a tutorial for an accessible authoring process that is specific to that authoring tool. (Level AAA)
JR: Can add an eg to support website
B.4.2.4 Instruction Index: The authoring tool documentation contains an index to the instructions for using any accessible content support features. (Level AAA)
JR: will add that as an eg
Summary of Action Items

[NEW] ACTION: Jan to To write an email to the list with changes to tests agreed today [recorded in http://www.w3.org/2013/01/07-au-minutes.html#action01]

(MR) JAN RICHARDS
PROJECT MANAGER
INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
OCAD UNIVERSITY

T 416 977 6000 x3957
F 416 977 9844
E jrichards@ocadu.ca


> -----Original Message-----
> From: Richards, Jan
> Sent: January-06-13 3:11 PM
> To: w3c-wai-au@w3.org
> Subject: AUWG Teleconference on 7 January 2013 3:00pm-4:00pm ET
> 
> There will be an AUWG teleconference on Monday 7 January 2013 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.
> 
> Most Recent Editors Drafts
> =====================
> ATAG 2.0
> http://www.w3.org/WAI/AU/2012/ED-ATAG20-20120924/
> Implementing ATAG 2.0
> http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20121011/
> 
> Agenda
> ======
> 1. Review of answers to the surveys re: tests:
> 
> Part 1 (A.1 - A.2)
> https://www.w3.org/2002/09/wbs/35520/20130107/
> 
> Part 2 (A.3)
> https://www.w3.org/2002/09/wbs/35520/20130107-2/
> 
> Part 3 (A.4 - B.2)
> https://www.w3.org/2002/09/wbs/35520/20130107-4/ (note: URL number is
> off, but the title is correct)
> 
> Part 4 (B.3 - B.4)
> https://www.w3.org/2002/09/wbs/35520/20130107-3/
> 
> 
> 
> 
> 
> Cheers,
> Jan
> 
> 
> 
> 
> (MR) JAN RICHARDS
> PROJECT MANAGER
> INCLUSIVE DESIGN RESEARCH CENTRE (IDRC)
> OCAD UNIVERSITY
> 
> T 416 977 6000 x3957
> F 416 977 9844
> E jrichards@ocadu.ca
Received on Monday, 7 January 2013 21:36:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 January 2013 21:36:10 GMT