Meeting minutes
[New Issue Triage](https://bit.ly/3ic5ZBJ)
<Jory> Issue #1493 set for 1.3
<Jory> Joanie will be assigned
[New PR Triage](https://bit.ly/3g3A6IO)
<Jory> jamesn: Issue 1494 may need wider discussion
<Jory> jamesn: we need to identify ways to tackle, 1) Add to prohibited roles 2) Change inheritance model 3) Add a normative statement (current PR approach)
<Jory> jamesn: requests that people comment in 1494 to indicate their preferred direction
<Jory> jamesn: will create a comment for each proposal to be voted upon
[Meaty topic for next week](https://bit.ly/3uJLeQn)
<Jory> No deep dive next week
Summer Schedule?
<Jory> jamesn: will be out for parts of the summer
[2C "where the user can adjust the embedded control's value" is misleading](https://github.com/w3c/accname/issues/106)
<Jory> msumner: wanted to get clarification, should the value be used instead of label
<Jory> msumner: should we remove ability to adjust embedded control value or add a note to except readonly
<Jory> jamesn: unless this list is not exhaustive, why do we need a change
<Jory> jcraig: there are examples where there is a list of radios where an option needs a secondary input, e.g. a quantity
<Jory> jamesn: feels that use is covered
<Jory> jamesn: votes we drop it, joanie agrees
<Jory> jcraig: I agree
<Jory> joanie: instead of dropping should we come up with a phrase that means has value
<Jory> msumner: will open a PR
[Trim whitespace from computed accessible name/description](https://github.com/w3c/accname/issues/95)
<Jory> msumner: thinks we should trim whitespace, there are quirks where not doing that breaks stuff. In FF spaces in options have caused an issue
<Jory> jamesn: do we mean at the end of the calculation or during it?
<Jory> msumner: what to implementers think?
<Jory> sarah_higley: would advocate for at the end
<Jory> jcraig: there was some discussion about collapsing multiple whitespace.. is this trimming at the end or ANY whitespace?
<Jory> jcraig: we need to be careful about inadvertently adding whitespace that the author did not intend
<Jory> joanie: thinks the example of starting and ending with a space is sub-optimal authoring, but we should not trim
<Jory> msumner: the spaces may be unintentional, e.g. a side-effect of a CMS
<Jory> jamesn: there are 9 open acc name whitespace issues, this would be the 10th
<Jory> msumner: will look at this set of issues and categorize them
[Update to Condition for step 2C](https://github.com/w3c/accname/pull/90)
Action: MichaelC to review why PR previews not working
<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.
<Jory> jamesn: purpose of this unclear
Action: Aaron Leventhal to review #90
<trackbot> Error creating an ACTION: could not connect to Tracker. Please mail <sysreq@w3.org> with details about what happened.
<Jory> joanie: will take a look too
[Support aria-description](https://github.com/w3c/accname/pull/69)
<Jory> jamesn: this will need to be a 1.3 branch
<Jory> msumner: wants to confirm that this is the approach we want to take before moving forward
<Jory> siri: why can this be on any element?
<Jory> Aaron: the thought was that it could be useful on anything and we want parity with describedby
<Jory> jamesn: we've merged HTML AAM into acc name
<Jory> Aaron: yes because its useful to me as a consumer for browser implementation, I think this is more practical
<Jory> Aaron: I'd put that in too, tables are easier than prose
<Jory> jamesn: if we do this we need to do it for name as well, not just description
<Jory> joanie: do we own SVG AAM?
<Jory> MichaelC: We can talk to SVG group, they may be open to handing it over
<Jory> jamesm: msumner may need to coordinate with Scott and Steve
<Jory> msumner: I may need to do a PR because some steps have been rearranged
[When is hidden content taken into calculation of name and description?](https://github.com/w3c/accname/issues/57)
<jamesn> https://
<Jory> jamesn: please take a look at this comment
<joanie> https://
<Jory> joanie: we need to decide how the spec interprests author intent where there are hidden descendants of an element targeted by a labelledby idref
<Jory> jcraig: I think that the child span if hidden, should not be included for fear of inadvertently exposing too much content in the case of massive author error
<Jory> jamesn: please comment on this issue