W3C

- DRAFT -

UAWG conference call

14 Dec 2006

Agenda

See also: IRC log

Attendees

Present
Jim_Allan, JR, parente, cklaws
Regrets
Chair
Jim Allan
Scribe
JR

Contents


 

 

<jallan> Scribe: JR

JA: Registration for tech plenary is open

<jallan> http://www.w3.org/2007/01/MGMoverview.html

<scribe> Scribe: JR

JA: WCAG not coming...

CL: But Becky coming to UAWG group

JA: Tuesday joint time with PF

CL: Do we have an issues doc?

JA: Yes 1/3 done

CL: Very helpful to send to becky

JA: Talke to John Slatin about keypress issue and he recommended talking to Becky

CL: Aaron hopefully will hae some time too in Boston

<jallan> http://www.w3.org/2007/01/MGMoverview.html plenary information

12.1 Provide accessible documentation (P1)

<jallan> update for WCAG 2.0 whne available

JR: - Maybe we should say Double-A of WCAG 1.0 or WCAG 2.0?

- What about promoting the accessibility of installation codes and

documentation to be a requirement.

CL: Packaging issue

<jallan> software key for licensed installation

CL: Code is unique per CD

JA: This is a high bar...should stay a technique

CL: Generally UA's are downloads with no codes.

PP: Online activation for JAWS

JR: main thought is that all steps in installation should be accessible

<jallan> ACTION: JA to write technique to allow online registration for licensed products [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action01]

12.2 Provide documentation of accessibility features (P1)

JA: This is P1 but requires P2?

JR: Couldn't we solve this by saying "if the functionality exits"
... (investigates ATAG2 approach)

JA: Prob non-issue

<jallan> ACTION: JA Couldn't we solve this by saying "if the functionality exits" [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action02]

12.3 Provide documentation of default bindings

CL: Suff technique states the obvious

JA: Strange wording here too

<scribe> ACTION: JA to Remove suuff technique from 12.3 [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action03]

12.4 Provide documentation of changes between versions (P2)

JA, JR: OK with it

Topi: 12.5 Provide dedicated accessibility section (P2)

12.5 Provide dedicated accessibility section (P2)

JR: Concerned about dedicated area

CL: Can get around it if central help area pointed to integrated areas.

PP: Can get around it if integrated areas point to central accessibility area.

JA: Wondered about normative inclusions...

CL: They seem to be pointing to 8.1 via 12.2, it should be changed to point directly

JR: This wording also misses UA features should as list of links.

<jallan> ACTION: JA need to expand here include content info from 8.1 and techniques of 12.2 [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action04]

CL: use wording "All User Agent features that benefit accessibility"

JR: (Missed noting myself)

CL: So what needs to documented regarding access keys.

<jallan> CL: how a UA handles accesskey should be documented, bring up a list, how to activate

CL: handling access key...
... There is "developer" help that talks abouting handling of all elements
... "user help" includes all keys to press for features etc

JA: User still needs to know that the user does something with alt text etc
... "Yes you can get list of headings by pressing shift-/ etc."

JR: Much clarification in wording

CL: #2 needs more around conformance detail

JA: Just there for clarity

CL: Really conformance scope

JR: In ATAG we have a term: "accessible content support features "
... That then references the checkpoints covered

CL: Just a few more words to clarify under normative
... To clarify that we are talking about user agent features

<jallan> ACTION: JA 12.5 needs clarification in wording in normative inclusion 1, specifing user agent features rather than content. [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action05]

JA: OK because of schedules...
... NExt UAAG meeting on Jan 11!
... Will come back with issue list - and we will be doing F2F planning

Summary of Action Items

[NEW] ACTION: JA Couldn't we solve this by saying "if the functionality exits" [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action02]
[NEW] ACTION: JA 12.5 needs clarification in wording in normative inclusion 1, specifing user agent features rather than content. [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action05]
[NEW] ACTION: JA need to expand here include content info from 8.1 and techniques of 12.2 [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action04]
[NEW] ACTION: JA to Remove suuff technique from 12.3 [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action03]
[NEW] ACTION: JA to write technique to allow online registration for licensed products [recorded in http://www.w3.org/2006/12/14-ua-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.127 (CVS log)
$Date: 2006/12/14 19:51:27 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.127  of Date: 2005/08/16 15:12:03  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: JR
Inferring ScribeNick: JR
Found Scribe: JR
Inferring ScribeNick: JR
Default Present: Jim_Allan, JR, parente, cklaws
Present: Jim_Allan JR parente cklaws
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0043.html
Got date from IRC log name: 14 Dec 2006
Guessing minutes URL: http://www.w3.org/2006/12/14-ua-minutes.html
People with action items: ja need

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


[End of scribe.perl diagnostic output]