Minutes: [aapi] UAI TF meeting Agenda Thu May 30 2013

Link: http://www.w3.org/2013/05/30-aapi-minutes.html

Plain text version follows:

    [1]W3C

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

                                - DRAFT -

            Protocols and Formats Working Group Teleconference
                               30 May 2013

    [2]Agenda

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

    See also: [3]IRC log

       [3] http://www.w3.org/2013/05/30-aapi-irc

Attendees

    Present
           Joseph_Scheuhammer, Cynthia_Shelly

    Regrets
           David_Bolter

    Chair
           Joseph_Scheuhammer

    Scribe
           clown

Contents

      * [4]Topics
          1. [5]ACTION-1200
          2. [6]ISSUE-550
          3. [7]ACTION-1221
          4. [8]ACTION-1222
          5. [9]remaining issues
          6. [10]551
          7. [11]issue-550
          8. [12]560
          9. [13]issue-564
         10. [14]issue-566
         11. [15]issue-570
         12. [16]issue-582
         13. [17]583
         14. [18]issue-584
      * [19]Summary of Action Items
      __________________________________________________________

    <trackbot> Date: 30 May 2013

    <scribe> scribenick: clown

    previous: [20]http://www.w3.org/2013/05/16-aapi-minutes.html

      [20] http://www.w3.org/2013/05/16-aapi-minutes.html

ACTION-1200

    action-1200?

    <trackbot> ACTION-1200 -- Cynthia Shelly to create table for
    author errors in UAIG, with columns for each API. -- due
    2013-05-01 -- OPEN

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

      [21] https://www.w3.org/WAI/PF/Group/track/actions/1200

    CS: Haven't done it, but on my to-do list.

    JS: let's change the due date.

    CS: let's set it to two weeks from now.

ISSUE-550

    issue-550?

    <trackbot> ISSUE-550 -- Come up with a date to stop editing
    UAIG in preparation for the next Last Call Draft -- closed

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

      [22] https://www.w3.org/WAI/PF/Group/track/issues/550

    JS: I have closed this one.

ACTION-1221

    action-1221?

    <trackbot> ACTION-1221 -- Joseph Scheuhammer to for ISSUE-559,
    remove the text near the end of the section about ATK/AT-SPI
    about aria-atomic and member-of, and point to the
    aria-atomic='true' entry in the mapping table. -- due
    2013-05-16 -- OPEN

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

      [23] https://www.w3.org/WAI/PF/Group/track/actions/1221

    JS: I have discussed with David.
    ... the best approach, we think, is to remove text from the
    AT-SPI section.
    ... I will do that soon.

ACTION-1222

    ACTION-1222?

    <trackbot> ACTION-1222 -- David Bolter to look into ISSUE-583,
    and think about section 4.3, step 4A to see if that answers the
    question. -- due 2013-05-16 -- OPEN

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

      [24] https://www.w3.org/WAI/PF/Group/track/actions/1222

    JS: David action, but he is not here.

remaining issues

    [25]https://www.w3.org/WAI/PF/Group/track/products/10

      [25] https://www.w3.org/WAI/PF/Group/track/products/10

    <scribe> agenda:
    [26]http://lists.w3.org/Archives/Public/wai-xtech/2013May/0009.
    html

      [26] http://lists.w3.org/Archives/Public/wai-xtech/2013May/0009.html

    issue-486?

    <trackbot> ISSUE-486 -- UAIG has some MUST requirements that
    could only be tested in HTML 5, but 1) the ARIA spec is being
    tested only against HTML 4 and we prefer to do the same with
    UAIG, and 2) HTML 5 isn't complete; so we need to deal with
    this in the UAIG CR exit criteria n -- open

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

      [27] https://www.w3.org/WAI/PF/Group/track/issues/486

    JS: text about mapping conflicts wrt html5 with some MUST
    statements. These may have already been tested.

    CS: Yes, we are testing in modern browsers.
    ... not sure this is an issue any more.

    JS: the tabindex information is now part of html5, so it may
    not even need to be there.

    CS: may be problematic to remove now.

    action-1136?

    <trackbot> ACTION-1136 -- Joseph Scheuhammer to ask the PFWG on
    the Mon call, what issue-486 is all about. -- due 2012-12-20 --
    CLOSED

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

      [28] https://www.w3.org/WAI/PF/Group/track/actions/1136

    [29]http://lists.w3.org/Archives/Public/wai-xtech/2013May/0009.
    html

      [29] http://lists.w3.org/Archives/Public/wai-xtech/2013May/0009.html

    [30]http://www.w3.org/WAI/PF/aria-implementation/#mapping_addit
    ional_nd_te

      [30] http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_nd_te

    CS: can you check with Steve Faulkner?
    ... what is the status of the html5 section 4.8.1.1?
    ... he had written a separate document, and there is an issue
    if it belongs in the HTML5 spec, a separate document, owned by
    wcag, or something else.

    JS: are you referring to the editorial note?

    CS: yes, but also the box above since it references the section
    in the HTML5 spec (4.8.1.1) that the editorial note is talking
    about.

    action-1142?

    <trackbot> ACTION-1142 -- Joseph Scheuhammer to remove
    reference to HTML5 @alt section in the UAIG name calculation
    section. -- due 2013-02-01 -- CLOSED

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

      [31] https://www.w3.org/WAI/PF/Group/track/actions/1142

