Meeting minutes
<jamesn> - Also how to get DPUB-AAM ready?
issue 1515 - mark as 1.3
mark issue 1513 as aria 1.4
mark issue 1511 as a won't fix
Action: jamesn mark 1511 as won't fix
<trackbot> Created ACTION-2158 - Mark 1511 as won't fix [on James Nurthen - due 2021-07-29].
cyns: if not finishing hidden elements in accName, then next deep dive?
jamesn: hidden or something else?
jamesn: have one next week, but not for 2 weeks after that
jamesn: due to implementors on vacation, no deep dive for next 3 weeks
DPUB-ARIA 1.1 - Publish FPWD CFC
<jamesn> https://
jamesn: first public wd ready for fist FPWD.
<jamesn> https://
MattGarrish: ready for review. have some new things we're adding, but need to do some cleanup.
jamesn: can do a cfc out for this. maybe approval by next week.
Action: jamesn to create cfc
<trackbot> Created ACTION-2159 - Create cfc [on James Nurthen - due 2021-07-29].
jamesn: but what to do about dpub aam?
MattGarrish: shouldn't be a lot of changes for 1.1 AAM. hopefully shouldn't be much to it.
jamesn: page footer and page header don't appear to have AXAPI
jamesn: just need to get the mac mapping. Matt try to contact james craig to push this forward.
joanie: i would suggest we file issues against the UAs we want to implement
[Why is outline depth involved in the level exposed for h1-h6?](https://github.com/w3c/html-aam/issues/336)
Scott_O: this issue is about the outline algorithm and if we should implement
cyns: browsers that change levels against expressed intent is usually not good
jamesn: kind of agree except in certain cases - consumed content from other places
joanie: - gives example about how google news uses h3s, but if implementing this it could undo this known heading level
mKing: unless author say do this for "this" part of the page, this seems like a bad idea
BryanG: i'm not in favor of it myself. too many ways for this to break.
consensus from group is to not implement outline algorithm
Scott_O: I will remove mention of outline depth from HTML AAM
[When is hidden content taken into calculation of name and description?](https://github.com/w3c/accname/issues/57)
jamesn: no progress on this issue in the last week, but we need to make progress
cyns: the use case for the double hidden was about 'super tooltips'. which seem these should be aria details instead of aria-describedby. maybe we can punt on this?
jamnes: 2 problems. 1. aria-details is not well supported today. 2. legacy content could cause breakage
cyns: i'm not sure if legacy 'super tooltips' were ever really accessible
jamesn: i'm not sure i've ever seen our use case in the wild where we'd need to worry about the hidden content within a tooltip
cyns: i think i was the one that wanted this in the first place. but, i'm no longer worried about this use case
cyns: i expect that the pattern i was worried about at the time that this would have solved for is no longer as much of an issue
jamesn: we need to better indicate what authors can expect
jamesn: if we don't care about double hidden stuff, will this work?
<jamesn> "This step can produce surprising results, as when the innerText getter is invoked on an element not being rendered, its text contents are returned, but when accessed on an element that is being rendered, all of its children that are not being rendered have their text contents ignored."
jamesn: if referencing an element that was visible vs when it becomes hidden, you can get different results
jamesn: could we get a draft pull request with spec text to review this in detail more easily?
BryanG: I can make a draft
jamesn: then we can get implementors to review the draft to see if anything might break
rrsh, make minutes
rrsagen, make minutes