Meeting minutes
<joanie> agenda: this
<joanie> agenda: be done
[New Issue Triage](https://bit.ly/3gDpQHj)
joanie: No new items
joanie: No new PRs
joanie: IIRC AccName mega meeting next week
jcraig: I am available for next week
Bryan: I am available.
[Meaty topic for next week](https://bit.ly/2RZHxIV)
[When is hidden content taken into calculation of name and description?](https://github.com/w3c/accname/issues/57)
joanie: people please chime in on issue #57
re: labelledy in unrendered/hidden spec, spec says only the specific node should be exposed. Not hidden/unrendeded child nodes.
Cyns also commented
joanie: jcraig said this was on purpose based on prior conversations
jcraig: I recall having this conversation with Aaron and others, maybe you Joanie. I don't know if there was written record of the conversation.
jcraig: We talked about the purposeful inclusion and accidental inclusion of things which are unrendered.
jcraig: Most of the time, I think it was an accidental inclusion.
jcraig: I remember a dialog that was marked as aria-hidden, but there were some unrendered child nodes. And we couldn't figure out how to expose some, but not others.
jcraig: The safest thing to do seemed to be to only expose the hidden container.
jcraig: I haven't read Cynthia's comments last week.
jcraig: I will do so later.
<jcraig> joanie: ok so please read and comment... need consensus between the group and implementors
[onboarding update?](https://github.com/w3c/aria/issues/1401)
joanie: any onboarding updates?
[TPAC 2021](https://github.com/w3c/aria/issues/1482)
joanie: jamesn has been managing.. should we meet and with whom?
jcraig: I don't see a need to meet as our group wince we're meeting regularly remotely anyway
jcraig: but if there is an item we should get on another group's agenda, some ARIA members could attend that.
joanie: agree that the main benefit is same time zone and physical location, so no pressing need for ARIA WG to meet at TPAC 2021. Deep dive has taken the place of some of that need… can invite people as needed
[Attribute with natural language but no language meta data](https://github.com/w3c/aria/issues/1365)
jcraig: Bert Bos, one of the founders of CSS WG, has pointed out that aria-valuetext is localizable user-presented string. But because it is an attribute, there is no way to explicitly set the language apart from setting it on the element itself.
jcraig: I think the issue resolution could be the following: 1) Do nothing and close the issue. You can use lang attribute on the node. Or 2) specifically mention that in the ARIA spec in the translatable states and properties section.
jcraig: I think it should defer to the host language.
jcraig: I am happy to do either. I was intending to do a pull request.
jcraig: If we don't think we need it, we can close the issue without it.
joanie: if someone has a valid point (which Bert does here), I'd prefer to make the clarification change in the Translatable attributes section
<joanie> https://
joanie: please use remaining time to review and comment issue 57 https://
adjourned