Re: Minutes: [aapi] UAI TF meeting Agenda 11 Apr 2013

Link: http://www.w3.org/2013/04/11-aapi-minutes.html

Plain text version follows:

    [1]W3C

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

                                - DRAFT -

                    WAI PF UAIG Weekly Teleconference
                               11 Apr 2013

    [2]Agenda

       [2] http://lists.w3.org/Archives/Public/wai-xtech/2013Apr/0006.html

    See also: [3]IRC log

       [3] http://www.w3.org/2013/04/11-aapi-irc

Attendees

    Present
           David_Bolter, Joseph_Scheuhammer

    Regrets
           Cynthia_Shelly

    Chair
           Joseph_Scheuhammer

    Scribe
           clown

Contents

      * [4]Topics
          1. [5]issue-566
      * [6]Summary of Action Items
      __________________________________________________________

    <scribe> scribenick: clown

    trackbot, start meeting

    <trackbot> Meeting: Protocols and Formats Working Group
    Teleconference

    <trackbot> Date: 11 April 2013

issue-566

    ISSUE-566?

    <trackbot> ISSUE-566 -- Inconsistency between Spec's required
    states/properties for certain roles and UAIG's error handling
    of those roles/states/properties -- open

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

       [7] https://www.w3.org/WAI/PF/Group/track/issues/566

    [8]http://www.w3.org/WAI/PF/aria-implementation/#document-handl
    ing_author-errors

       [8] http://www.w3.org/WAI/PF/aria-implementation/#document-handling_author-errors

    JS: describes the issue and the history of the issue.

    <davidb> discussion ensues about how crazy the idea of a
    literal "undefined" value is

    <davidb> noticing earlier bullet about "When exposing as a
    platform API Boolean state, treat "", "undefined" or no
    attribute present as false. Treat any other value as true."

    [9]http://www.w3.org/WAI/PF/aria/roles#requiredState

       [9] http://www.w3.org/WAI/PF/aria/roles#requiredState

    <davidb> also discussing whether ARIA spec "required" aria-
    attributes means required for the author to explicitly add or
    if required == implicit

    <davidb> seems authors must be explicit is the correct
    interpretation

    <davidb> note UIAG often uses hacker sense of 'undefined'

    JS: I will bring this up at the Mon call — the bit about the
    bullet where "undefined" is generall mapped to "false". Also
    the attribute absence is mapped to "false", but shouldn't be.
    ... speaks to the *-able states. If the attribute is missing (=
    undefined?), then the accessible is not *-able in some sense.
    E.g., not grab-able.

    DB: what about a role="checkbox"?

    JS: that's covered by the required state; that aria-checked is
    required for checkbox.

    DB: worried that there still might be gotchas.

    <davidb> (aside: language semantics between UIAG and ARIA spec
    might be bit different)

    JS: Proposed algorithm: if the role requires an aria-* and it
    is absent, then the accessible gets any relevant *-able state.
    Othewise, if absent, the *-able state is effectively "false."
    ... Proposed algorithm:  if the role requires an aria-* and it
    is absent, then the accessible gets any relevant *-able state.
     Otherwise it is not required by the role and the relevant
    *-able state is effectively "false."

    <davidb> I might change it to something along the lines of, "if
    the role obviously implies the children are *-able then expose
    that way"

    <davidb> and avoid the 'required attribute' thing

    option: [10]http://www.w3.org/WAI/PF/aria/roles#option

      [10] http://www.w3.org/WAI/PF/aria/roles#option

    JS: options should have a required aria-selected.

    DB: where are options used?

    JS: they must appear within a "select"
    ... select is abstract.
    ... but the concrete sub-classes are combobox, listbox, menu,
    radiogroup, and tree.

    [11]http://www.w3.org/WAI/PF/aria/roles#treeitem

      [11] http://www.w3.org/WAI/PF/aria/roles#treeitem

    <davidb> DB: wondering if options can always default to
    selectable… unsure

    <davidb> tree item inherits from option...

    JS: notes that option is defined as "A selectable item"

    DB: options that are within selects are always selectable.

    <davidb> DB: by default

    DB: that might override the bullet in the UAIG re: "",
    "undefined", and absence are treated as false.

    JS: I will bring all of this up at Monday's meeting.

    absent: Cynthia_Shelly

    s/absent:  Cynthia_Shelly//

    s/absent\: Cynthia_Shelly/ /

Summary of Action Items

    [End of minutes]
      __________________________________________________________


     Minutes formatted by David Booth's [12]scribe.perl version
     1.137 ([13]CVS log)
     $Date: 2013-04-11 18:08:40 $
      __________________________________________________________

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

-- 
;;;;joseph.


'A: After all, it isn't rocket science.'
'K: Right. It's merely computer science.'
              - J. D. Klaun -

Received on Thursday, 11 April 2013 18:13:57 UTC