<jallan> scribe: JA

<jallan> PP: reviewed mozilla and Gnome conference...

<jallan> scribe: jallan

<parente> WAI-ARIA

there was some discussion about AJAX and ARIA

http://www.w3.org/2006/08/backplane/

http://www.w3.org/2005/Incubator/wcl/XGR-report/

8.1 Implement Accessiblity Features (P1)

add references to HTML and XHTML

CL: not clear how <col> and <colgroup> enable accessibility
... UAAG test suite item #195 about <col> and <colgroup>, does not make sense

what kind of information are we trying to convey to the user about the relationship of columns in a colgroup. what is the UA supposed to communicate to the user?

CL: need to figure out how they benefit accessibiltiy., if no benefit then remove from techniques.

if beneficial, then describe information provided to the user

need to provide examples

Should we include tabindex and accesskey. both are confusing to end users

<scribe> ACTION: JA add references to HTML and XHTML [recorded in http://www.w3.org/2006/10/12-ua-minutes.html#action01]

<scribe> ACTION: JA issues col, colgroup, thead, tbody, tfoot, accesskey, tabindex. benefit accessibilty? are there accessibilty examples in WCAG or HTML? [recorded in http://www.w3.org/2006/10/12-ua-minutes.html#action02]

CL: although tabindex=-1 and accesskey are used significantly in AJAX and HTML

thats DHTML not html

<scribe> ACTION: JA add comments - although tabindex=-1 and accesskey are used significantly in AJAX and HTML [recorded in http://www.w3.org/2006/10/12-ua-minutes.html#action03]

8.2 conform to specifications (p2)

this is very vague and confusing. You can pick and choose which specification to conform

<scribe> ACTION: JA issue: does 8.2 need to be removed due to vagueness [recorded in http://www.w3.org/2006/10/12-ua-minutes.html#action04]

9.1 Provide content focus (p1)

no techniques.

CL: AJAX and DHTML using tabindex=-1 to allow focus on non-focusable elements

there is work on style guide for DHTML elements for keyboard navigation and focus

CL: may need techniques for using javascript to move content focus

<scribe> ACTION: JA issue: update defintions of "enabled elements" and "interactive elements" to provide for components used in DHTML [recorded in http://www.w3.org/2006/10/12-ua-minutes.html#action05]

<scribe> ACTION: JA reference WCAG 2 for techniques [recorded in http://www.w3.org/2006/10/12-ua-minutes.html#action06]

CL: where is the line drawn between what the UA vs author coding should do to provide for accessibility

<scribe> ACTION: JA issue where is the line drawn between what the UA vs author coding should do to provide for accessibility [recorded in http://www.w3.org/2006/10/12-ua-minutes.html#action07]

CL: UA responsibiltiy to generate focus for elements so accessiblity api can provide info to the AT

discussion of caret browsing in documents

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: JA
Found Scribe: jallan
Inferring ScribeNick: jallan
Scribes: JA, jallan
Default Present: Jim_Allan, parente, cklaws
Present: Jim_Allan parente cklaws
Regrets: JR
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0005.html

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

Got date from IRC log name: 12 Oct 2006
Guessing minutes URL: http://www.w3.org/2006/10/12-ua-minutes.html
People with action items: 8.2 add defintions does elements enabled interactive issue ja need of references update

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