Re: [aapi] Agenda for 6/26

hi cynthia,
in regards to the HTML and ARIA as-built mapping table , where a role
is not supported and another role is reported such as "cell" or
"grouping" this is because the role of the element that that role
attribute is on is reported.

<div role="alert">  if role="alert" is not supported, then it usually
produces a role="grouping" in MSAA
<td role="alert">  if role="alert" is not supported, then it usually
produces a role="cell" in MSAA

i would suggest that instead of reporting the default roles, it may be
better to have use a term such as "not supported".


regards
Stevef

2009/6/25 Cynthia Shelly <cyns@exchange.microsoft.com>:
> The ARIA Implementation Task Force call will be June 26 at 15:00 UTC on the
> Zakim bridge
>
> 1.617.761.6200 2274 passcode "AAPI"
>
> We'll be on the aapi IRC channel
>
>
>
> Please read section 3, and the mapping tables, and resolve one bug before
> the meeting.
>
>
>
> ·         Bug prioritization (20 minutes)
>
> ·         Section 3 Mapping, starting with 3.6 (20 minutes)
> http://www.w3.org/WAI/PF/aria-implementation/#mapping_special
>
> ·         HTML and ARIA as-built mapping table analysis (20 minutes)
> http://www.w3.org/WAI/PF/wiki/ARIA_as-built_browser_comparison,
> http://www.w3.org/WAI/PF/wiki/HTML_4.x_as-built_browser_comparison



-- 
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