<scribe> scribe: JR

<jallan> +[IBM] is Peter Parente

Zakim+ Review revision 2 UAAG - WCAG correlation table

<jallan> http://www.tsbvi.edu/technology/uawg/wcag2e.html

<jallan> JR: reviews message http://lists.w3.org/Archives/Public/w3c-wai-ua/2006AprJun/0045.html

<jallan> and attachement http://lists.w3.org/Archives/Public/w3c-wai-ua/2006AprJun/att-0045/uaag_support_for_WCAG20_levels.htm

JR: Explains email.

JA: Not sure where we need to go with comments...
... Only technical point is a problem with a reqwuirement in WCAG 2 to automatically leaping from form field to form field.
... Thinks we have done useful things in comparing with WCAG...
... but what else can we tell WCAG.
... We only have 2 more meetings before the deadline.

<jallan> jr: could report on our alignment exercise

JR: We comment on our exercise but not make any requests of them.

CL: Brings up fact that WCAG has checkpoints that we don't say anything about.

JA: Well some wcag stuff is totally content-focussed or overly broad.
... e.g. orders of nav bars etc.

CL: Also question about natural lang in 3.1.1 and 3.1.2

<jallan> cl: UAAG explict repect tab order (tab index)

<jallan> ja: do we need to have a function to ignore

<jallan> cl: should uaag require cofigurable tab order

CL: If lang attribute is P1...

<jallan> author has no control of user agent behavior (programatically determined)

JR: Maybe we have a comment on "programmatically determined" as a whole

CL: COuldn't find explicit reference to natural lang respect.

<jallan> cl: 3.1.1 is worded in a confusing manner, author can not ensure progamaticaly determined

<jallan> cl: can supply lang attrib, to enable the user agent to programatically determine the language

CL: Seems like this term is used in a way that shifts burden to ua's..
... when it should be on author (from wcag perspective)

<jallan> cl: programatically determined checkpoints seem more as a UAAG behavior rather than directed at the author

<jallan> the primary language should be provided by the web author so that it can be determined by the user agent

<jallan> cl: not sure we have the requirement solidified in UAAG

ja: so WCAG should just lay out what to do and ua's should catch up
... just noticed they want to separate technologies - but then make lots of implicit user agent requirements
...

<jallan> cl: reword to say "identify the primary natural language according to your basiline technology"

CL: The issue is in the phrasing.

JA: Yes there does seem to be a phrasing difference between other guidelines and these ones

<scribe> ACTION: CL to find problematic instances of "programmatically determined" or other user agent assumptions [recorded in http://www.w3.org/2006/05/11-ua-minutes.html#action01]

<scribe> ACTION: JA to Help CL to do formulate re-phrasing. [recorded in http://www.w3.org/2006/05/11-ua-minutes.html#action02]

JA: Also has a problem with content hacks of user agent functionality (e.g setting font size in the content)

<scribe> ACTION: JA to Identify instances where wcag requires something of the author that really should be done by the user agent. [recorded in http://www.w3.org/2006/05/11-ua-minutes.html#action03]

e.g. separate background audio control

<scribe> ACTION: JR to take a look at the "programmatically determined" construct [recorded in http://www.w3.org/2006/05/11-ua-minutes.html#action04]

JA: starting to think more about uaag 1.1

CL: Agreed

JR: Agreed - prob will be lerss checkpoints, more simplified

CL: e.g. Different treatment of DOM, other topics incl. SVG.

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

WARNING: No "Topic:" lines found.

Default Present: [IBM], Jim_Allan, Jan_Richards
Present: [IBM] Jim_Allan Jan_Richards
Got date from IRC log name: 11 May 2006
Guessing minutes URL: http://www.w3.org/2006/05/11-ua-minutes.html
People with action items: cl ja jr

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report