- From: Lionel Wolberger <lionel@userway.org>
- Date: Mon, 7 Nov 2022 23:55:10 +0200
- To: Adapt tf <public-adapt@w3.org>
- Cc: Janina Sajka <janina@rednote.net>
- Message-ID: <CAHOHNHe309DrLC3=U19uR57TQOqbVbFk-4E2MzOUF43BCDjw4A@mail.gmail.com>
+1 -- ok with me! Thanks, Janina [image: Lionel Wolberger] <https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger> Lionel Wolberger COO, UserWay Inc. [image: UserWay.org] <https://userway.org/?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger> [image: Phone Icon] +1 (415) 800-4557 <+14158004557> [image: Envelope Icon] lionel@userway.org <lionel@userway.org> [image: Schedule with Me] <https://userway.org/s/lionel?utm_source=email-signature&utm_medium=email&utm_campaign=Lionel_Wolberger> On Mon, Nov 7, 2022 at 10:16 PM Janina Sajka <janina@rednote.net> wrote: > 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 Monday, 7 November 2022 21:55:59 UTC