<scribe> Scribe: JR

<jallan> title: UAWG Conference Call

10.1 Associate table cells and headers (P1)

JR: Confused about sufficient techniques

JA: But these are not normative

JT: ATAG uses "sufficient in conjunction"

JT=JR

JR: in cases where both techniques should work together to meet the normative req

JA: So Peter does ScReader just grab DOM?

PP: Not on Linux - we depend on what Firefox gives us
... But we can get table info through API

JA: So doesn't matter about the visual things in 10.1?
... Thinks that separate from visul rendering, there should be an underlying structure.

PP: Right as long as proper table structure is used

JA: CSS craziness plays in here.

PP: Welcome to Web 2.0 :)

JA: Where should this logic be done?

PP: Browser probably will pass.
... But in Linux we can
... can't get DOM

CL: Right on Windows we go to DOM because MSAA not rich enough
... Only browser knows what source is...
... (mean all the components of the browser)

<jallan> CL: if the author used only css to structure a table, then the browser should the provide the structure of the css layout to accessibility api

JA: CSS includes some specific table structure properties
... SHould we require UA's to figure this CSS out?

<jallan> ACTION: JA Issue SHould we require UA's to figure this CSS out, and privide strudture to the accessibility api? [recorded in http://www.w3.org/2006/11/30-ua-minutes.html#action01]

<jallan> Group meeting

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

JA: Our group meeting has been approved for Jan 21,22

C: Peter and Cathy are approved to go

CL: Rich wants PF and UA to have a joint meeting.

JR: AU is likely to pullout.

JA: Still not quite getting his chair status.

Clarify: JA is the chair, but just in terms of the automated w3 system

JA: We have 3 more meeting after today and before xmas

CL: PP and CL to miss Nov 22 mtg

Correction: Dec 21st

Dec 28 no mtg

JA: OK Let's hustle and work on list to try and get our walkthrough done by around end of year...

so a few weeks to prep for f2f

JA: would also like to discuss WCAG, UAAG split

10.2 Highlight selection, content focus, enabled elements, visited links

JA: No particular issue - but brings up same old OS-UA-author stylesheet issue
... ABBR expansion issue related - AT's do lot's of handling

CL: Where in 10.2?

JA: Not - just reminds me of the same bundle of issues

JR: Asks about figure in 10.1, seems to be a mockup?

<scribe> ACTION: JA to Remove image in 10.1 [recorded in http://www.w3.org/2006/11/30-ua-minutes.html#action02]

JR: 10.2 seems to be overly complicated - who uses font family as a highlighting?

<scribe> ACTION: JA to maybe highlight 10.2 for further discussion [recorded in http://www.w3.org/2006/11/30-ua-minutes.html#action03]

CL: Selection info comes from different place
... DOM has focus events
... But for example if gighlighted with text style, have to go to OS for that

<scribe> ACTION: JA to Cross check 10.2 with earlier checkpoint - maybe duplicate [recorded in http://www.w3.org/2006/11/30-ua-minutes.html#action04]

CL: Look at 4.3 and 9.1.

JA: Maybe also 9.3

10.3 Single highlight configuration (P2)

JR: This is yet another modifier-type checkpoint

JA: We have lots of confuration checkpoints
... If we say do this - later we say and allow it to be configured

<scribe> ACTION: JA to Think about larger organization of "configurastion" [recorded in http://www.w3.org/2006/11/30-ua-minutes.html#action05]

JA: Does ScReader care?

PP: Not really - we just get from API.

JA: ScreenMags on Win are using MSAA

PP: On Linux ScreenMags are driven by Screen Readers

10.4 Provide outline view (P2)

JA: Didn't Safari do something with this?

JR: IF not navigable - not useful - if navigable it becomes structured navigation

PP: Useful for someone with low vision

CL: Or cognitive disabilities

JR: Agree with JA to drop TITLE from outline

JA: See your point Cathy that it would not need to be navigable
... Is this too granular - almost technique of 9.9 or important on its own.
... ?

CL: Intent different than navigation.
... Much like in word, a TOC can be created.
... Aaron came back..."no one ever does that"

that=(CSS table markup)

CL: Firefox does not support

<jallan> 10.4 for folks with cognitive issues this is important for non-cluttered visual view

CL: Most CSS things came through to IE DOM as DOM style
... Aaron says mostly conveyed through role attribute and computed style attributes
... role=table cells, etc
... Browser assigns the role

JA: Let's wrap up this call
... Let's try to handle JR and JA's comments on the list

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 "Present: ... " found!
Possibly Present: CL Clarify Correction IBM JA JR JT Jim_Allan P12 PP cklaws jallan parente title
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Agenda: http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0027.html

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 30 Nov 2006
Guessing minutes URL: http://www.w3.org/2006/11/30-ua-minutes.html
People with action items: issue ja require s should ua we

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