551

    issue-551?

    <trackbot> ISSUE-551 -- When UAIG enters CR, we need to ask
    Director if we have to have 2 mappings to all platforms, or
    just demonstrate implementability of mapping via a sample and
    say all the mappings are therefore defined implementable --
    open

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

      [32] https://www.w3.org/WAI/PF/Group/track/issues/551

    CS: I think this is actually closed in that Michael asked Judy.
    ... can you ask him on Mon?

    JS: yes.

    action-1152?

    <trackbot> ACTION-1152 -- Cynthia Shelly to investigate whether
    a pure UIA implementation does not have a description field --
    due 2013-01-28 -- CLOSED

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

      [33] https://www.w3.org/WAI/PF/Group/track/actions/1152

    JS: that one is closedd.

issue-550

    issue-550?

    <trackbot> ISSUE-550 -- Come up with a date to stop editing
    UAIG in preparation for the next Last Call Draft -- closed

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

      [34] https://www.w3.org/WAI/PF/Group/track/issues/550

    JS: whoops, that should be 560

560

    issue-560?

    <trackbot> ISSUE-560 -- MSAA/IA2 spec. inconsistent with
    implementation in FF on aria-activedescendant -- open

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

      [35] https://www.w3.org/WAI/PF/Group/track/issues/560

    JS: that's a David issue, and he's not here.

    JS next is another FF question, skip it (issue-563).

issue-564

    issue-564?

    <trackbot> ISSUE-564 -- ROLE_SYSTEM_TEXT is not used
    role="heading" -- open

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

      [36] https://www.w3.org/WAI/PF/Group/track/issues/564

    CS: this is a case where FF is putting in strings where they
    should only put in enumerated types.

    JS: yes, david has another related issue, and this is going
    away.
    ... it's action-1175

    action-1175?

    <trackbot> ACTION-1175 -- David Bolter to status of
    ROLE_SYSTEM_TEXT in MSAA/IA2 column for role=heading -- due
    2013-03-18 -- OPEN

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

      [37] https://www.w3.org/WAI/PF/Group/track/actions/1175

    JS: linking action 1175 to the issue to keep track of the work.

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> [38]https://www.w3.org/WAI/PF/Group/track/issues/566

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

    JS: your table for action-1200 will fix this.
    ... and that action already associated with the issue.
    ... there is an action on James Craig to change the spec for
    some of these,

    CS: Check with him about that on the mon call.

    JS: yes, good idea.

issue-570

    issue-570?

    <trackbot> ISSUE-570 -- Investigate if this UAIG requirement is
    incompatible with AX API. #keyboard-focus_aria-activedescendant
    "Do not expose the focused state in the accessibility API for
    any element when it has DOM focus and also has
    aria-activedescendant which points to a va -- open

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

      [39] https://www.w3.org/WAI/PF/Group/track/issues/570

    JS: looks like an AXApi issue.

    CS: talk to James about this on Mon.
    ... our position is to close this. Do not want to open this can
    of worms again.
    ... postpone to aria 2.0, perhaps.

issue-582

    issue-582?

    <trackbot> ISSUE-582 -- We don't have an explicit mapping, for
    each platform, for the focusable state in the UAIG -- open

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

      [40] https://www.w3.org/WAI/PF/Group/track/issues/582

    [41]http://www.w3.org/WAI/PF/aria-implementation/#focus_state_e
    vent_table

      [41] http://www.w3.org/WAI/PF/aria-implementation/#focus_state_event_table

    JS: James Craig suggested this is what rich was looking for.

    CS: works for me.

    JS: so, I'll point this out on Mon to, and see if we can close
    it.

583

    Issue-583?

    <trackbot> ISSUE-583 -- Elements that are descendants of an
    element having aria-activedescendant should not all be
    focusable -- open

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

      [42] https://www.w3.org/WAI/PF/Group/track/issues/583

    JS: David had a suggestion — his action-1222

    action-1222?

    <trackbot> ACTION-1222 -- David Bolter to look into ISSUE-583,
    and think about section 4.3, step 4A to see if that answers the
    question. -- due 2013-05-16 -- OPEN

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

      [43] https://www.w3.org/WAI/PF/Group/track/actions/1222

    CS: I think we should postpone this.

    JS: Aria 1.1 or 2.0?

    CS: 2.0. I could accept 1.1., but I think we should push this
    out to 2.0 since how OSes handle focus is revved much slower.
    ... the core issue is that all issue should be postponed to 2.0
    unless there is a real good reason to change things at this
    stage.
    ... the bar is very high now.

issue-584

    issue-584?

    <trackbot> ISSUE-584 -- Firefox has introduce a role mapping of
    grouping for rowgroup (should this be consistent across
    platforms) -- open

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

      [44] https://www.w3.org/WAI/PF/Group/track/issues/584

    CS: we shouldn't make the change, since this is testing
    implementabiity, and I think these tests have passed in older
    browsers.

    JS: notes that this doesn't affect the UIA implementations.
    Nor, probably, the Ax API implementation.

    CS: so, I vote for aria 1.1.

Summary of Action Items

    [End of minutes]
      __________________________________________________________


     Minutes formatted by David Booth's [45]scribe.perl version
     1.138 ([46]CVS log)
     $Date: 2013-05-30 18:02:02 $
      __________________________________________________________

-- 
;;;;joseph.


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

Received on Thursday, 30 May 2013 18:10:54 UTC