- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Thu, 20 Jun 2013 14:16:22 -0400
- To: "wai-xtech@w3.org >> \"wai-xtech@w3.org\"" <wai-xtech@w3.org>
Link: http://www.w3.org/2013/06/20-aapi-minutes.html
Plain text version follows:
[1]W3C
[1] http://www.w3.org/
- DRAFT -
Protocols and Formats Working Group Teleconference
20 Jun 2013
[2]Agenda
[2] http://lists.w3.org/Archives/Public/wai-xtech/2013Jun/0004.html
See also: [3]IRC log
[3] http://www.w3.org/2013/06/20-aapi-irc
Attendees
Present
Joseph_Scheuhammer, David_Bolter
Regrets
Cynthia_Shelly
Chair
Joseph_Scheuhammer
Scribe
clown
Contents
* [4]Topics
1. [5]ACTION-1200
2. [6]ACTION-1221
3. [7]ACTION-1222
* [8]Summary of Action Items
__________________________________________________________
<trackbot> Date: 20 June 2013
<scribe> scribenick: clown
RRSAgent: make mintues
RRSAgent: make minutes
GVoice is Joseph_Scheuhammer
RRSAgent: make minutes
<scribe> agenda:
[9]http://lists.w3.org/Archives/Public/wai-xtech/2013Jun/0004.h
tml
[9] http://lists.w3.org/Archives/Public/wai-xtech/2013Jun/0004.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-06-13 -- OPEN
<trackbot>
[10]https://www.w3.org/WAI/PF/Group/track/actions/1200
[10] https://www.w3.org/WAI/PF/Group/track/actions/1200
JS: regarding author errors.
[11]http://www.w3.org/WAI/PF/aria-implementation/#document-hand
ling_author-errors
[11] http://www.w3.org/WAI/PF/aria-implementation/#document-handling_author-errors
JS: Cynthia was going to add columns and value for each a11y
platform.
... Cynthia's proposall is here on wai-xtech:
[12]http://lists.w3.org/Archives/Public/wai-xtech/2013Jun/0002.
html
... I suggested a compromise — to link from the error table to
the roles table.
... But the more I think about it, the more I want to just fill
in the error table.
... there is the danger of keeping the two tables in sync.
[12] http://lists.w3.org/Archives/Public/wai-xtech/2013Jun/0002.html
DB: yes, that's true.
JS: so, I will take a stab at filling in the error table?
DB: Sure, we can see how it looks, and if necessary, move it to
the roles table later, if that looks better.
<davidb> [13]https://github.com/eeejay/specular
[13] https://github.com/eeejay/specular
<davidb> [14]https://github.com/askalski/mats
[14] https://github.com/askalski/mats
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>
[15]https://www.w3.org/WAI/PF/Group/track/actions/1221
[15] https://www.w3.org/WAI/PF/Group/track/actions/1221
JS: see also issue-559
ISSUE-559?
<trackbot> ISSUE-559 -- Missing member of relationships -- open
<trackbot> [16]https://www.w3.org/WAI/PF/Group/track/issues/559
[16] https://www.w3.org/WAI/PF/Group/track/issues/559
look here, but scroll up a bit:
[17]http://www.w3.org/WAI/PF/aria-implementation/#mapping_event
s_selection
[17] http://www.w3.org/WAI/PF/aria-implementation/#mapping_events_selection
Look for: Exposing additional useful information about the
context of the change
JS: the easy solution is to add: In ATK/AT-SPI *and IA2*.
... previously we though to remove this, but reference the
states and properties mapping table.
... but that doesn't work because this is about events, and the
mapping table is (mostly) about data.
DB: so, how about just adding IA2?
JS: works for me.
... just need to confirm that it works that way for IA2.
DB: I believe it does.
resolved: Joseph to add "and MSAA+IA2" to the section on
context changes where it already discusses ATK/AT-SPI (towards
the end of section 5.8.2).
<davidb> so when are all the APIs going to converge :)
<davidb> (DB and JS discuss ARIA's scope)
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>
[18]https://www.w3.org/WAI/PF/Group/track/actions/1222
[18] https://www.w3.org/WAI/PF/Group/track/actions/1222
issue-583?
<trackbot> ISSUE-583 -- Elements that are descendants of an
element having aria-activedescendant should not all be
focusable -- open
<trackbot> [19]https://www.w3.org/WAI/PF/Group/track/issues/583
[19] https://www.w3.org/WAI/PF/Group/track/issues/583
DB: I *think* 4A. in section 4.3 is still fragile — or I'm
unsure.
JS: the problem is that not all descendants of a container that
has a aria-activedescendant are intended to be "focusable".
... Rich is asking for another criterion so that only the
intended focusable descendants are marked focusable.
... He suggests that the descendant must have an ID attribute.
DB: but that won't always work since ID might be used for, say,
styling.
JS: right
Summary of Action Items
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [20]scribe.perl version
1.138 ([21]CVS log)
$Date: 2013-06-20 18:09:45 $
__________________________________________________________
[20] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[21] 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, 20 June 2013 18:16:50 UTC