See also: IRC log
<Jan> Scribe: ARonksley
JT: first item on agenda is
review of comments on last call
... does anyone know of people to chase for comments?
GP: Andrew Kirkpatrick from Adobe is currently reviewing
JT: Need to make sure comments are representative of the community / organisations etc
<Jan> AR: Will try and chase someone at RNIB
AR: Sally Cain from RNIB - i'll
chase tomorrow.
... Will also email Joshue O'Connor who has done a lot of work
around Joomla / Drupal
JT: Can everyone send in a list
of 10 people to review the editors draft for the push
list
... Moving onto Cynthia's comments
http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0058.html
Guideline A.3.6 [For the authoring tool user interface] Manage preference settings
Should there be an SC for honoring operating system settings for keyboard and display?
Alternatively, perhaps both honoring OS settings, and saving keyboard and display settings, are general software issues, and not specific to authoring tools?
JR: Do people think it's such a
general software issue we should remove it? If it stays, what
do people think of my proposal?
... Any tools that leave preferences / keyboard settings etc to
the OS are exempt
JT: When we first created this,
we went beyond what the OS would provide. It's subsequently
been whittled down to a similar level to what the OS will
provide.
... E.g. individual preference settings per user.
TB: My concern is that a tool won't allow a level of customisation if we fall back to relying on OS provisions.
JR: An example is the customisation of a WYSIWYG tool.
<Jan> ACTION: JR to Take A.3.6 back to drawing board - add points about when to pass OS and when perhaps not [recorded in http://www.w3.org/2010/01/04-au-minutes.html#action01]
<trackbot> Created ACTION-220 - Take A.3.6 back to drawing board - add points about when to pass OS and when perhaps not [on Jan Richards - due 2010-01-11].
<Jan> JT: Not override OS< but rather when more settings are necessary
JR: Suggest adding "third party" to user agent to clarify it doesn't have to be built into the tool
<Jan> Resolution: Use JR's rewording for A.3.7.2 Preview in http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0058.html
<Jan> Resolution: Use JR's rewording for A.4.1.3 Preview in http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0058.html
<Jan> JR: Maybe we should say "Applicability" instead of "responsibility"
<Jan> ACTION: JR to To reword proposal with applicability instead of responsibility [recorded in http://www.w3.org/2010/01/04-au-minutes.html#action02]
<trackbot> Created ACTION-221 - Reword proposal with applicability instead of responsibility [on Jan Richards - due 2010-01-11].
Guideline B.1.1 Support web content technologies that enable the creation of content that is accessible
<Jan> B.1.1.1 Accessible Content Production (WCAG Level A): The author(s) can use the authoring tool to produce web content that conforms to WCAG 2.0 Level A. (Level A)
<Jan> ACTION: JR to Write some intent text for B.1.1.1 to explain that instead of accessibility supported uses we took the decision support approach in B.2.1 [recorded in http://www.w3.org/2010/01/04-au-minutes.html#action03]
<trackbot> Created ACTION-222 - Write some intent text for B.1.1.1 to explain that instead of accessibility supported uses we took the decision support approach in B.2.1 [on Jan Richards - due 2010-01-11].
<Jan> Resolution: Add JRs example to B.1.2.2 in http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0058.html
<Jan> ACTION: JR to Add "Remember" sections in context as proposed text - also reword the "manual" check/repair clarifications to more positively portray automated and semi-autoameted without removing the possibility of the manual option [recorded in http://www.w3.org/2010/01/04-au-minutes.html#action04]
<trackbot> Created ACTION-223 - Add "Remember" sections in context as proposed text - also reword the "manual" check/repair clarifications to more positively portray automated and semi-autoameted without removing the possibility of the manual option [on Jan Richards - due 2010-01-11].
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: ARonksley Inferring ScribeNick: ARonksley WARNING: No "Present: ... " found! Possibly Present: AR ARonksley GP Greg Greg_Pisocky IPcaller JR JT Jan Jeanne Jutta P1 P3 TB Tim Tim_Boland trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2010JanMar/0000.html Got date from IRC log name: 04 Jan 2010 Guessing minutes URL: http://www.w3.org/2010/01/04-au-minutes.html People with action items: jr WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]