Rewritten messaging files

messaging/to-comment.md

@@ -1,12 +1,17 @@
 For in-progress updates to the document, see the Editors' Draft at:
+
 https://w3c.github.io/adapt/symbols/
 
 
-To comment, please use one of the following methods:
-  *   By GitHub: please open a new issue in the [WAI-Adapt GitHub repository](https://github.com/w3c/adapt/issues/new). Create separate GitHub issues for each topic, rather than commenting on multiple topics in a single issue.
-  *   By email: Please send comments in e-mail to [[email protected]](mailto:[email protected]). Include [Symbols] as the beginning of your subject line in your email.
+To comment, please use one of the following two methods:
+
+* By GitHub:
+please open a new issue in the [WAI-Adapt GitHub repository](https://github.com/w3c/adapt/issues/new).
 
+* By email:
+Please send comments in e-mail to <[email protected]>. Include \[Registry\] as the beginning of your subject line in your email message.
 
+Whether you comment in a github issue or by email, please create separate GitHub issues (or email messages) for each topic you address, rather than commenting on multiple topics in a single issue (or email).
 
 Please send comments by Friday 24 February 2023.
 

messaging/w3c-news.md

@@ -1,4 +1,5 @@
 WAI News:
+
 Announcing: *WAI-Adapt Symbols Module* Candidate Recommendation
 
 The Accessible Platform Architectures (APA) WAI-Adapt Task Force (WAI-Adapt) invites implementation and welcomes comment on the Candidate Recommendation of the [WAI-Adapt Symbols Module 1.0](https://www.w3.org/TR/adapt/symbols/).
@@ -12,17 +13,20 @@ The purpose of this specification is to support Augmentative and Alternative Com
 
 - It is anticipated that user agents will display the corresponding AAC symbol from the user's preferred symbol set by allowing the user to configure for their preferred AAC symbol set and cache that symbol set locally.
 
-
-
 For in-progress updates to the document, see the Editors' Draft at:
+
 https://w3c.github.io/adapt/symbols/
 
 
-To comment, please use one of the following methods:
-  *   By GitHub: please open a new issue in the [WAI-Adapt Registry GitHub repository](https://github.com/w3c/adapt/issues/new). Create separate GitHub issues for each topic, rather than commenting on multiple topics in a single issue.
-  *   By email: Please send comments in e-mail to [[email protected]](mailto:[email protected]). Include [Symbols] as the beginning of your subject line in your email.
+To comment, please use one of the following two methods:
+
+* By GitHub:
+please open a new issue in the [WAI-Adapt GitHub repository](https://github.com/w3c/adapt/issues/new).
 
+* By email:
+Please send comments in e-mail to <[email protected]>. Include \[Registry\] as the beginning of your subject line in your email message.
 
+Whether you comment in a github issue or by email, please create separate GitHub issues (or email messages) for each topic you address, rather than commenting on multiple topics in a single issue (or email).
 
 Please send comments by Friday 24 February 2023.
 

messaging/wai-announce-email.txt

@@ -0,0 +1,51 @@
+
+Dear WAI Interest Group,
+
+W3C WAI announces publication of the Candidate Recommendation of:
+
+WAI-Adapt Symbols Module 1.0
+
+https://www.w3.org/TR/adapt/symbols/
+
+*** Overview***
+
+* For the very first time in web content the WAI-Adapt Symbols Module 1.0 specifies a cross-platform standrad mechanism incorporating Augmentative and Alternative Communication (AAC) symbols in web content. It relies on the [WAI-Adapt registry](https://www.w3.org/TR/adapt-registry/) to achieve this. 
+
+
+* Authors are provided guidance on  associating an appropriate BCI index value with a span of text corresponding to the defined concept expressed as standard text.
+
+* It is anticipated that user agents will display the corresponding AAC symbol from the user's preferred symbol set by allowing the user to configure for their preferred AAC symbol set and cache that symbol set locally.
+
+For in-progress updates to the document, see the Editors' Draft at:
+
+https://w3c.github.io/adapt/symbols/
+
+
+To comment, please use one of the following two methods:
+
+* By GitHub:
+please open a new issue in the [WAI-Adapt GitHub repository](https://github.com/w3c/adapt/issues/new).
+
+* By email:
+Please send comments in e-mail to <[email protected]>. Include \[Registry\] as the beginning of your subject line in your email message.
+
+Whether you comment in a github issue or by email, please create separate GitHub issues (or email messages) for each topic you address, rather than commenting on multiple topics in a single issue (or email).
+
+Please send comments by Friday 24 February 2023.
+
+***Share***
+
+We encourage you to share this information widely. Please include @w3c_wai, @w3c, #accessibility, #a11y, @@
+Here's a tweet text you can use: 
+
+W3C announces the First Public Working Draft of *WAI-Adapt Registry for AAC Symbols*: https://www.w3.org/TR/adapt-registry/, providing first-time support for interoperable Augmentative and Alternative Communication (AAC) symbols support in web content.
+
+Regards,
+
+Sharon D Snider and Lionel Wolberger, Task Force Facilitators.
+
+Janina Sajka and Matthew Atkinson, APA Working Group Co-Chairs
+
+Roy Ran, W3C Staff Contact for APA Working Group
+
+