See also: IRC log
<jeanne> jim, did you do the meeting set up already?
<jeanne> ...for scribing
<AllanJ> just invited zakim and rrsagent, no titles, agenda etc
<jeanne> Ok, will do. I just joined so I didn't see what was done.
<jeanne> rssagent, set logs public
<scribe> Scribe: Jan
JA: No commenting yet on succes
... Then some work on "passive reflow"
DH: Defintion of flow looks fine
<scribe> ACTION: JS Add "Flow" to glossary [recorded in http://www.w3.org/2008/05/29-ua-minutes.html#action01]
JA: OK on to the printing success criteria
<scribe> ACTION: JR to Edit http://lists.w3.org/Archives/Public/w3c-wai-ua/2008AprJun/0072.html to remove "horizontal" [recorded in http://www.w3.org/2008/05/29-ua-minutes.html#action02]
JS: Key thing is to say "appropriate with the language"
JA: I think if you review it...most of the text is in the flow defintion so this can be simplified
<jeanne> "Print Scale: If a print from viewport feature is provided,
<jeanne> the user has the option of printing using the viewport's scale settings
<jeanne> such that the user agent should attempt to *passively reflow* the
<jeanne> content into the horizontal dimensions of paper. If passive reflow is
<jeanne> not possible, more than one sheet of paper will be required horizontally.
JA: Then were we say the reflow is not possible, the same
DH: ok...but looks like I need to
get on irc
... OK with basic requirement
<jeanne> JS: Ok
JA: Brought up by Kelly...
... Looked at WCAG2...
... In UAAG1 my rememberance is just that it was thrashed out in group...if something would "really" cause problems it was an A
... Barrier to some is AA
... Nice to do become AAA
JR: Explains the WAI 1.0 vs 2.0 levels
So Level A...no work around for user
DH: What do you mean by "barrier" at level AA
JA: Level AA is nuanced thing...if don't do it...things are difficult but not stonewalled
JR: Points out that "reasonably be achieved" usually comes into it
JA: We should try to harmonize with WCAG
JR: ATAG not fully worked out
... I suggest UAAG harmonizes with WCAG
... Reads from http://www.w3.org/TR/2008/WD-UNDERSTANDING-WCAG20-20080430/conformance.html
"Understanding Levels of Conformance"
DH: Any one concerned about
testable by machine or human
... Concerned about machine testing
<AllanJ> JR: explains machine testing,
JR: Thinks that UA context would mainly be human testing
JA: WCAG thinking about
accessible content testing
... Don't think we could do this in UA
<AllanJ> JR: talking about accessibility of web application
<AllanJ> ... tools can inspect the web application
<AllanJ> ... UAAG has requirement to provide a "list of link"
<AllanJ> ... not sure a machine can do this, but a human can determine if list is available
JR: Would think a couple people for ac ouple weeks could test a browser
oops that was JR
JA: So WCAG fully baked?...
... Don't know if we will creat an "Understanding UAAG"...
... Maybe for our own internal use we can use the 13 page version...
... We should inform our discussion of levels from WCAG's 13 page version...but when we actually write UAAG2's conf section we'll try to be shorter
JA: We have the"Keyboard access"
... But think that needs more work;...
... Then we have the UA and video peice
DH: WHat meant by video?
JA: Right now video treated as
plugin...we talk about passing control...etc.
... In HTML5 video will become more native...so more issues come up: captions, text track
... Our placeholder text needs to be cleaned up
... I was thinking the browser should provide a standard widget set around video
DH: Yeah...if its native it
shouldn't be on screen readers to handle the scripting
... Prob a pretty hot topic
<AllanJ> JR: ALT issue, give background.
<AllanJ> ... a request for feedback to XTECH and HTML5 from UAWG
JA: So from user agent...we're
going to reveal to user agent what's important...
... Up to HTML5 to decide how to store what's important...
<AllanJ> JR: doesn't want ambiguity in the HTML5 spec.
JA: And in HTML5 there is a cascading layer thing....legends...containing imgs etc.
<AllanJ> JR: don't think a big deal. @alt to be alternate representation of the image, e.g. image of iceberg, @alt - iceberg floating in ocean, <legend> if it uses the same language
<AllanJ> ... then only reveal one, if they are different then reveal both
JA: This is a screen reder repair issue...alt="" is decorative, no alt triggers repair
<scribe> ACTION: JA will go through UAAG2 and look at places concerned with revealing alternates [recorded in http://www.w3.org/2008/05/29-ua-minutes.html#action03]
DH: Maybe I will try and get James Craig involved.
JA: Great...there's process things to do.
This is scribe.perl Revision: 1.133 of Date: 2008/01/18 18:48:51 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/DH: Would/JR: Would/ Found Scribe: Jan Inferring ScribeNick: Jan Default Present: jeanne, AllanJ, Jan, Dean Present: jeanne AllanJ Jan Dean Regrets: Kelly_Ford Alan_Cantor Agenda: http://lists.w3.org/Archives/Public/w3c-wai-ua/2008AprJun/0120.html Got date from IRC log name: 29 May 2008 Guessing minutes URL: http://www.w3.org/2008/05/29-ua-minutes.html People with action items: add flow ja jr js WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]