<scribe> Scribe: Andi

SF: work so far hasn't had much input from others
... can get some information from ARIA UAIG

DB: so need to scope out purpose that each document will serve

<Stevef> http://dev.w3.org/html5/html-api-map/overview.html

SF: have been finding differences in name calculation across browsers
... should be consistent
... have been mapping out algorithms for providing accessible names
... label element on form control, name changes depending on whether you wrap with <label> element or use <label for=id>
... difficult to provide authoring guidance using standard HTML labeling mechanisms to guarantee a particular name or description across browsers

DB: probably need two phone calls and a bunch of work in between
... have automated tests, have schema of rules for name calculation
... SF had indicated that in some cases, FF was not doing what he wanted

CS: need to look at what we're all doing, figure out if differences matter, change where we need to

SF: FF does some different things when you have placeholder or title attributes
... agree we have to weed out the cases where it doesn't really matter
... need some agreed rules across browsers

CS: as we update, there has to be a review loop with people that don't come to these phone calls

SF: lot of elements that don't have any particular role mapping - in HTML 5 as well
... is there a semantic that could be created that would be useful

CS: IE 9 used UIA text pattern for a lot of test constructs

SF: bunch of new interactive elements and controls, some are simple, some are more complex
... need to define roles and relationships and how they will be conveyed

CS: color picker worries me - UI is totally unspecified by design
... how do we specify API implementation when we don't know what the UI will be
... could be a color picker like we think of it but could be list of radio buttons
... API mappings would be entirely different, depending on what the UI is
... could be that we don't spec that or have examples of how they might look in the API

SF: in the document, have an example for each of the accessible features
... may not be complete or correct - useful to provide those sort of details
... has begun to be implemented in Chrome and Webkit
... but accessibility implementation is nowhere yet

CS: so the first step is to review it amongst ourselves, then take it and review with others
... probably need to try a few things - get input from broader group

DB: in terms of the interactive elements, does W3C ever spec out what the mouse/keyboard is supposed to do

CS: no, but they spec out the widget in a lot of detail in some cases
... menu is spec'ed to a great level of detail but the color picker just says to use the OS color picker

DB: not sure this is the role of the W3C

CS: agree we can delay dealing with those kinds of things but we need to record an issue
... implementors need to know that they need to use a color picker that has accessibility or that they have to implement it themselvs
... may be more functional requirements than the level of detail we normally have in the spec
... let's pick a section to review next week - Section 4 HTML attribute to Accessibility API State and Property Mapping Matrix sounds like a good one

SF: useful to walk through and decide whether something needs to be in the table or not

CS: don't like leaving things out of the table - don't know whether it was just forgotten

SF: can include all and indicate which ones are not mapped
... updated information in the UAIG role mapping that need to be picked up

new Actions

http://www.w3.org/WAI/PF/Group/track/products/10

<davidb> http://www.w3.org/2002/09/wbs/myQuestionnaires

AS: need to have a walk-through of the UAIG

<davidb> http://www.w3.org/2002/09/wbs/32212/201106_uaig-review/

AS: planning to schedule a day-long conference call to do it
... be sure to answer the survey

CS: Friday is looking like the best day

AS: Friday is not a good day for Europeans
... but don't really think it will take 8 hours so maybe we can get through most of it before they have to leave

CS: trying to rearrange some things so that Monday or Tuesday would work

DB: have hard stop at 4 ET

http://www.w3.org/WAI/PF/Group/track/products/10

Issue 442: http://www.w3.org/WAI/PF/Group/track/products/10

http://www.w3.org/WAI/PF/Group/track/issues/442

DB: FF exposes aria-valuetext with priority over aria-valuenow
... think there is a way to get both

CS: IE doesn't support aria-valuetext yet so can implement however it makes sense

<scribe> ACTION: Andi take a look at f2f minutes to see if there is relevant discussion that needs to be captured in the Action [recorded in http://www.w3.org/2011/05/12-aapi-minutes.html#action01]

issue 439: http://www.w3.org/WAI/PF/Group/track/issues/439

CS: could put in aria properties, AT would have to know the API doesn't support mixed and look for it elsewhere
... but have to specify what should go in the API, kind think "unchecked" since that's the default but not sure

<scribe> ACTION: Cynthia look at MS APIs to see if any don't support "mixed" [recorded in http://www.w3.org/2011/05/12-aapi-minutes.html#action02]

<scribe> ACTION: David to look at IA2 and ATK to see if they don't support "mixed" [recorded in http://www.w3.org/2011/05/12-aapi-minutes.html#action03]

<scribe> ACTION: Andi to check with James to see if OS X doesn't support "mixed" [recorded in http://www.w3.org/2011/05/12-aapi-minutes.html#action04]

CS: if all support, then just need a generic note for any that might not support it to map to whatever API feature you have that for passing a text string

issue 440: http://www.w3.org/WAI/PF/Group/track/issues/440

action 782 http://www.w3.org/WAI/PF/Group/track/products/10

AS: think this one is already closed

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

DB: IA2 has a role for table caption, even has an event for caption changes
... feels like an author error

CS: similar to role="presentation" and alt
... if consistent with HTML 5 decision on alt, there isn't anything to apply the name to so it's just text like the rest of the table
... could put caption role on it but it's not a caption for anything anymore
... validator will flag as not conforming
... table with role="presentation" is a layout table
... maybe we should look at HTML 5 spec and see what to do

<scribe> ACTION: Andi to create bug and assign to David [recorded in http://www.w3.org/2011/05/12-aapi-minutes.html#action05]

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/attribute section sounds/Section 4 HTML attribute to Accessibility API State and Property Mapping Matrix sounds/
Succeeded: s/action 782:/action 782/
Succeeded: s/role=presentation/role="presentation"/
Succeeded: s/[Mozilla]/David_Bolter/
Found Scribe: Andi
Inferring ScribeNick: Andi
Default Present: David_Bolter, Andi_Snow-Weaver, Cynthia_Shelly
Present: Cynthia_Shelly Andi_Snow-Weaver Steve_Faulkner David_Bolter
Got date from IRC log name: 12 May 2011
Guessing minutes URL: http://www.w3.org/2011/05/12-aapi-minutes.html
People with action items: andi apis at cynthia david look ms

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