-
Notifications
You must be signed in to change notification settings - Fork 27
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
10 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,7 @@ | ||
WAI News: | ||
W3C News: | ||
|
||
Announcing: *WAI-Adapt: Symbols Module* Candidate Recommendation | ||
CR — W3C Invites Implementations of WAI-Adapt: Symbols Module | ||
|
||
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](https://www.w3.org/TR/adapt-symbols/). The purpose of this specification is to support Augmentative and Alternative Communication (AAC) symbols in web content. Millions of users comprehend AAC symbols better than standard text, but there are multiple AAC symbol sets and they are not mutually comprehensible. To solve this issue and make it possible for content creators to support AAC users in web content, this specification defines the appropriate use of Blissymbolics Communication International (BCI) concept indexing as spefieid by the [W3C Alternative and Augmented Communication (AAC) Symbol Registry](https://www.w3.org/TR/aac-registry/) in web content, provided guidance on associating an appropriate BCI index value with a span of text corresponding to the defined concept expressed as standard text, and 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. Please send comments by Friday 24 February 2023. | ||
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](https://www.w3.org/TR/adapt-symbols/). The purpose of this specification is to support Augmentative and Alternative Communication (AAC) symbols in web content. Millions of users comprehend AAC symbols better than standard text, but there are multiple AAC symbol sets and they are not mutually comprehensible. To solve this issue and make it possible for content creators to support AAC users in web content, this specification defines the appropriate use of Blissymbolics Communication International (BCI) concept indexing as spefieid by the [W3C Alternative and Augmented Communication (AAC) Symbol Registry](https://www.w3.org/TR/aac-registry/) in web content, provided guidance on associating an appropriate BCI index value with a span of text corresponding to the defined concept expressed as standard text, and 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. | ||
Please send comments by *24 February 2023*. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
WAI News: | ||
|
||
Call for Implementations: WAI-Adapt: Symbols Module Candidate W3C Recommendation | ||
|
||
[WAI-Adapt: Symbols Module](https://www.w3.org/TR/adapt-symbols/) has been published as a Candidate Recommendation. The purpose of this specification is to support Augmentative and Alternative Communication (AAC) symbols in web content. We’re seeking implementations for symbol attribute and welcome comment. Please submit implementations and any comments by *24 February 2023*. | ||
|