W3C home > Mailing lists > Public > public-adapt@w3.org > November 2022

RE: Draft #2 Msg to WHAT

From: Mike Beganyi <mbeganyi@tpgi.com>
Date: Tue, 8 Nov 2022 11:26:16 +0000
To: Adapt tf <public-adapt@w3.org>
Message-ID: <BY5PR20MB30127A8FAE1661765A42D09AAD3F9@BY5PR20MB3012.namprd20.prod.outlook.com>
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!

-----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.


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

<begin github issue>


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:


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



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:


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.


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
Received on Tuesday, 8 November 2022 11:26:50 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 8 November 2022 11:26:51 UTC