<joanie> agenda this
<joanie> agenda: be done
<scribe> scribe: HarrisSchneiderman
jd: TPAC is here - James is managing the agenda, if anyone has concerns, please just comment. Its your last chance to purpose topics
joanie: nothing has changed since last week
https://github.com/w3c/aria/pull/820
<joanie> No platform will be dropped out of the specification without prior consultation with that platform's owners. Every effort will be made to take member organizations' schedules into account and to ensure all platforms are included.
joanie: everyone seems to be able
to "live with" the above wording. This hopefully addresses 1 of
the 2 concerns
... we've reached out to the party who brought up the other
concern
MichaelC: We've given a timeline. Realistically we may have to discuss at TPAC
<joanie> https://github.com/w3c/core-aam/issues/26
joanie: The first one is a 1.2 one (issue 26) - marking it as such. The reason is based on new workflow, it can go into editor spec draft but it can't go into working draft (must file bugs/get agreement)
<joanie> https://github.com/w3c/core-aam/issues/24
joanie: The 2nd one (issue 24) is going to be 1.2
carmacleod: its just a matter of wording - more understood to say the "element referenced by aria-controls"
<joanie> https://github.com/w3c/accname/issues/32
joanie: wilco questioned this
test case. Steve Faulkner - "The AAM documents what is in
browsers", Joanie suggested that we need to figure out what
screen readers should be presenting.
... If we can get everyone on the same page - thats what should
go into the spec and thats what will get us at
interoperability
... tldr; its a 1.2 issue
<joanie> https://github.com/w3c/accname/issues/31
Joanie: still confusion surrounding this - which is why i think it should be a 1.2 issue
<joanie> https://github.com/w3c/aria/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+created%3A%3E%3D2018-09-27+
<joanie> https://github.com/w3c/aria/issues/819
Joanie: 819 has been marked as
1.2
... role=presentation on a table. What about tags within table
(td, th etc)
<joanie> https://github.com/w3c/aria/issues/821
<joanie> role="timer" has implicit aria-live=off, consider options for interval announcements
Joanie: new properties, if not
critical, shouldn't go into role parity
... its not 1.2, lets reconsider it during 1.3 cycle. If we
can't then it'll be 1.4
Joanie: google reviewed patches to fix issues in AccName in a SUPER timely manner. Mad props to google! Gave great feedback
MichaelC: Good things might not happen as soon as we hope...Technically we were a day short which means we could be blocked from publishing tuesday.
Michael: Hopefully there aren't any questions - its simple. Worst case scenario we have to publish a week after TPAC when we publish the 1.2 working draft.
<joanie> https://w3c.github.io/test-results/accname/
Joanie: Theres nothing platform-y
about the name stuff (for the most part). Each test case has 2
passes for each UA. Wanted to have all anticipated questions
asked
... It was important to AccName out the door while we still had
a charter
Joanie: we need authoring
guidance in place
... I think we'll be able to pull it off
<carmacleod> https://github.com/w3c/aria/issues/699
carmacleod: I just added a
comment very recently...Without testing ALL the browsers
(safari questions and linux questions), I think I see that div
always has a role (tends to be section sometimes group). Span
is never mapped, the text content is taken out of the span an
thrown into parent (in a11y trees)
... I'm wondering if it just makes sense to map div to section
or maybe even generic. What should we map span to?
joanie: there are times that
spans are exposed (if they're focusable for example). So since
they have to exist in the tree, we need a role that makes
sense
... repeat the manual tests with <span tabindex=0 /> and
see what we get
<carmacleod> https://w3c.github.io/html-aam/#el-div
joanie: dt = term role
<carmacleod> https://w3c.github.io/html-aam/#el-span
joanie: div will change from no
corresponding role to whatever we decide to call this "generic"
role
... for span change to "not exposed, but if it has to be
exposed, its the 'generic' role". Span will often not be
mapped
... making a div map to section has been proposed
before...consensus was "no, because...(can't remember what the
point was)"
<joanie> https://github.com/w3c/aria/wiki/Plans-regarding-role-parity
carmacleod: sticking to the previously discussed mapping to generic?
joanie: yea
carmacleod: span is not mapped but if it has semantic content (like tabindex), its 'generic'
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/jm/jd/ Succeeded: s/jonie/joanie/ Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Default Present: Joanmarie_Diggs, HarrisSchneiderman, MichaelC, MarkMcCarthy, janina, melanierichards, carmacleod, CurtBellew Present: Joanmarie_Diggs HarrisSchneiderman MichaelC MarkMcCarthy janina melanierichards carmacleod CurtBellew Regrets: James_Nurthen Found Scribe: HarrisSchneiderman Inferring ScribeNick: HarrisSchneiderman Found Date: 11 Oct 2018 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]