W3C

ARIA Editors

19 August 2022

Attendees

Present
James_Nurthen, Jemma_Ku, MCK, MichaelC, Valerie_Young
Regrets
Peter_Krautzberger
Chair
MichaelC
Scribe
MichaelC

Meeting minutes

Follow up on Evergreen questions

how does a reader know a spec is evergreen?

Respec working on addition to boilerplate

Status should have text, but not checked

https://w3c.github.io/tr-design/p2021mockup/cr-6.3.8.1.html mockup

Could make enhancement request to tr-design, respec

people need to know doc is evergreen so not mixed up with number versions

if we can document use cases, we can better prepare feedback

what do we do with spec versions after evergreen?

Can do indefinite CR without Rec snapshots, if we don't need AC endorsement

Spec will still have version in system (pub URI), but we don't have to put it in the title

Unversioned URI still exists, tied to a versioned URI, Core-aam will need update to 1.2 anyways

but we won´t refer to it as versions

we can enable auto publication after going to CR the first time

will need to work out a comfortable workflow for the living standards process

Updating workflow process for living standards

need a different workflow to approve AAM content that won´t be too much, but gets review

potentially different workflow for AAMs, specs, and guides

Testing check-in -- taken up

MichaelC has approve on wpt, but that seems outdated

Valerie and Joanie should be the reviewers instead

Jon won´t be able to help with IA2

Valerie has been looking in in the framework, may be able hodge podge something for 1.2

OpenUI liaising

deferred

Next meeting

<MichaelC> Next meeting: 2 Sept 2022

Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).