Re: Minutes: [aapi] UAI TF Meeting Tue Mar 04, 2014

This brings up one question regarding the proposal to expose focusable 
elements even when aria-hidden is true.

Would this be to expose a focusable element in the accessibility tree only 
when the element receives focus, or to expose all focusable elements 
regardless which one has focus?

I'd be much happier if it were the first and not the second, since 
aria-hidden is useful when conditionally hiding regions to simplify layout 
for AT users without having to distort the UI visually.




----- Original Message ----- 
From: "Joseph Scheuhammer" <clown@alum.mit.edu>
To: <wai-xtech@w3.org>
Sent: Tuesday, March 04, 2014 1:11 PM
Subject: Minutes: [aapi] UAI TF Meeting Tue Mar 04, 2014


> Link: http://www.w3.org/2014/03/04-aapi-minutes.html
>
> Text-only version follows:
>
>    [1]W3C
>
>       [1] http://www.w3.org/
>
>                                - DRAFT -
>
>            Protocols and Formats Working Group Teleconference
>                               04 Mar 2014
>
>    See also: [2]IRC log
>
>       [2] http://www.w3.org/2014/03/04-aapi-irc
>
> Attendees
>
>    Present
>           Joseph_Scheuhammer, David_Bolter, Bryan_Garaventa
>
>    Regrets
>           Joanie_Diggs, Cynthia_Shelley
>
>    Chair
>           Joseph_Scheuhammer
>
>    Scribe
>           davidb
>
> Contents
>
>      * [3]Topics
>          1. [4]Note that DST for Canada/US comes into effect by
>             next meeting (Mar 11).
>          2. [5]Progress on refactoring UAIG and starting on edits
>             for UAIG 1.1.
>          3. [6]Addition of table role(s) to ARIA 1.1.
>             ISSUE-423/ACTION-1395.
>          4. [7]ISSUE-481/ACTION-1368/ACTION-1369: (David, Cynthia)
>             aria-live removal events should/must happen before
>             object removal.
>          5. [8]ISSUE-441/ACTION-1372: (Cynthia) Test case for
>             incomplete use of aria-posinset/aria-setsize.
>          6. [9]ISSUE-618/ACTION-1371: (Cynthia) Investigate how IE
>             implements item de-selection in single selection
>             container.
>          7. [10]ISSUE-635/ACTION-1372: (Cynthia) Create test case
>             for rowgroup role.
>          8. [11]ISSUE-644: (All) Update ATK/AT-SPI mapping for
>             aria-hidden="true" to reflect elements should not be
>             exposed/mapped.
>          9. [12]1.1 ISSUES and ACTIONS: (All) Start with
>             ISSUE-540,
>             https://www.w3.org/WAI/PF/Group/track/products/23
>      * [13]Summary of Action Items
>      __________________________________________________________
>
>    <trackbot> Date: 04 March 2014
>
>    <clown> agenda: this
>
>    oh
>
>    <clown> zakaim, agenda?
>
>    <clown> scribenick: davidb
>
>    DB: hoping to move some of my items to email so that I don't
>    have to be an obstacle during my chaotic weeks
>
>    JS: this meeting is good for final resolution, do everything
>    else via email
>
> Note that DST for Canada/US comes into effect by next meeting (Mar
> 11).
>
> Progress on refactoring UAIG and starting on edits for UAIG 1.1.
>
>    JS: discussing documentation build system
>
>    JS explains it is getting simplified (post 1.0)
>
>    JS: will add corrected gnome mappings to 1.1 uaig soon
>
> Addition of table role(s) to ARIA 1.1. ISSUE-423/ACTION-1395.
>
>    JS: this is to bring DB up to speed
>    ... we concluded we would add a table role, primarily for non
>    html languages.
>    ... grid is considered interactive, table is a classic data
>    table, just structure.
>    ... table role added to 1.1, someone will look at sub elements
>    as well... TBD
>    ... so you can make a table in SVG
>
>    alex might say just mix in html
>
>    (group discussion of role hierarchy)
>
>    BG: I see people misusing grid.
>
>    <clown> action-1396?
>
>    <trackbot> action-1396 -- Joseph Scheuhammer to Modify uaig to
>    convey grid role in accessibility mappings, beyond table.
>    (atk/atspi/ ia2 xml-role=grid, macosx: roledescription: grid,
>    msaa/uiaexpress localizedcontroltype="grid"?) -- due 2014-03-10
>    -- OPEN
>
>    <trackbot>
>    [14]https://www.w3.org/WAI/PF/Group/track/actions/1396
>
>      [14] https://www.w3.org/WAI/PF/Group/track/actions/1396
>
>    JS: grid is currently mapped to table in all a11y APIs
>    ... where do we map table? (sic)
>
>    DB: hard not to map it to table
>
>    discussion of BSTR hack in light of xml-roles obj attr
>
>    DB: BSTR should be considered deprecated
>
>    discussion of who controls navigation for grid vs table
>
>    JS: (reads spec wording about grid edit-ability vs read
>    only-ness from spec)
>
>    DB: this smells fuzzy
>
>    JS: no black and white line between tables and grids
>    ... and what about selection
>
>    sounds like table could be treated like a grid with aria
>    readonly on the whole thing
>
>    <clown> <table role="log" ...>
>
>    (brief review of "addition of HTML role requirement mappings"
>    public thread)
>
>    DB: i never liked edge cases
>    ... conclusion - we need broader feedback
>
> ISSUE-481/ACTION-1368/ACTION-1369: (David, Cynthia) aria-live removal
> events should/must happen before object removal.
>
>    <clown> issue-481?
>
>    <trackbot> issue-481 -- aria-live removal events should or must
>    happen before object removal -- open
>
>    <trackbot> [15]https://www.w3.org/WAI/PF/Group/track/issues/481
>
>      [15] https://www.w3.org/WAI/PF/Group/track/issues/481
>
>    postpone to next week
>
> ISSUE-441/ACTION-1372: (Cynthia) Test case for incomplete use of
> aria-posinset/aria-setsize.
>
>    meeting shame!
>
> ISSUE-618/ACTION-1371: (Cynthia) Investigate how IE implements item
> de-selection in single selection container.
>
> ISSUE-635/ACTION-1372: (Cynthia) Create test case for rowgroup role.
>
>    <clown> cynthia not here, let's skip.
>
> ISSUE-644: (All) Update ATK/AT-SPI mapping for aria-hidden="true" to
> reflect elements should not be exposed/mapped.
>
>    <clown> issue-644?
>
>    <trackbot> issue-644 -- Update ATK/AT-SPI mapping for
>    aria-hidden="true" to reflect elements should not be
>    exposed/mapped -- open
>
>    <trackbot> [16]https://www.w3.org/WAI/PF/Group/track/issues/644
>
>      [16] https://www.w3.org/WAI/PF/Group/track/issues/644
>
>    <clown> "If the object is in the accessibility tree, map all
>    attributes as normal. In addition, expose object attribute
>    hidden:true."
>
>    <clown> "Element SHOULD NOT be exposed in a11y tree. If the
>    object is in the ….
>
>    <clown> AXAPI says: "Not exposed in AX API unless focused. If
>    focused, expose as normal."
>
>    DB: I'm probably ok with _SHOULD_ NOT but with a grunt
>
>    BG: could be bad to expose even the interactive elements, given
>    you want to prevent usage of the hidden tree
>
>    (group discussing aria-hidden yet again)
>
> 1.1 ISSUES and ACTIONS: (All) Start with ISSUE-540,
> [17]https://www.w3.org/WAI/PF/Group/track/products/23
>
>      [17] https://www.w3.org/WAI/PF/Group/track/products/23
>
>    <clown> end of the hour.
>
> Summary of Action Items
>
>    [End of minutes]
>      __________________________________________________________
>
>
>     Minutes formatted by David Booth's [18]scribe.perl version
>     1.138 ([19]CVS log)
>     $Date: 2014-03-04 21:08:04 $
>      __________________________________________________________
>
>      [18] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
>      [19] http://dev.w3.org/cvsweb/2002/scribe/
>      [22] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
>
> -- 
> ;;;;joseph.
>
>
> 'A: After all, it isn't rocket science.'
> 'K: Right. It's merely computer science.'
>              - J. D. Klaun -
>
>

Received on Tuesday, 4 March 2014 21:37:06 UTC