Agenda for ARIA sub team meeting Tuesday, 14th Setember 2010, 19:00 UTC

Tuesday, 14th Setember 2010
Time: 19:00 UTC (20:00 BST; 15:00 EDT; 14:00 CDT; 12:00 PDT)
Name: ARIA mapping call
Code:  2742 ("ARIA") (irc.w3.org:6665)
Zakim Bridge +1.617.761.6200
irc channel= #aria
Agenda:
1. Identify Scribe
2. Discuss bugs below:

= the following have been escalated =

1. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10450>

'Allow lists to be used as menus or tab sets'

reason: role of presentation on lists was rejected by editor.
rationale to be provided in change proposal

2. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10449>
'consider allowing various command-like ARIA roles for h1-h6'

reason: disagreement with editor
rationale to be provided in change proposal

3. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10448>

'Consider broadening the set of allowed roles for command elements'

reason: disagreement with editor
rationale to be provided in change proposal

4. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10493>

'"ARIA restricts usage of this role to one per page" is an unclear
statement'

reason: disagreement with editor
rationale to be provided in change proposal



== The following require discussion by the aria mapping sub team ==

1. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10452>

'Consider documenting attributes that map to ARIA properties in a separate
table'
 -> RESOLVED WONTFIX (as a side note, it seems like a matter of style how
the different tables are broken down, so maybe we can let this one slide)


2. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10462>

'merge ARIA mapping tables and list'
 -> RESOLVED WONTFIX (again, it seems like a matter of style how the
different tables are broken down, so maybe we can let this one slide)


3. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10463>

'provide a comprehensive HTML5 to accessibility API mapping reference'
 -> RESOLVED WONTFIX -- note, this requests a spec change that is not
reflected in the proposal


4. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10467>

'provide headings in the WAI-ARIA section of the spec to make it easier to
understand'
 -> RESOLVED WONTFIX (seems purely an editorial matter again; is this really
important?)


5. details element

 -> no bug on this, but proposal authors agreed that what is in spec
generally makes sense; proposal needs updating


6. <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10496>

'fix error in aria conformance checker advice'
 -> RESOLVED FIXED

7.  <http://www.w3.org/Bugs/Public/show_bug.cgi?id=10464>

'provide clear user friendly links to WAI-ARIA documents in the ARIA section
of the spec'
 -> RESOLVED LATER -- editor proposes to do this later using an automatic
cross-reference tool. Strikes me as reasonable.



= the following are NEW BUGS=

1. conforming use of various aria attributes not specified
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10594

2. thead, tfoot and tbody conflicts in aria section
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10593

3. "h1 to h6 element that does have an hgroup ancestor" not listed in ARIA
section
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10592

4. conflicting info for table element in aria section
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10591

5.Details element Focus problem
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9817
 NOTE: this is not a new bug but has been added to 10066 as it relates to
the <details>, <summary> mapping.

 --
with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium

www.paciellogroup.com | www.wat-c.org
Web Accessibility Toolbar -
http://www.paciellogroup.com/resources/wat-ie-about.html