[aapi] Minutes: UAI TF Meeting Wed 20 August 2014

~~~~~~~~~
NB: This week's meeting had been moved to the 20th due to personal
schedule conflicts on the 19th. The link below for the HTML version of
the minutes includes noise associated with trying to arrange an ad-hoc
meeting. I've trimmed this from the plain text below. Apologies for any
inconvenience.
--jd
~~~~~~~~~

Link: https://www.w3.org/2014/08/20-aapi-minutes.html

Plain text follows:

   [1]W3C

      [1] http://www.w3.org/

                               - DRAFT -

           Protocols and Formats Working Group Teleconference
                              20 Aug 2014

   See also: [2]IRC log

      [2] http://www.w3.org/2014/08/20-aapi-irc

Attendees

   Present
          Bryan_Garaventa, Joseph_Scheuhammer, Joanmarie_Diggs,
          cyns

   Regrets
          David_Bolter

   Chair
          Joseph_Scheuhammer

   Scribe
          Joanie

Contents

     * [3]Topics
         1. [4]News: ISSUE-657/ACTION-1498: (All) New role="term"
            to associate with role="definition".
         2. [5](Cynthia) Name computation.
         3. [6]News: ISSUE-657/ACTION-1498: (All) New role="term"
            to associate with role="definition".
         4. [7]ACTION-1199: (All) Browsers SHOULD throw errors for
            missing required attributes.
     * [8]Summary of Action Items
     __________________________________________________________

News: ISSUE-657/ACTION-1498: (All) New role="term" to associate with
role="definition".

(Cynthia) Name computation.

   JS: Cynthia said the spec algorithm is too hard to understand
   and must be rewritten.

   CS: Michael and I have an action to create a diagram at TPAC.

   <cyns>
   [10]http://rawgit.com/w3c/aria/master/implementation/aria-imple
   mentation.html#mapping_additional_nd_name

     [10]
http://rawgit.com/w3c/aria/master/implementation/aria-implementation.html#mapping_additional_nd_name

   CS: This is written as an algorithm and not inputs and outputs,
   so it's hard to test.
   ... I was thinking about trying to do this as an input-output.

   <cyns>
   [11]http://rawgit.com/w3c/aria/master/implementation/aria-imple
   mentation.html#mapping_additional_nd_te

     [11]
http://rawgit.com/w3c/aria/master/implementation/aria-implementation.html#mapping_additional_nd_te

   CS: Maybe having some examples?

   JS: There is an example in 2A.
   ... And I think there are more examples in the spec.

   <clown>
   [12]http://rawgit.com/w3c/aria/master/spec/aria.html#namecomput
   ation

     [12] http://rawgit.com/w3c/aria/master/spec/aria.html#namecomputation

   JS: The above is the spec version.
   ... The examples (only 2) are at the bottom.
   ... Did this discussion happen in the last two weeks?

   CS: About a month ago.

   JS: Rich is trying to write the SVG document and thinks the
   core mapping is too specific to HTML. He'd like it more
   generic.
   ... I said there's not alot in here that's specific to HTML.
   There's some, but not alot.
   ... I suggested that if it is so specific to the language, it
   shouldn't be in the core guide.

   CS: I agree.

   JS and CS: Then it shouldn't be in the spec either.

   CS: Some parts are generic, like aria-label and
   aria-labelledby.

   JS: Rich is concerned about CSS before and after because it
   doesn't work in SVG.
   ... Is that then a bug in SVG? Besides, the CSS before and
   after is just an example.
   ... If you don't have a name-from-contents scenario, the text
   nodes are not visited.
   ... Number 3 is buried in there and just not well worded.

   CS: Is there a normative requirement anywhere in 3? I don't see
   one.

   JS: (quotes section text)
   ... A lot of this stuff needs to be fixed.

   CS: We should pull out the normative stuff and then figure out
   how to reorganize the rest.

   CS and JS: (Each stated they probably won't have the time in
   the next couple of weeks)

   JS: Is this part of ARIA 1.1 work?

   CS: I think so. And I think we should suggest this be taken out
   of the ARIA spec.

   <clown> [13]https://www.w3.org/WAI/PF/Group/track/actions/1151

     [13] https://www.w3.org/WAI/PF/Group/track/actions/1151

   JS: The above is the action for creating the flowchart.

   CS: There are two actions: The flowchart and the text.

   JS: Michael seems to have a due date of Sept 8.

   <clown> [14]https://www.w3.org/WAI/PF/Group/track/issues/522

     [14] https://www.w3.org/WAI/PF/Group/track/issues/522

   action-1474

   <trackbot> action-1474 -- Cynthia Shelly to Work with joseph s.
   and david b. to rewrite text alternative computation for both
   the aria spec. and the core accessibility api mappings
   specification. -- due 2014-08-12 -- OPEN

   <trackbot>
   [15]https://www.w3.org/WAI/PF/Group/track/actions/1474

     [15] https://www.w3.org/WAI/PF/Group/track/actions/1474

   CS: Reiterates that the first step is to identify the normative
   items. I think this will help Rich too.

   JS: I've changed the date, I've changed the owner, and I have a
   pretty good idea about what needs to be done now.

