W3C

- DRAFT -

WAI AU

20 Jul 2009

Agenda

See also: IRC log

Attendees

Present
Jeanne, Jan, Tim_Boland, Jutta, Greg_Pisocky, ARonksley, +200000aaaa
Regrets
Ann, M.
Chair
Jutta Treviranus
Scribe
Greg

Contents


 

 

<Jan> Chair: Jutta Treviranus

Greg can scribe

<Jan> Scribe: Greg

<Jan> http://lists.w3.org/Archives/Public/w3c-wai-au/2009JulSep/0010.html

Real-time publishing Note

<Jan> New editors draft: http://www.w3.org/WAI/AU/2009/ED-ATAG20-20090717/

First item on agenda, take a look at Real Time publishing Note on the new editors draft

<Jan> Real-time publishing: ATAG 2.0 applies to authoring tools with workflows that involve real-time publishing of web content (e.g., some collaborative tools). For these authoring tools, conformance to Part B of ATAG 2.0 may involve some combination of real-time accessibility supports and additional accessibility supports available after the real-time authoring session (e.g., the ability to add...

<Jan> ...captions for audio that was initially published in real-time). For more information, see the Techniques - Appendix E: Real-time content production.

JR: Used to say real time authoring tools did not have to look at B, just A. This was considered a loophole, so here is the reworked content.

JS: Any problem addressing real time issues in Part A?

JR: Then agreed, the issue is Part B

JS above should be JR

<Jan> Resolution: To use wording: Real-time publishing: ATAG 2.0 applies to authoring tools with workflows that involve real-time publishing of web content (e.g., some collaborative tools). For these authoring tools, conformance to Part B of ATAG 2.0 may involve some combination of real-time accessibility supports and additional accessibility supports available after the real-time authoring...

<Jan> ...session (e.g., the ability to add captions for audio that was initially published in real-time). For more information, see the Techniques - Appendix E: Real-time content production.

Conformance Claim section

<Jan> JR: Required Components of an ATAG 2.0 Conformance Claim...

<Jan> All: Claimant name and affiliation.: No objections.

<Jan> All: Conformance level satisfied.: No objections.

<Jan> All: Authoring tool information:: No objections.

<Jan> All: Included Technologies: No objections.

<Jan> All: Excluded Technologies: No objections.

<Jan> All: Declarations: No objections.

That completes the conformance section

B.2.1.X proposal

Proposal on Decision Support by JT

Add another success criteria to B.2.1.x

<Jan> http://www.w3.org/WAI/AU/2009/ED-ATAG20-20090717/#principle-support-author

JT: Any objections to adding as a success criteria?

<Jan> Techs: http://www.w3.org/WAI/AU/2009/ED-ATAG20-TECHS-20090717/#principle-support-author

<Jan> GP: How to determine what is the most accessible way

<Jan> JT: Doesn't need to be "most accessible way"..just accessible vs not accessible

<Jan> GP: OK as long as techniques are not ranked over each other

<Jan> JT: Guidance can take various forms but its about ensuring authors can make informed choices

<Jan> JR: Objectins?

<Jan> Resolution: Add in new success criteria B.2.1.X Decision Support.

<Jan> GP: Back on previous question...

<Jan> GP: Would it be sufficient to have a mode where an author could turn off "onerous"

<Jan> JR: Doesn't need to be oneours...not a requirement to force author behaviour

<Jan> GP: But user might not want prompts etc

<Jan> JT: Right it might just be extra text

<Jan> GP: User jusdt wants to drop in images...because know where they go....

<Jan> GP: I see prompt...dialog...etc. in the examples in the techniques

<Jan> JT: OK we need to modify that text to include less obtrusive choices]

<Jan> JR: Could we just keep it yellow until we get the tech examples woked out?>

<Jan> GP: OK

<Jan> JT: Example from iPhone dev kit....

<Jan> JR: Can you send a screenshot?

<Jan> JT: Yes

<Jan> ACTION: JT to Screenshot of iphone dev enviro showing inobtrusive info [recorded in http://www.w3.org/2009/07/20-au-minutes.html#action01]

<trackbot> Created ACTION-174 - Screenshot of iphone dev enviro showing inobtrusive info [on Jutta Treviranus - due 2009-07-27].

<Jan> GP: I like the idea...but don't want to require authors to use it at a partilar time in every case

<Jan> JT: Of course not

<Jan> JR: Please look at new approach in the techniques document

Summary of Action Items

[NEW] ACTION: JT to Screenshot of iphone dev enviro showing inobtrusive info [recorded in http://www.w3.org/2009/07/20-au-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009/07/20 20:47:08 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Greg
Inferring ScribeNick: Greg
Default Present: Jeanne, Jan, Tim_Boland, Jutta, Greg_Pisocky, ARonksley, +200000aaaa
Present: Jeanne Jan Tim_Boland Jutta Greg_Pisocky ARonksley +200000aaaa
Regrets: Ann M.
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2009JulSep/0010.html
Got date from IRC log name: 20 Jul 2009
Guessing minutes URL: http://www.w3.org/2009/07/20-au-minutes.html
People with action items: jt

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]