RE: Draft #2 Msg to WHAT

Hi all,

My only proposed changes would be from "non mutually" to "non-mutually" (with a hyphen) and "comprehendible" to "comprehensible" in Note 2. I would also remove the comma after the word "multiple" in Note 2.

My proposed changes would read:

"...language using an industry-accepted index value to identify the user's understood AAC symbol, as there are multiple non-mutually comprehensible symbol sets in use."

These are minor at best so if you don't agree Janina then feel free to ignore.

Thanks for your work on this!
--Mike

-----Original Message-----
From: Janina Sajka <janina@rednote.net> 
Sent: Monday, November 7, 2022 8:17 PM
To: Adapt tf <public-adapt@w3.org>
Subject: Draft #2 Msg to WHAT

CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.


Colleagues:

Below the changes we discussed during our teleconference today. If I've missed any, please advise by COB Tuesday!

<begin github issue>

Colleagues:

The Accessible Platform Architectures (APA) Working Group of the W3C hereby formally requests "adapt-" be designated a reserved prefix in HTML 5. This request follows our in-person discussions during the W3C TPAC recently concluded in Vancouver and logged here:

https://www.w3.org/2022/09/13-apa-minutes.html#t03

In response to our TPAC conversation, the following W3C issue indicates WHAT's research has indicated the "adapt-" prefix should be web
compatible:

https://github.com/w3c/adapt/issues/222

NOTES:

1.)     As recommended during our TPAC conversation, the W3C WAI-Adapt Symbols Module forthcoming Candidate Recommendation draft
will utilize "adapt-". The current draft can be viewed here:

https://w3c.github.io/adapt/symbols/

2.)     The above specification relies normatively on a forthcoming W3C
Registry specification which will publish shortly as a W3C First Public Working Draft (FPWD). The registry specification provides a mapping between thousands of concepts expressed in common written language using an industry-accepted index value to identify the user's understood AAC symbol, as there are multiple, non mutually comprehendable symbol sets in use.

https://w3c.github.io/adapt-registry/

For the very first time in web technology,  these two specifications will together provide content creators a single, internationally-supported  numeric attribute value which user agents can then use to provide an individual user their preferred AAC symbolic representation of that concept.


--

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures     http://www.w3.org/wai/apa

Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/

Received on Tuesday, 8 November 2022 11:26:50 UTC