Introductory Personalization Video: https://ln.sync.com/dl/04f8c9330/6wk4ff4v-77wd78s5-ge6wc24s-vm3iwxwm (no captions, yet)

We have one module (from what is expected to be a short series of
probably 3 modules) just about ready for CR. The specification describes an ARIA-type semantic overlay
that will facilitate web use by people with various cognitive and
learning disabilities not previously served directly by assistive
technology.

One key user group who will benefit from this overlay markup is persons
who don't do well with written text but rather rely on a long
established communication approach known in accessibility as
"Augmentative and alternative communication (AAC)." AAC users tend to be
schooled from their earliest years to a particular, proprietary AAC
vocabulary. AAC users in a different educational jurisdiction will have
been schooled to a different vocabulary. Unfortunately, these
vocabularies are mutually unintelligible. Among other things it does,
our specification will facilitate automated translation among
them--greatly expanding communication for quite a few people who could
not communicate with each other before.

What we need from WHAT: We need an reserved attribute prefix to replace
data- which we used during development and
prototype implementation per Sec. 3.2.6.6 of the HTML specification. We
believe this is a simple request, but we want to address any concerns up
front.

We're going to have to get back to you on this. It's looking like the relevant parties can't make this timing.

The APA currently scheduled meetings are listed here: https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2020#Agenda