See also: IRC log
<MichaelC> scribe: Andi
DB: is SHOULD strong enough in first sentence?
Change to MUST
CS: first para - think about how control types and patterns fit into (bug - assign to cyns)
Change "User agents SHOULD notify AT.." to MUST
3.2 - change SHOULD to MUST
change "MAY always expose" to "MAY expose"
3.2, 2nd para - add that desktop APIs also have features that are not in ARIA
3.2 aria-live example - add "at this time", change MUST to "would be" or "can"
3.2. 1st para - when aria ... don't map ... and there is a way in the API to expose a text string, then UAs must expose raw ...
note to Andi: above 3.2 items are actually 3.3
DB: parse role string and take
the first role that means something and expose whole role
string if there is a mechanism
... multiple roles used in case API doesn't support the 1st
choice role
add explanation and compare to font specification
3.4 4th para - change SHOULD to MUST
3.4 bullet # 1 - change SHOULD to MUST
3.4 bullet # 3 - change SHOULD to MUST
3.4 bullet # 4 - attribute is API dependent - remove "xml-roles" - expose as a text string
3.4 - dynamic role sentence - change to a note - change "dynamic role changes" to "Changes to the role attribute"
3.4 add caption to table
CS: thought there was a heading role in MSAA
bug - David - verify ATK mappings
bug - Cynthia - do UIA and Mac mappings
bug - David - do IA2 mappings
3.5 - merge states and properties back into one table
3.5 - bullet # 2 - Map states that are supported in the API
3.5 - new bullet # 3 - add additional information to the description, object attribute, or other text string
bug - table for how to map unsupported states and properties in the different APIs
3.5 - new bullet # 3 - SHOULD
3.5 - bullet # 3 - "object attributes" - change to "additional information" - example - list levels
another good example is "table hint" - layout or data
3.5 - bullet # 4 - correct but hard to read - need to spell out the algorithm for each role
aria spec will be adding a table that lists states & properties for each role
bug - Michael - create table, include 3rd column with implementation details that are only visible in the UAIG
3.5 - bullet # 4 - reword to refer to table
3.5 - bullet # 5 - change "object attribute" to "text string"
3.5 - bullet # 5 - SHOULD
bug - work with browser vendors to come up with convention for this
3.5 - table - should list all properties and states, what they should be set to, and what their defaults are
model after tables in WCAG 2.0 technique and little tables in the aria spec
3.5 - following tables - 1st para - 1st sentence - add "MUST expose"
3.5 - following tables - 1st para - last sentence - remove "at a minimum", change SHOULD to MUST
bug - mapping table for events, decide which are MUSTs
<davidb> Zakim: ??P2 is David_Bolter
<davidb> ok
<davidb> Andi: i forgot to identify myself to Zakim
<davidb> MichaelC: ^
<davidb> (in case it matters)
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, Janina, Cynthia_Shelly Present: Michael_Cooper Andi_Snow_Weaver Janina Cynthia_Shelly David_Bolter Got date from IRC log name: 19 Jun 2009 Guessing minutes URL: http://www.w3.org/2009/06/19-aapi-minutes.html People with action items: 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]