News: ISSUE-657/ACTION-1498: (All) New role="term" to associate with
role="definition".

   <clown> issue-657

   <trackbot> issue-657 -- Consider 1.1 "term" role (related to
   html dfn/dt elements) in addition to the 1.0 "definition"
   (equiv to html dd element) -- open

   <trackbot> [16]https://www.w3.org/WAI/PF/Group/track/issues/657

     [16] https://www.w3.org/WAI/PF/Group/track/issues/657

   JS: There is in HTML a definition list which has dt and dd
   elements. The first is the term; the second the definition.
   ... We already have a definition role in ARIA; we lack a term
   role.
   ... It has been suggested we add a term role to be symetrical.
   ... Related question: What about dfn? And how to we associate
   the proposed new role.

   <clown> action-1498

   <trackbot> action-1498 -- James Craig to Draft "term" role
   (related to html dfn/dt elements) in addition to the 1.0
   "definition" (equiv to html dd element) -- due 2014-08-25 --
   OPEN

   <trackbot>
   [17]https://www.w3.org/WAI/PF/Group/track/actions/1498

     [17] https://www.w3.org/WAI/PF/Group/track/actions/1498

   JS: James Craig is going to draft some text for our
   consideration.

   oy

ACTION-1199: (All) Browsers SHOULD throw errors for missing required
attributes.

   <clown>
   [18]http://www.w3.org/TR/wai-aria-implementation/#document-hand
   ling_author-errors

     [18]
http://www.w3.org/TR/wai-aria-implementation/#document-handling_author-errors

   JS: If you look at the current 1.0 mapping guide under the
   author errors section

   <clown> "If a required WAI-ARIA attribute for a given role is
   missing, user agents SHOULD process the attribute as if the
   values given in the following table were provided. User agents
   MAY report these errors via their console."

   JS: There's a paragraph in the middle(ish) of that section that
   reads the above.
   ... There's been an action that the final MAY should become a
   SHOULD.
   ... I'm willing to change it. It doesn't really add a lot to
   the user agents, though it does make it stronger.
   ... I guess this would be shown via the javascript console
   ... I'd like to get David's opinion.

   JD: I think it's good if it helps web devs find their errors.

   JS: Next time I pass through these actions, I will put that in
   and mention it to David.

Summary of Action Items

   [End of minutes]
     __________________________________________________________


    Minutes formatted by David Booth's [19]scribe.perl version
    1.138 ([20]CVS log)
    $Date: 2014-08-20 20:30:08 $
     __________________________________________________________

     [19] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
     [20] http://dev.w3.org/cvsweb/2002/scribe/

Received on Wednesday, 20 August 2014 20:39:56 UTC