From ba5209f68564fc16dbbd1fb66ce65845cd6c1844 Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 22 Jul 2025 14:02:38 +0100 Subject: [PATCH 01/13] Post-workshop updates --- explainers/symbols.md | 113 +++++++++++++++++++++++++----------------- 1 file changed, 68 insertions(+), 45 deletions(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index e12754e..8228292 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -48,14 +48,30 @@ Some people find graphical symbols easier to interpret than written text. They may find that when symbols are presented alongside text content, that content is easier to understand. But there are many different symbol sets in use, and people don't tend to learn more than one. -We propose the `adapt-symbol` attribute, which allows content authors to mark up the _concepts_ relevant to their content, +We propose an approach that allows content authors to mark up the _concepts_ relevant to their content, so that the appropriate symbol(s) for that concept can be rendered for the user, using _their chosen symbol set_. We use the set of concepts maintained by [Blissymbolics Communication International](https://www.blissymbolics.org/) (BCI). These concepts underpin the Blissymbolics (or "Bliss") language—though our use of the concepts is strictly for mapping from a concept to the appropriate aymbol(s) for the user, and is not grammatical in nature. -We're working closely with BCI on this specification, and the W3C AAC Symbol Registry (more details below). +We're working closely with BCI on this approach, and the W3C AAC Symbol Registry (more details below). + +Broadly speaking, the approach is comprised of the following: + +* **The use of (upcoming) Bliss Unicode code points to encode a concept.** + + A font then maps these code points into the appropriate symbol for the user. + + The code points are under Unicode Consortium review. + +* **Use of the `` element for presentation—with an attribute to indicate this is a symbol.** + + The idea is that the browser will not display such elements by default, but will do if the user has expressed a preference for symbols to be shown. + +* **A registry of concepts (BCI code point sets) for authors to look up.** + + The [W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry) is described below. ### Demo @@ -94,13 +110,51 @@ Though rendering is out of scope, it's important to be aware of the nature of sy > [!NOTE] > This work has been developed over several years, with input from the Cognitive Accessibility TF, and experts from BCI. We will add references to some key elements of that background work here. -## The `adapt-symbol` attribute +## Use of Bliss Unicode code points + +FIXME + +## Extending `` to support "symbol" + +FIXME + +## The W3C AAC Symbol Registry + +> [!NOTE] +> We are planning to split this explainer off into a separate file, to avoid explainers that are too long. + +The registry brings BCI's dictionary of concepts into W3C space. Each record in the registry contains: + +* A uniquely-identifying key. + +* A description of the concept in a written language (e.g. English). + +* The Bliss symbol(s) that embody this concept in the Bliss language. + +The registry can be found at: https://www.w3.org/TR/aac-registry/ + +> [!NOTE] +> The registry's key for identifying concepts is presently the concepts' BCI concept ID (an integer). However, as discussed above, we are in discussions with potential implementers on whether the corresponding Bliss Unicode code point(s) for a given concept could be used instead. + +## Privacy considerations + +> [!NOTE] +> This section is to be expanded. + +Because the rendering of symbols is expected to be done by injecting them into the HTML, the site could determine that the user is using symbols, and which symbol set is in use. + +## Considered alternatives + +> [!NOTE] +> This section is to be made more concise (after the outcome of the workshop has been incorporated into the primary sections above), and have any additional alternative approaches added. + +### The `adapt-symbol` attribute The intent of the `adapt-symbol` attribute is to link a _concept_ (for which the UA will render an appropriate symbol for the user) to some content (usually text) on the page. The value of the `adapt-symbol` attribute is a representation of a concept, which will be rendered as one or more symbols by the UA. There are several ways that the concepts may be encoded, which is the subject of current discussion. -### Mapping concepts to symbols (in general) +#### Mapping concepts to symbols (in general) There are a number of ways we may identify, or "key", concepts—some alternatives are discussed below. @@ -146,17 +200,17 @@ Here are three examples of how the `adapt-symbol` attribute could be used. שמה ``` -### Concept IDs: keying schemes +#### Concept IDs: keying schemes There is [ongoing discussion on how the concepts should be expressed in the HTML markup in issue 240](https://github.com/w3c/adapt/issues/240). This section makes three suggestions. -#### BCI concept IDs as attribute values +##### BCI concept IDs as attribute values ***This keying scheme maps one integer (the BCI concept ID) to a concept.*** BCI maintains a dictionry of concepts, with corresponding Bliss symbols, and written-language definitions. -##### Advantages +###### Advantages * Simple—provides a 1:1 mapping between concept and key that identifies the concept. @@ -164,11 +218,11 @@ BCI maintains a dictionry of concepts, with corresponding Bliss symbols, and wri * Relatively minimal lag time between a concept addition/update and availability via authoring tools, or the W3C AAC Symbol Registry. -##### Disadvantages +###### Disadvantages * Allows us to only specify concepts available in the Bliss language. (But we can still map to any symbol set, based on those concepts.) -#### Bliss characters' Unicode representations as attribute values +##### Bliss characters' Unicode representations as attribute values ***This maps one or more representations of Bliss characters (symbols) to a concept.*** @@ -188,24 +242,23 @@ Instead of BCI concept IDs (integers), we could use: > [!NOTE] > Further details can be found in our comment on issue 240 (this comment only suggest the user of code points directly, though): . -##### Advantages +###### Advantages * Based on an existing standard (Unicode). -##### Disadvantages +###### Disadvantages * Exposes the implementation details of Bliss to someone writing this markup. - As part of this, it's more complex than using atomic keys (such as BCI concept IDs): some concepts that would be represented by one BCI ID would need more than one Bliss character representation to identify them. - -##### Unknown factors +###### Unknown factors * Unclear as to what the process for adding additional Bliss characters to Unicode would be. * The time between new concepts being added to Bliss, and them being available via Unicode would likely be significant, due to the release cadence of Unicode. -### Multiple concepts per attribute value +#### Multiple concepts per attribute value Though it is not expected to be used extensively, we have considered how multiple concepts may be referenced within one attribute value. @@ -228,40 +281,10 @@ In this example, there are 4 concepts identified, via... > [!NOTE] > We want to maintain consitency with how other parts of the platform handle this—we're very-much open to using other delimiters if needed. -### Looking up concepts +#### Looking up concepts The content author needs to be able to find known concepts, and their associated identifier. This is addressed in the next section. -## The W3C AAC Symbol Registry - -> [!NOTE] -> We are planning to split this explainer off into a separate file, to avoid explainers that are too long. - -The registry brings BCI's dictionary of concepts into W3C space. Each record in the registry contains: - -* A uniquely-identifying key. - -* A description of the concept in a written language (e.g. English). - -* The Bliss symbol(s) that embody this concept in the Bliss language. - -The registry can be found at: https://www.w3.org/TR/aac-registry/ - -> [!NOTE] -> The registry's key for identifying concepts is presently the concepts' BCI concept ID (an integer). However, as discussed above, we are in discussions with potential implementers on whether the corresponding Bliss Unicode code point(s) for a given concept could be used instead. - -## Privacy considerations - -> [!NOTE] -> This section is to be expanded. - -Because the rendering of symbols is expected to be done by injecting them into the HTML, the site could determine that the user is using symbols, and which symbol set is in use. - -## Considered alternatives - -> [!NOTE] -> This section is to be added. - ## Stakeholder feedback/opposition Our work is currently focused on working with BCI within W3C to solidify our recommendations for the syntax of the `adapt-symbol` attribute. We have run several breakouts on the work, and will more actively seek feedback once this is decided. From 9e3dd09f7c6a6282c1821445e732fcb541088c89 Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 22 Jul 2025 14:09:36 +0100 Subject: [PATCH 02/13] Update ToC --- explainers/symbols.md | 26 ++++++++++++++------------ 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 8228292..39e028a 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -19,21 +19,23 @@ - [Out of scope](#out-of-scope) - [Important notes on symbols and rendering](#important-notes-on-symbols-and-rendering) - [User research](#user-research) -- [The `adapt-symbol` attribute](#the-adapt-symbol-attribute) - * [Mapping concepts to symbols (in general)](#mapping-concepts-to-symbols-in-general) - * [Concept IDs: keying schemes](#concept-ids-keying-schemes) - + [BCI concept IDs as attribute values](#bci-concept-ids-as-attribute-values) - - [Advantages](#advantages) - - [Disadvantages](#disadvantages) - + [Bliss characters' Unicode representations as attribute values](#bliss-characters-unicode-representations-as-attribute-values) - - [Advantages](#advantages-1) - - [Disadvantages](#disadvantages-1) - - [Unknown factors](#unknown-factors) - * [Multiple concepts per attribute value](#multiple-concepts-per-attribute-value) - * [Looking up concepts](#looking-up-concepts) +- [Use of Bliss Unicode code points](#use-of-bliss-unicode-code-points) +- [Extending `` to support "symbol"](#extending--to-support-symbol) - [The W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry) - [Privacy considerations](#privacy-considerations) - [Considered alternatives](#considered-alternatives) + * [The `adapt-symbol` attribute](#the-adapt-symbol-attribute) + + [Mapping concepts to symbols (in general)](#mapping-concepts-to-symbols-in-general) + + [Concept IDs: keying schemes](#concept-ids-keying-schemes) + - [BCI concept IDs as attribute values](#bci-concept-ids-as-attribute-values) + * [Advantages](#advantages) + * [Disadvantages](#disadvantages) + - [Bliss characters' Unicode representations as attribute values](#bliss-characters-unicode-representations-as-attribute-values) + * [Advantages](#advantages-1) + * [Disadvantages](#disadvantages-1) + * [Unknown factors](#unknown-factors) + + [Multiple concepts per attribute value](#multiple-concepts-per-attribute-value) + + [Looking up concepts](#looking-up-concepts) - [Stakeholder feedback/opposition](#stakeholder-feedbackopposition) - [References](#references) - [Acknowledgments](#acknowledgments) From 74cf99b50838cf757e872850507201cbcf416f8c Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 22 Jul 2025 14:24:34 +0100 Subject: [PATCH 03/13] Content additions --- explainers/symbols.md | 55 +++++++++++++++++++++++++++++++++++++++---- 1 file changed, 50 insertions(+), 5 deletions(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 39e028a..5df37d3 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -20,7 +20,12 @@ - [Important notes on symbols and rendering](#important-notes-on-symbols-and-rendering) - [User research](#user-research) - [Use of Bliss Unicode code points](#use-of-bliss-unicode-code-points) -- [Extending `` to support "symbol"](#extending--to-support-symbol) + * [Content author's perspective](#content-authors-perspective) + * [Symbol providers' perspective](#symbol-providers-perspective) + * [Browser implementers' perspective](#browser-implementers-perspective) + * [Unicode perspective](#unicode-perspective) + * [Managing changes](#managing-changes) +- [Extending `` to support "symbol" content](#extending--to-support-symbol-content) - [The W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry) - [Privacy considerations](#privacy-considerations) - [Considered alternatives](#considered-alternatives) @@ -75,6 +80,12 @@ Broadly speaking, the approach is comprised of the following: The [W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry) is described below. +Here's an example of what some mark-up might look like (you would need a font that supports Bliss' code points in order for this to render correctly)... + +```html +

A nice cup@@@ of tea@@@.

+``` + ### Demo A proof-of-concept authoring tool demo can be found at: http://matatk.agrip.org.uk/adaptable-content-authoring-tool/editor/ @@ -114,11 +125,40 @@ Though rendering is out of scope, it's important to be aware of the nature of sy ## Use of Bliss Unicode code points -FIXME +> [!NOTE] +> This section to be completed. + +### Content author's perspective -## Extending `` to support "symbol" +> [!NOTE] +> This section to be completed. + +### Symbol providers' perspective + +> [!NOTE] +> This section to be completed. + +### Browser implementers' perspective + +> [!NOTE] +> This section to be completed. -FIXME +### Unicode perspective + +> [!NOTE] +> This section to be completed. + +### Managing changes + +> [!NOTE] +> This section to be completed. + +## Extending `` to support "symbol" content + +> [!NOTE] +> This section to be completed. + +There is [a proposal to extend the `` element to indicate when "symbol" content is being used](https://github.com/w3c/html-ruby/issues/24). ## The W3C AAC Symbol Registry @@ -143,7 +183,12 @@ The registry can be found at: https://www.w3.org/TR/aac-registry/ > [!NOTE] > This section is to be expanded. -Because the rendering of symbols is expected to be done by injecting them into the HTML, the site could determine that the user is using symbols, and which symbol set is in use. +It would be possible for a site to know that symbols are being displayed. + +The site could also find out which font is being used. + +> [!NOTE] +> Double-check on font detection. ## Considered alternatives From b4098ae617990cab9f601f173df336639714dfa3 Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 22 Jul 2025 15:29:50 +0100 Subject: [PATCH 04/13] Typo --- explainers/symbols.md | 80 +++++++++++++++++++++---------------------- 1 file changed, 40 insertions(+), 40 deletions(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 5df37d3..4d9dcce 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -9,44 +9,44 @@ * Issues: https://github.com/w3c/adapt/issues * Discussions: https://github.com/w3c/adapt/discussions -## Contents - - - -- [Introduction](#introduction) - * [Demo](#demo) -- [Goals](#goals) -- [Out of scope](#out-of-scope) -- [Important notes on symbols and rendering](#important-notes-on-symbols-and-rendering) -- [User research](#user-research) -- [Use of Bliss Unicode code points](#use-of-bliss-unicode-code-points) - * [Content author's perspective](#content-authors-perspective) - * [Symbol providers' perspective](#symbol-providers-perspective) - * [Browser implementers' perspective](#browser-implementers-perspective) - * [Unicode perspective](#unicode-perspective) - * [Managing changes](#managing-changes) -- [Extending `` to support "symbol" content](#extending--to-support-symbol-content) -- [The W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry) -- [Privacy considerations](#privacy-considerations) -- [Considered alternatives](#considered-alternatives) - * [The `adapt-symbol` attribute](#the-adapt-symbol-attribute) - + [Mapping concepts to symbols (in general)](#mapping-concepts-to-symbols-in-general) - + [Concept IDs: keying schemes](#concept-ids-keying-schemes) - - [BCI concept IDs as attribute values](#bci-concept-ids-as-attribute-values) - * [Advantages](#advantages) - * [Disadvantages](#disadvantages) - - [Bliss characters' Unicode representations as attribute values](#bliss-characters-unicode-representations-as-attribute-values) - * [Advantages](#advantages-1) - * [Disadvantages](#disadvantages-1) - * [Unknown factors](#unknown-factors) - + [Multiple concepts per attribute value](#multiple-concepts-per-attribute-value) - + [Looking up concepts](#looking-up-concepts) -- [Stakeholder feedback/opposition](#stakeholder-feedbackopposition) -- [References](#references) -- [Acknowledgments](#acknowledgments) - - - +## Contents + + + +- [Introduction](#introduction) + * [Demo](#demo) +- [Goals](#goals) +- [Out of scope](#out-of-scope) +- [Important notes on symbols and rendering](#important-notes-on-symbols-and-rendering) +- [User research](#user-research) +- [Use of Bliss Unicode code points](#use-of-bliss-unicode-code-points) + * [Content author's perspective](#content-authors-perspective) + * [Symbol providers' perspective](#symbol-providers-perspective) + * [Browser implementers' perspective](#browser-implementers-perspective) + * [Unicode perspective](#unicode-perspective) + * [Managing changes](#managing-changes) +- [Extending `` to support "symbol" content](#extending--to-support-symbol-content) +- [The W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry) +- [Privacy considerations](#privacy-considerations) +- [Considered alternatives](#considered-alternatives) + * [The `adapt-symbol` attribute](#the-adapt-symbol-attribute) + + [Mapping concepts to symbols (in general)](#mapping-concepts-to-symbols-in-general) + + [Concept IDs: keying schemes](#concept-ids-keying-schemes) + - [BCI concept IDs as attribute values](#bci-concept-ids-as-attribute-values) + * [Advantages](#advantages) + * [Disadvantages](#disadvantages) + - [Bliss characters' Unicode representations as attribute values](#bliss-characters-unicode-representations-as-attribute-values) + * [Advantages](#advantages-1) + * [Disadvantages](#disadvantages-1) + * [Unknown factors](#unknown-factors) + + [Multiple concepts per attribute value](#multiple-concepts-per-attribute-value) + + [Looking up concepts](#looking-up-concepts) +- [Stakeholder feedback/opposition](#stakeholder-feedbackopposition) +- [References](#references) +- [Acknowledgments](#acknowledgments) + + + ## Introduction @@ -60,7 +60,7 @@ so that the appropriate symbol(s) for that concept can be rendered for the user, using _their chosen symbol set_. We use the set of concepts maintained by [Blissymbolics Communication International](https://www.blissymbolics.org/) (BCI). -These concepts underpin the Blissymbolics (or "Bliss") language—though our use of the concepts is strictly for mapping from a concept to the appropriate aymbol(s) for the user, and is not grammatical in nature. +These concepts underpin the Blissymbolics (or "Bliss") language—though our use of the concepts is strictly for mapping from a concept to the appropriate symbol(s) for the user, and is not grammatical in nature. We're working closely with BCI on this approach, and the W3C AAC Symbol Registry (more details below). @@ -353,4 +353,4 @@ We have engaged with experts in the COGA TF regarding the appropriateness of bui * Russell Galvin, BCI -* WAI-Adapt TF participants +* WAI-Adapt TF participants From 8d763b2e8ca6ff81e55cbb0461fb45a9737bc054 Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 22 Jul 2025 15:34:32 +0100 Subject: [PATCH 05/13] Streamlining, per call --- explainers/symbols.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 4d9dcce..c010019 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -62,9 +62,7 @@ using _their chosen symbol set_. We use the set of concepts maintained by [Blissymbolics Communication International](https://www.blissymbolics.org/) (BCI). These concepts underpin the Blissymbolics (or "Bliss") language—though our use of the concepts is strictly for mapping from a concept to the appropriate symbol(s) for the user, and is not grammatical in nature. -We're working closely with BCI on this approach, and the W3C AAC Symbol Registry (more details below). - -Broadly speaking, the approach is comprised of the following: +We're working closely with BCI on this approach, which is comprised of the following: * **The use of (upcoming) Bliss Unicode code points to encode a concept.** From 93a05580b2862d4137f59b1e0942a54945d70b23 Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 22 Jul 2025 15:44:39 +0100 Subject: [PATCH 06/13] Re-order sections, per call --- explainers/symbols.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index c010019..b4deb7d 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -25,8 +25,8 @@ * [Browser implementers' perspective](#browser-implementers-perspective) * [Unicode perspective](#unicode-perspective) * [Managing changes](#managing-changes) -- [Extending `` to support "symbol" content](#extending--to-support-symbol-content) - [The W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry) +- [Extending `` to support "symbol" content](#extending-ruby-to-support-symbol-content) - [Privacy considerations](#privacy-considerations) - [Considered alternatives](#considered-alternatives) * [The `adapt-symbol` attribute](#the-adapt-symbol-attribute) @@ -64,20 +64,20 @@ These concepts underpin the Blissymbolics (or "Bliss") language—though our We're working closely with BCI on this approach, which is comprised of the following: -* **The use of (upcoming) Bliss Unicode code points to encode a concept.** +* **The use of Bliss Unicode code points to encode a concept.** A font then maps these code points into the appropriate symbol for the user. The code points are under Unicode Consortium review. -* **Use of the `` element for presentation—with an attribute to indicate this is a symbol.** - - The idea is that the browser will not display such elements by default, but will do if the user has expressed a preference for symbols to be shown. - * **A registry of concepts (BCI code point sets) for authors to look up.** The [W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry) is described below. +* **Use of the `` element for presentation—with an attribute to indicate this is a symbol.** + + The idea is that the browser will not display such elements by default, but will do if the user has expressed a preference for symbols to be shown. + Here's an example of what some mark-up might look like (you would need a font that supports Bliss' code points in order for this to render correctly)... ```html @@ -151,13 +151,6 @@ Though rendering is out of scope, it's important to be aware of the nature of sy > [!NOTE] > This section to be completed. -## Extending `` to support "symbol" content - -> [!NOTE] -> This section to be completed. - -There is [a proposal to extend the `` element to indicate when "symbol" content is being used](https://github.com/w3c/html-ruby/issues/24). - ## The W3C AAC Symbol Registry > [!NOTE] @@ -176,6 +169,13 @@ The registry can be found at: https://www.w3.org/TR/aac-registry/ > [!NOTE] > The registry's key for identifying concepts is presently the concepts' BCI concept ID (an integer). However, as discussed above, we are in discussions with potential implementers on whether the corresponding Bliss Unicode code point(s) for a given concept could be used instead. +## Extending `` to support "symbol" content + +> [!NOTE] +> This section to be completed. + +There is [a proposal to extend the `` element to indicate when "symbol" content is being used](https://github.com/w3c/html-ruby/issues/24). + ## Privacy considerations > [!NOTE] From 4c55809cf1f42e72273de953592e62de3a90956b Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 22 Jul 2025 15:47:25 +0100 Subject: [PATCH 07/13] Remove link to AAC Symbols Registry from intro Per the call, the three intro bullets should introduce the primary sections to come later, as equals. So no need to link to just one. --- explainers/symbols.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index b4deb7d..409f448 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -72,7 +72,7 @@ We're working closely with BCI on this approach, which is comprised of the follo * **A registry of concepts (BCI code point sets) for authors to look up.** - The [W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry) is described below. + The W3C AAC Symbol Registry provides the code points used to identify a given concept. * **Use of the `` element for presentation—with an attribute to indicate this is a symbol.** From b52ca4a0d35f4e5c0176f1027701d3f89722651f Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 9 Sep 2025 13:33:26 +0100 Subject: [PATCH 08/13] Rename to remove 'module' --- explainers/symbols.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 409f448..927277e 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -1,4 +1,4 @@ -# WAI-Adapt: Symbols Module Explainer +# WAI-Adapt: Symbols Explainer ## Authors From caeb5630c2deea5d4ff387faac14018d8b901b56 Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 9 Sep 2025 13:39:48 +0100 Subject: [PATCH 09/13] Tweak phrasing to include the registry in this doc --- explainers/symbols.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 927277e..654451a 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -106,6 +106,9 @@ Please note the following limitations: * Providing an exhaustive list of concepts (the [W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry), described below, aims to do this). +> [!CAUTION] +> The last point here contradicts the inclusion of the registry section in this document; perhaps a better way to explain it would be to say that we're not relying on _content authors_ to provide an exhaustive list of concepts—rather that we have one, from Bliss, in the form of the registry. + ## Important notes on symbols and rendering Though rendering is out of scope, it's important to be aware of the nature of symbols, and different symbol sets: @@ -153,9 +156,6 @@ Though rendering is out of scope, it's important to be aware of the nature of sy ## The W3C AAC Symbol Registry -> [!NOTE] -> We are planning to split this explainer off into a separate file, to avoid explainers that are too long. - The registry brings BCI's dictionary of concepts into W3C space. Each record in the registry contains: * A uniquely-identifying key. From 3ad92ff1fcb796a7b6320848d5e4095516cdbe11 Mon Sep 17 00:00:00 2001 From: Lionel <2069690+lwolberg@users.noreply.github.com> Date: Tue, 10 Feb 2026 17:45:48 +0200 Subject: [PATCH 10/13] Apply suggestion from @lwolberg --- explainers/symbols.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 654451a..4e0651b 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -76,7 +76,7 @@ We're working closely with BCI on this approach, which is comprised of the follo * **Use of the `` element for presentation—with an attribute to indicate this is a symbol.** - The idea is that the browser will not display such elements by default, but will do if the user has expressed a preference for symbols to be shown. + The idea is that the browser will not display such elements by default, but will do so if the user has expressed a preference for symbols to be shown. Here's an example of what some mark-up might look like (you would need a font that supports Bliss' code points in order for this to render correctly)... From 57caaed2e20fb1c36cc9000fba0de10bbdf0a7cb Mon Sep 17 00:00:00 2001 From: Lionel <2069690+lwolberg@users.noreply.github.com> Date: Tue, 10 Feb 2026 17:49:15 +0200 Subject: [PATCH 11/13] Apply suggestion from @lwolberg --- explainers/symbols.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 4e0651b..6098443 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -74,7 +74,7 @@ We're working closely with BCI on this approach, which is comprised of the follo The W3C AAC Symbol Registry provides the code points used to identify a given concept. -* **Use of the `` element for presentation—with an attribute to indicate this is a symbol.** +* **Use of the `` element for presentation—with a `lang=zbl` attribute to indicate this is a symbol.** The idea is that the browser will not display such elements by default, but will do so if the user has expressed a preference for symbols to be shown. From 16a6448456bf34eb01306e2aa4664be7a43b74d9 Mon Sep 17 00:00:00 2001 From: Lionel <2069690+lwolberg@users.noreply.github.com> Date: Tue, 10 Feb 2026 17:55:09 +0200 Subject: [PATCH 12/13] Apply suggestion from @lwolberg --- explainers/symbols.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 6098443..4076676 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -81,7 +81,7 @@ We're working closely with BCI on this approach, which is comprised of the follo Here's an example of what some mark-up might look like (you would need a font that supports Bliss' code points in order for this to render correctly)... ```html -

A nice cup@@@ of tea@@@.

+

A nice cup@@@ of tea@@@.

``` ### Demo From 52a9a240690329eca455d666de86e349389b6f26 Mon Sep 17 00:00:00 2001 From: Matthew Tylee Atkinson Date: Tue, 24 Feb 2026 15:33:13 +0000 Subject: [PATCH 13/13] Clarify scope point about the registry --- explainers/symbols.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/explainers/symbols.md b/explainers/symbols.md index 4076676..f3f6d0e 100644 --- a/explainers/symbols.md +++ b/explainers/symbols.md @@ -104,7 +104,7 @@ Please note the following limitations: * Providing translation—the concepts are specified by the author to match the language of the page's content; if the page content were to be translated, the concepts would need to be translated too. -* Providing an exhaustive list of concepts (the [W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry), described below, aims to do this). +* Providing a way to define new concepts (the [W3C AAC Symbol Registry](#the-w3c-aac-symbol-registry), described below, provides a list of available concepts). > [!CAUTION] > The last point here contradicts the inclusion of the registry section in this document; perhaps a better way to explain it would be to say that we're not relying on _content authors_ to provide an exhaustive list of concepts—rather that we have one, from Bliss, in the form of the registry.