Meeting minutes
scribe Jory
[New Issue Triage](https://bit.ly/aria-issues-aug19)
<joanie> audio fail
James: for issue 1 we need to pull aria-dsecription out of CR for 1.2... agreed?
Issue: 1598 nater in agenda
<trackbot> Created ISSUE-1056 - 1598 nater in agenda. Please complete additional details at <https://
reflecting element references should be a 1.3 milestone, assigned to CYNS
[New PR Triage](https://bit.ly/aria-pr-aug19)
PR 140 in AccName, needs Brain and Matt will review together
PR 1595 James will review
[Meaty Topic Meeting Reminders](https://www.w3.org/groups/wg/aria/calendar)
Layout Grids is Meaty next week, then alertdialog the following week
[Meaty topics for future weeks](https://bit.ly/aria-meaty-topic-candidates)
[Updating ARIA 1.2 due to IDL implementations (exit and re-enter CR?)](https://github.com/w3c/aria/issues/1598)
joanie: if we can put the spec BACK TO nullable DOMstring we have 3 implementations, if not we are back to 0
joanie: whould we pull the 1.2 CR, fix it, then put it back up?
james: why was it changed in the first place?
cyns: here was feedback that in #1058
correction: there was feedback in 1058 that prompted the change. AOM working group noted that there have been IDL changes that need to taken into account
james: let's make sure we understand the reason for the change before we revert it
cyns: let's get feedback from jamesc
james: let's do a draft PR for this change
cyns: will do a PR for next week
joanie: we also need to change the narrative and normative text explaining the validation and handling of an absent value
joanie: there may be role-by-role differences for what the default value should be
jamesn: please set implementers as reviewers of the draft PR
cyns: do we have tests for this yet?
joanie and syn will try to find those tests
correction: syn = cyns
jamesn: will need a CFC if we want to enter a new CR
valerie: I think all the tests are written but there may be open PRs to be review
jamesn: happy to help with reviews
joanie: a good next step would be to test the new w3c validator
jamesn: IBM has one too (that may be OSS)
jamesn: does anyone know of another agent we can file issues against? It would be good to have a second one. W3 validator?
valerie: not sure if that one does aria 1.2 validation
jamesn: not every Author MUST statement is going to be machine checkable, but we should do the best we can.
jamesn: maybe the W3C one is not the best candidate
<pkra> https://
jamesn: (looking at the repo) they do have some ARIA validation in here
validator repo: https://
[Prohibit presentation / none on where it causes conflict resolution](https://github.com/w3c/aria/pull/1494)
jamesn: this PR needs some improvement, anyone want to take this?