W3C

- DRAFT -

AAPI

11 Oct 2011

See also: IRC log

Attendees

Present
David_Bolter, Andi_Snow-Weaver, Cynthia_Shelly
Regrets
Chair
Andi_Snow-Weaver
Scribe
Andi_Snow-Weaver

Contents


<scribe> Scribe: Andi_Snow-Weaver

<scribe> ScribeNick: Andi

bug 11811

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

AS: First sentence, change "contained document" to "sub-document"
... Second sentence starts out talking about frame elements and ends up talking about iframe elements
... change all to "frame or iframe"

<davidb> maybe: "For example, in a mashup scenario, it is usually the nearest parent container with aria-live, aria-atomic, aria-relevant, and aria-busy (state) that decides what gets mapped through accessibility API"

AS: "it is usually the nearest parent container with aria-live, aria-atomic, aria-relevant, and aria-busy (state) that decides what appears on the child for the corresponding attributes in the Accessibility API."
... Remove sentence that starts out "for example, in a mashup scenario..."

CS: "This allows the author of the parent or containing document to control the assertiveness of the sub-document."

<scribe> ACTION: Andi to work on language to make it normative - these are SHOULDs, not MUSTs [recorded in http://www.w3.org/2011/10/11-aapi-minutes.html#action01]

CS: in the table, for UIA, it goes into AriaProperties

Remove bullets 2 and 3 from the list.

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

AS: bullets after the table

DB: reads definiton of root WAI-ARIA node

CS: think it would mean the <frame> not the <body> in this case
... suggest frameset or iframe

DB: might be talking about a body element of a frame

CS: bullet 1 sounds like an author error

DB: or somebody trying to dup somebody

CS: is it a valid way to group controls in a single place?
... need to ask ARIA TF for the use case for these bullets

DB: think 4 bullets could be collapsed into one idea

CS: when there are properties on the frame, use them. If not, look to the body of the contained document

DB: Aaron's idea was to always use the properties on the body of the contained document except in the case of -live, -atomic, -relevant, and -busy
... not sure why aria-selected, aria-valuenow, aria-valuetext, aria-activedescendant are called out

CS: suggest deleting these 4 bullets and saying "except for -live, -atomic, -relevant, and -busy, use the attributes on the body of the contained document"

AS: Note contains normative language

CS: should be a must

DB: security issue

Summary of Action Items

[NEW] ACTION: Andi to work on language to make it normative - these are SHOULDs, not MUSTs [recorded in http://www.w3.org/2011/10/11-aapi-minutes.html#action01]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2011/10/11 16:34:56 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/a-live/-live/
Found Scribe: Andi_Snow-Weaver
Found ScribeNick: Andi
Default Present: David_Bolter, Andi_Snow-Weaver, Cynthia_Shelly
Present: David_Bolter Andi_Snow-Weaver Cynthia_Shelly
Got date from IRC log name: 11 Oct 2011
Guessing minutes URL: http://www.w3.org/2011/10/11-aapi-minutes.html
People with action items: andi

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


[End of scribe.perl diagnostic output]