Sounds good, I can take a look later this week.
On Mon, Nov 28, 2022 at 8:33 AM Roy Ruoxi Ran <ran@w3.org> wrote:
> FYI, we have updated the link of [2] W3C Alternative and Augmented
> Communication (AAC) Symbol Registry to https://w3c.github.io/aac-registry/
>
> Sorry for confusion.
>
> Best,
>
> Roy
>
> 2022年11月28日 14:12,Roy Ruoxi Ran <ran@w3.org> 写道:
>
> Hi Vladimir, Garret and Web Fonts WG,
>
> According to the request from PLH for the W3C transition process, the
> Accessible Platform Architectures (APA) Working Group hereby formally
> requests a review from WebFonts WG from Web Fonts technology perspective.
>
> Documents are needed to review as below:
>
> *[1] WAI-Adapt: Symbols Module *(to CR):
> https://w3c.github.io/adapt/symbols/
> *[2] W3C Alternative and Augmented Communication (AAC) Symbol Registry *(to
> First Registry Draft):
> https://w3c.github.io/adapt-registry/
>
> There is also an explainer for your reference at:
> https://w3c.github.io/adapt/
>
> The technology described in WAI-Adapt: Symbols Module [1] is intended to
> be used to programmatically transform the appearance of typical web content
> including form controls, icons, and other user interface elements into a
> rendering incorporating an individual user's preferred AAC symbols, there
> is an example show the proof of concept at:
> https://w3c.github.io/adapt/#proof-of-concept-symbol-example.
> The W3C Alternative and Augmented Communication (AAC) Symbol Registry
> <https://w3c.github.io/adapt-registry/> [2] provides the required
> mappings between concept values used by content authors and the user's
> preferred AAC symbol set representation of that concept.
>
> Please file any feedbacks into corresponding GitHub issues at: WAI-Adapt
> Github issue <https://github.com/w3c/adapt/issues/new> and Adapt registry
> issue <https://github.com/w3c/adapt-registry/issues/new>.
>
> Thank you,
>
> Best,
>
> Roy
>
>
>