W3C

- DRAFT -

AAPI

04 May 2010

See also: IRC log

Attendees

Present
Michael_Cooper, Andi_Snow_Weaver, Cynthia_Shelly, David_Bolter
Regrets
Chair
Cynthia
Scribe
Andi

Contents


<scribe> Scribe: Andi

<davidb> sorry yes.

<davidb> coming

default value of state/property

DB: confused about what default value means

add wording similar to wording in 5.3 Author Errors "If a required aria property for a given role is missing, user agents SHOULD process as if the following values were provided:"

<davidb> DB: great

bug 8947: add overrides to first column of state/property mapping table

bug 8907: this belongs in the Authoring Practices Guide, not UAIG. open tracker action

issue 59: related to bug CS is going to work on this week

<cyns> http://www.w3.org/WAI/PF/Group/track/issues/88

issue 86 & 87: Andi to close when she closes related bug

editorial: "accessible tree" should be "accessibility tree"

issue 379: close

issue 393: add a note to HTML specific sections "This section is specific to HTML and may not be relevant to other technologies."

issue 383: for MSAA and UIA, take the text from the referenced element in aria-labelledby and make it the name of the referencing element

issue 383: what to do about IA2 and ATK. If the referenced element has role="presentation", it won't be an accessible object (in the accessibility tree)

CS: sounds like an author error, UA should probably ignore the referenced element if it has role="presentation"

DB: agree this is an author error, behavior is unknown

should role="presentation" win or "labelledby" win?

bug - corresponding to issue 383 - assign to David

issue 391

CS: agree with the issue but it's a huge work item
... is this really an aria thing? seems like it's an HTML thing

DB: starting writing a document on caret browsing in contenteditable areas
... keyboard operation inside contenteditable section of web page is not well spec'ed
... should be spec'ed outside ARIA

CS: refer to HTML task force or UAAG

DB: applies to any editable region, not just ARIA

issue 391: re-assign to HTML task force

Next week's agenda: pick up with 395 and continue through actions

<scribe> ACTION: refer issue 391 to HTML task force or UAAG [recorded in http://www.w3.org/2010/05/04-aapi-minutes.html#action01]

Summary of Action Items

[NEW] ACTION: refer issue 391 to HTML task force or UAAG [recorded in http://www.w3.org/2010/05/04-aapi-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/05/04 18:17:21 $

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)

Found Scribe: Andi
Inferring ScribeNick: Andi

WARNING: No "Topic:" lines found.

Default Present: Michael_Cooper, Andi_Snow_Weaver, Cynthia_Shelly, David_Bolter
Present: Michael_Cooper Andi_Snow_Weaver Cynthia_Shelly David_Bolter
Got date from IRC log name: 04 May 2010
Guessing minutes URL: http://www.w3.org/2010/05/04-aapi-minutes.html
People with action items: 391 issue refer

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]