W3C

- DRAFT -

AAPI

02 Dec 2010

See also: IRC log

Attendees

Present
Andi_Snow_Weaver, Cynthia_Shelly, David_Bolter
Regrets
Chair
Cynthia
Scribe
Andi

Contents


<scribe> Scribe: Andi

Action items from last week

bug 6883: http://www.w3.org/Bugs/Public/show_bug.cgi?id=6883

bug 7634: http://www.w3.org/Bugs/Public/show_bug.cgi?id=7634

AS: started discussion on mailing list

Thread starts here: http://lists.w3.org/Archives/Member/w3c-wai-pf/2010OctDec/0069.html

http://lists.w3.org/Archives/Member/w3c-wai-pf/2010OctDec/0070.html

CS: names and values are completely different things in MSAA
... agree that AT should read it but don't think that putting it in the name is the right way to accomplish that
... might be able to get it changed in a future release of IE but doubt it. The team is going to think the spec is wrong.

AS: Joseph agrees that this could be a MAY but doesn't agree that the IE implementation is correct in the example given in the e-mail

DB: if we pass the string "flash the screen times" to the AT, then the AT has to figure out where to put the number "5"

CS: this is a problem with localization

DB: yes, but it happens in the wild

CS: can live with MAY or SHOULD but IE probably won't change

DB: okay with SHOULD

http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_nd

CS: think this is the only place where Microsoft "disagrees" with what's in the UAIG vs. just haven't gotten around to doing what's in there

DB: what does Safari do?

AS: not sure but think that if Safari didn't do this, James would have raised an issue with the spec
... if Safari includes the embedded control within the text alternative computation, then we have two implementations and there is no issue

bug 10288: http://www.w3.org/Bugs/Public/show_bug.cgi?id=10288

DB: haven't figured out who wants this so not addressing it for now

AS: but this may keep us from getting to W3C Recommendation if we have something in the ARIA spec but there is no mapping for it
... we also don't have a mapping for "search"

CS: think search is mapped as a text box

DB: also HTML5 element input type="search"

CS: think it's a hole but we don't have it right now
... pretty sure it would show up in the UIA role property

put "no mapping" in the table. Add an editorial note and ask for feedback.

footnote or asterisk

bug 9368

AS: completed the work but needs thorough review by David and Cynthia

bug 8319: http://www.w3.org/Bugs/Public/show_bug.cgi?id=8319

CS: had related HTML5 piece of work

AS: not sure this is related to the UAIG Last Call

bug 9656: not done

<cyns> command stuff http://www.w3.org/html/wg/wiki/ChangeProposals/ARIAinHTML5#basis_for_changes_to_command_roles

bug 7064: closed

bug 7984: Steven F has not responded to two pings from Andi but this is not a LC issue

<cyns> http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html

bug 7128 is fixed and closed

Cynthia: find out what IE does with aria-hidden. Does it remove the element from the tree? (action 666)

DB: has patch ready to go for FF to remove it from the tree

http://www.w3.org/WAI/PF/Group/track/actions/666

<scribe> ACTION: David to find out what AccessibleSelection should be as there is no interface in IA2 for AccessibleSelection [recorded in http://www.w3.org/2010/12/02-aapi-minutes.html#action01]

action166 is done - also closes actions 632 and 667 and bug 9363

HTML and non-ARIA specific sections, should they really be normative?

CS and DB think maybe they should not be

<scribe> ACTION: Andi to discuss with Michael Cooper to get his recommendation [recorded in http://www.w3.org/2010/12/02-aapi-minutes.html#action02]

Section 3.1

These are the steps for implementing tabindex

AS: steps 8 & 9 look like maybe they should be covered in 4.1 where we have the rules for what to put in the accessible tree and what must not be in it.
... 8 is already covered I think
... but on second thought, 9 had better stay where it is

DB: change "The user agents MUST do the following to enable tabindex on all elements" to "The user agent MUST do the following to enable accessible tabindex usage on all elements."

Summary of Action Items

[NEW] ACTION: Andi to discuss with Michael Cooper to get his recommendation [recorded in http://www.w3.org/2010/12/02-aapi-minutes.html#action02]
[NEW] ACTION: David to find out what AccessibleSelection should be as there is no interface in IA2 for AccessibleSelection [recorded in http://www.w3.org/2010/12/02-aapi-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/12/02 18:57:22 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/action 166/action166?/
Succeeded: s/+1.416.848.aaaa/David_Bolter/
Succeeded: s/Andi: the minutes don't show me as present (not sure it matters)//
Succeeded: s/I didn't identify myself//
Succeeded: s/i showed up as a phone number//
Succeeded: s/action166?/action166/
Succeeded: s/through review by David and Cynthia/thorough review by David and Cynthia/
Succeeded: s/action166: Done/action166 is done/
Succeeded: s/oops, on my way//
Found Scribe: Andi
Inferring ScribeNick: Andi
Default Present: Andi_Snow_Weaver, Cynthia_Shelly, David_Bolter
Present: Andi_Snow_Weaver Cynthia_Shelly David_Bolter
Got date from IRC log name: 02 Dec 2010
Guessing minutes URL: http://www.w3.org/2010/12/02-aapi-minutes.html
People with action items: andi david

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


[End of scribe.perl diagnostic output]