Meeting minutes
New Issue Triage
cynthia called in from phone
<arigilmore_> regrets D.A. Kahn
sorry Ari oops
jamesn: aria #1760 in 1.3
do we need to tell UA's how to resolve error
?
mostly for chrome
gone off spec for good reasons exposing some children that have presentational true on them
jamesC_: html buttons can take inputs
aaronlev: be loose in what you accept
browser should not truncate content
jamesn: need button group role
where outside is focusable
bryang:
please no
Bryan put anything in antything
a can of worms
bryan it won't work
jamesn: 1.3? authors must not do this
New PR Triage
Deep Dive planning
aaronlev: popup issue
how to map html popup
three values
opens auto, opens hover, manually opened by author
important grouping needs expression
aaronlev: ok to have minimal role
jamesn: is there an issue for this?
slightlyoff: make it an html aam issue
who do you think needs to be in the Deep dive?
scotto, aaronlev , jcraig and anyone who wants to
jcraig: in the next 3 weeks
<aaronlev> https://
<aaronlev> We need to map what is proposed in that open ui issue ^
jamesn: popoup deep dive in the next 3 weeks?
slightlyoff: should work
jcraig: should work
jamesn: modals? discuss in the next three weeks
Bryan, next week come? Yes
Bryan can come next Thursday
jamesn: should we do modals as well in the next 3 weeks?
next week
Does aria-hidden obey DOM or AX tree ancestors?
aaronlev: we agreed it is resolved
aaronlev: aria owns is ignored if source is aria hidden
aaronlev: wrote up how chrome implements aria owns
cycles and things that shouldn't exist in tree
image maps cause problems
can share the link to that
<aaronlev> https://
<aaronlev> aria-owns implementation in Chrome ^
jcraig: also linked to webkit bug
jcraig: something worth doing in aria repo as well
jcraig: wiki can be moved to aria resource
jcraig: keep a live separate informative doc
jamesn: could be more evergreen
aaronlev: linked to chrome tests
useful to run just to see if they don't crash
jamesn: make sure we have concensus
1.3 triage
103 issues
need prioritization
punt some
reduce/prioritize somehow
must vs. nice to have
currently 6 blocking issues
1365 need to resolve in next version
jamesn: #1159
assinged to Sina
spectranaut: took 1159
aaronlev: issues need grouping
jamesn: haven't had a chance
spectranaut: people can look at all the issues that are assigned to them
we can look together at it
jamesn: 1.3 has braille and annotation stuff
jamesn: time to move on
aaronlev: some can be punted to 1.4
aaronlev: do a bulk edit lol
aaronlev: need project manager
spectranaut: me and jamesn
spectranaut: go to ARIA 1.3 project
go to the board
ARIA 1.3
spectranaut: what to we think of the idea of deciding on what is important on 1.3?
do we have any document that defines high priority
caller, likes making it very easy
jamesn: proirities. low medium
use labels
aaronlev: blocking, clarification
knitpicks
jamesn: what about a feature to support something in openUI
aaronlev: openUI issues are AAM issues
otherwise the trains leaves the station
<aaronlev> high author impact
jamesn: external dependencies are different
jamesn: clarify tagging strategy
aaronlev: we have "deepdive"
<aaronlev> f2f candidate
jamesn: F2F candidate
meet with APA
meeting room at a bar?
jamesn: better use present labels?
jamesn: lets come up with something
low, medium, high
than they can triage
spectranaut: thats one idea
spectranaut: aarons idea is different
grouping
jamesn: need new tags
spectranaut: call it 'prioritize:'
jamesn: reuse, we have to make sure as a group we have concensus
spectranaut: have everyone use a tag like '1.3:'
jamesn: lets go through some issues
jamesn: #1760 restrict aria-owns
<aaronlev> so far we have: blocking, clarification, nitpick, open-ui-coordination, deepdive, f2f-candidate, high-author-impact, high-user-impact
labels, 1.3-Clarification
jamesn: I think its clarification
aaronlev: added blocking, clarification, nitpick, open-ui-coordination, deepdive, f2f-candidate, high-author-impact, high-user-impact
<aaronlev> editorial, good-first-issue
jamesn: we don't need release number
<aaronlev> get rid of clarification, we can use editorial
spectranaut: editorial
no tests no core-aam
editorial doesn't change anything
clarification is more complicated then editorial
#1758 is clarification
jamesn: 1758 is complicated
#1732 suffix elements for IDL attributes
jcraig: need a solid day for this
jcraig: on his list
jamesn: I did a PR for it
#1680
clarification
jamesn: everything is clarification
jamesn: is it useful to label as clarification?
spectranaut: if its clarification individuals can punt to 1.4?
jamesn: clarification (high medium low)?
aaronlev: we already have good stuff in 1.3
if it has a pr we should finish it
spectranaut: we still want to tag the issues
some won't be clarification
if you can fix quickly created a PR
spectranaut: label as goodfirstbug
when possible
clarification and nitpick, multiple lables
spend last ten minutes
propose to take issues
aaronlev: what about AAM issues?
jamesn: you, cythia, joannie and valerie
scott has all html-aam ones
start by triaging the ARIA ones
most don't know whats going on in AAM
jcraig:
issue had a PR then was reopened, #1365
should I created a new issue?
jamesn: yes created a new issue
createdd 1761
spectranaut: examples of high user impact or high author impact?
aaronlev: whether a property should be now supported on a given role
aaronlev: role-dialog aria-modal=true, focus ...
chromium bug
#1487
jamesn: 1487 high user impact
aaronlev: need a vacation again lol