Meeting minutes
[New Issue Triage](https://bit.ly/3uMyTv9)
https://
jamesn: I recommend to creat PR to remove
Melanie will create the pr
intro - Cynthia from Google
going around for intro
v
https://
jn: Not enough information yet
scott: It belongs HTML-AAM
… we can push over html-aam and let the discussion happen.
brayn: There has to be acc name some day
https://
melanie: it is straight forward and we can move to next milestone
[New PR Triage](https://bit.ly/3g9namu)
#1454 is being worked on.
#122 was reviewed by multiple members
jamescraig will review the issue.
also please help to reach out to Mozila, James Teh
[Meaty topic for next week](https://bit.ly/2QqpnyL)
stefann: added deep dive issue
jn: please add deep dive label to the issue, Stefa
the role description discussion by Stefan will be three weeks time frame
<jcraig> May 6th
data visualization will be next topic for deep dive session
[Consider deleting aria-dropeffect and aria-grabbed](https://github.com/w3c/aria/issues/1447)
aria channel for deep dive is #aria-dive
jn: waiting for Bryan to join the discussion since brayn implemented this effectively
<msumner> I have a codepen demo of this: https://
brayn: talking about list box behavior example
jc: "support" is loaded term here
drag is more of both select and drop, not one action
jc: the reason for deprecation was that there are not enough support
… aria grabbed with keyboard command can be working but the test work cannot be generalized and universal
jn: we used to use live region for the drag...
jc: The path may be to fix HTML drag and drop. Once we're able to get enough out of that API to make it accessible, we'll be better informed to redesign any necessary ARIA API.
jn: do not hear no great desire to drop it.
Car: I can close it for now/
jn: Carolyn will add comment on what the future plan is when she close the issue
[Suggested simplification](https://github.com/w3c/accname/issues/96)
https://
jn: We need review for the issue
group is talking about the way to reference each spec flexibly.
options are adding editor's note, fixing the numbering and so on.
jn: one option will be name reference
jc: bulleted list of headings be helpful?
bryan: we can name it based on section is meant to be - each step after aria label and so on...
[Add role=image as synonym for role=img](https://github.com/w3c/aria/pull/1370)
scott: it is ready for the review and connected to the issue of role="none"
… curious about whether I need to add presentation to the table or revised the javascript
good first issue for JamesN
scott: two role definition can be within the sae heading, it would be great but it will break the spec.
jc: We might consider using rel=synonym (and suggest ReSpec or Bikeshed support it) and to link each other.
jn: we are moving out of Respec
… currently work on definition before the migration
jn: I can investigate the solution
scott: PR is ready for word smithing
jn: example is presentaion and none
… in which order do we link the synonym?
… none or presentation first?
jc: we can consider "backward (historical) compatibility" for the order
Cyn: should someone make a one up for the issue to witch them around?
jn: good idea
car: adding the depreciatation date will be helpful to users
… as the part of intent note.
<jamesn> fyi i have a branch for presentation and none https://
jc: there is a challenge for adding specific depreciate date due to specific work flow. - drag and drop example. but we can consider in the future.
… we can keep those info until we have fall back info.
scott: I createed the issue 1456 from this discussion
[1.3 triage](https://bit.ly/3wVub07)
#1203
jn: it is not feasible to implement within 1.3 timeline
… we move to 1.4
jn: I will go through and pull out of this extra labeling stuff.
#1219
https://
Name from author on column header & structural relationships
scott: I will look at this.
https://
jn: we can move this to 1.4
https://
Processing of the role attribute not clearly defined #1236
<jcraig> Am I correct in thinking image role hasn't yet landed in Editor's draft? I only see img. https://
<pkra> gotta run. see you next week.
james craig will review and add comments
https://
aria-hidden error case: remove attribute aria-hidden=true on elements that become focused, and any ancestor of the element that is currently focused. #1255
it will be assigned to Irfan
jc: can we potentailly point body type element, not html root element when Irfan works on the issue?
… the issue was that disallow are hidden are bascially ignore our hidden on the root element at some point in the past in webkit
… we have to make sure we only do it on the top level document.
scott: it is a good point. my only concern is that just making sure that we don't bascially say that nested documents can be set to already hidden equals true.
jn: that is interesting. I don't think it should be allowed on the body element itself.
jc: to your pint about nested documents, it is right as JamesN said in an iframe or something like a shadow root. Aria-hiden attribute can be used effectively in that case.
irfan: Scott, would you like to discuss that with me at some point of time?
Scott: yes.
persent+ Cynthia
present scottohara
rrsagents, make minutes