See also: IRC log
<scribe> Scribe: JR
JA: Nothing to report on emails to new members
JR: Did a first pass: http://lists.w3.org/Archives/Public/w3c-wai-ua/2007AprJun/0017.html
JA: Al's conversation...
<AllanJ> discussion of 'perceivable'. AG thinks should use 'recognizable'
<AllanJ> http://lists.w3.org/Archives/Public/w3c-wai-ua/2007AprJun/0024.html
<AllanJ> cl: is WCAG changing?
<AllanJ> jr: not that we are aware of.
<AllanJ> JR: we should not just parrot WCAG, and look at things with a fresh eye.
<AllanJ> JR: any other issuers with operable, perceivable, understandable, AT friendly?
CL: Who decides on styles
<AllanJ> jr: what is worst case scenario...website with 1 pixel divs, content drawing content on screen, UA has no control of accessibility of content
<AllanJ> jr: UA has limited resources, especially with AJAX type controls
<AllanJ> cl: UA have different rendering engines
CL: The different renderings on different UAs is proof of a UA role
JR: Is Pereceivale UI understood to mean all of the UA
KF: Maybe not
PP: We canhave our own defns
KF<CL: Yes but should keep consistency
<AllanJ> JR: WCAG dictionary is used by ATAG, but on occasion have differences
JR: atag doesn't use wcag dictionmary...
but try to keep coordinated defns
KF: Recommend bringing this up at coord meeting
JA, JR: OK
<scribe> ACTION: JA to Send email to CG list about coordinating "perceivable" etc. [recorded in http://www.w3.org/2007/05/10-ua-minutes.html#action01]
JA: Thinks its something we need
to review.
... Al also refers back to essential components doc - which is
also good to review
... Similar to to JTC work - where we want to make sure user
needs are addressed in uaag
Needs Summary (UNS)"
JA: Anyone have a chance to look at this?
All: nope.
JA: Pretty big chunk of
information
... 16 diff categories
... Maybe each of us take 3 categories...for next time
CL: 1-3
JR: 4-6
JA: 7-9
KF: 10-12
PP: 13-15
JR: 16
JA: Review - are these properly done + are we missing anything (we should have a checkpoint for)
<scribe> ACTION: All to Group members to review assigned sections of the User Needs Mapping document [recorded in http://www.w3.org/2007/05/10-ua-minutes.html#action02]
<AllanJ> ALL: discussion of JTC
<AllanJ> http://www.jtc1access.org/documents/swga_212.zip
JA: The new version has a cover
letter...
... Purpose is to help out the JTC to make sure the mapping is
ok, but it also helps us to review the needs to see if we are
missing anything.
... Since jR already did prelim mapping we should all review
that
JA: But concerned about
overloading...
... Let's split...do the JTC mapping for May 17 and then for
May 24, look at JR's mapping...
<AllanJ> JR: JTC is a gap analysis
JR: I can do a better chart
CL: Ok to leave way it is but add titles
JA: New Adobe user agent...
... Apparently its pretty interesting...does anyone know about
it?
CL: Think they are implementing IA2 on it
JA: sounds like its a browser replacment
CL: They say it allows flash to jump beyond the browser
<cklaws> http://news.com.com/Flash+to+jump+beyond+the+browser/2100-1007_3-6071005.html
KF: Do a web search there's lots out there
<KFord> I believe this is a good URL http://labs.adobe.com/wiki/index.php/Apollo
This is scribe.perl Revision: 1.128 of Date: 2007/02/23 21:38:13 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 Default Present: JR, KFord, Allanj, parente, cklaws Present: JR KFord Allanj parente cklaws WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 10 May 2007 Guessing minutes URL: http://www.w3.org/2007/05/10-ua-minutes.html People with action items: all ja WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]