See also: IRC log
<Jan> Not meeting Feb 21 due to absence of multiple US, CDN members...
<Jan> So a pre-CSUN TR draft will not be happening
<scribe> scribe: jeanne
Jutta: Discuss with your company
commenters to make sure that there is agreement with how we
have handled the comments. Also any other issues from within
the group need to be handled, so that we do not rehash issues
that we have already worked through - especially with people
internal to the group.
... so any comments that come forward at this stage should be significant and not issues we have already addressed.
Tim: Is there a process to get feelers to see if there are any other issues?
Jutta: This next draft is a way to ask people to see if there are any issues left before we go into Last Call.
<Jan> JT: We will revisit
<Jan> Resolution: All accept
<Jan> Note on Accessibility Checker: While accessibility checking functionality is an important part of an ATAG 2.0 conforming authoring tool, a stand-alone accessibility checker with no automated or semi-automated repair functionality is not considered an authoring tool because it is not used to edit web content for use by other people.
Jutta: While we are not going to be considering an accessibility checker with no repair or edit functions, when a checker is including in the authoring tool or when it is bundled with an authoring tool, it will be included
<Jan> JR: Agree to GP's request for a note that checkers can be considered part of tool
Jutta: Creating, modifying content is what we want.
Alex: We are excluding specific
categories, like Simple Text Editor, and Checkers that don't
have repair, but we aren't giving the criteria for something
being included/excluded which isn't sound.
... We need to have specific if/then statements in the criteria
Jan: We have it in most success criteria.
Alex: Any given product can go through ATAG and go through the if/then statements in a yes/no. So a specialized tool like a checker will only say yes to the ones that apply. Then conformance doesn't have to deal with collections.
Jan: A lot of tools don't haave built-in checkers, so we wanted to encourage bundling with a checker
Jutta: We need to make it clear that if the Success Criteria doesn't apply, then we don't have to restrict our definition of authoring tool.
<Jan> ACTION: JR to To write a note about what "not applicable" means and how to use it [recorded in http://www.w3.org/2011/02/14-au-minutes.html#action01]
<trackbot> Created ACTION-322 - Write a note about what "not applicable" means and how to use it [on Jan Richards - due 2011-02-21].
Jan: If it applies or not, then evaluate whether you met it. The conformance section section then says that you meet all the success criteria that apply to your tool.
<Jan> Resolution: all accept
<Jan> ACTION: JR to Provide more explanation around why unaware people to be excluded as authors [recorded in http://www.w3.org/2011/02/14-au-minutes.html#action02]
<trackbot> Created ACTION-323 - Provide more explanation around why unaware people to be excluded as authors [on Jan Richards - due 2011-02-21].
rssagent, make logs public
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: jeanne Inferring ScribeNick: jeanne Default Present: Jeanne, Jan, Alexandro, Cherie, Alex, Sueann, Jutta, Greg, Tim_Boland Present: Jeanne Jan Alexandro Cherie Alex Sueann Jutta Greg Tim_Boland Regrets: Andrew_R. Greg_P. Alastair_C. Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2011JanMar/0045.html Got date from IRC log name: 14 Feb 2011 Guessing minutes URL: http://www.w3.org/2011/02/14-au-minutes.html People with action items: jr[End of scribe.perl diagnostic output]