RE: Re:RE: essential use case of personlization missed out

I have some experience of the use of symbols to support people with cognitive\literacy difficulties.

A key aspect of providing symbolised versions of content is that the content is re-written specifically to be translated into symbols. As Lisa points out, there are multiple symbol libraries which people use.

Providing a direct translation of a portion of text into its equivalent symbol language (Rebus, Makaton, BSL etc) would not provide a satisfactory outcome; in much the same way as machine translating from one language to another verbatim will have undesirable results. Having a symbolised document littered with common symbols (a, the, and) does not necessarily make it more readable. Like BSL, there must be some thought to the grammar and language structure of symbol documents.

Not sure what the solution would look like, but suspect it would be partially addressed by the current AAA SC 3.1.5 Reading Level: - Having content written that is easy to understand, and avoids jargon\terminology, would have better results at being translated into symbols.

I do know of at least one proprietary browser plugin that provides symbol support on a per-word basis for users; this functions broadly in the same way as BrowseAloud, but in this case, it is the end user who pays for the product, not the site owner. This at least allows users to get different levels of support, but doesn’t take into account content on sites being written to take advantage of these symbols.


From: lisa.seeman []
Sent: 26 July 2017 09:51
Subject: Re:RE: essential use case of personlization missed out

Content that is made specifically for symbol users uses symbols by most of the text or in place of it- not just controls.

We can add this to the AAA level but we really urgently need it a A or AA so that people can talk to each other and symbol users can share content.

All the best

Lisa Seeman

LinkedIn<>, Twitter<>

---- On Wed, 26 Jul 2017 10:15:04 +0300<> wrote ----

Hi Lisa,

I’m a bit confused, I take it this is separate from the purpose of controls AA one we’re discussing, and the AAA equivalent of that.

In which case, what is the content requirement? What is it sites would need to do to support symbol use?



From: lisa.seeman [<>]
Sent: 26 July 2017 04:26
To: public-cognitive-a11y-tf <<>>; W3c-Wai-Gl-Request@W3. Org <<>>
Subject: essential use case of personlization missed out

Hi Folks

We need to see a single A requirement interoperable symbol set codes for non-verbal people. Products for people who are non vocal often use symbols to help users communicate. These symbols are in fact peoples language and people spend years learning a set of symbols tat can not be used with content that is made for these users but by a different company or indeed talk to other people with the same disability but who have learnt the symbols from a different company. Unfortunately many of these symbols are both subject to copy write and are not interoperable. That means end-users can only use one device, and can not use apps or AT from a different company. An open set of references for symbol codes for these symbol sets however, could be interoperable. That means the end user could use an open source symbol set or buy the symbols and use them across different devices or applications. Symbols could still be proprietary but they would also be interoperable.

We need to include this as soon as possible. In the mean time people can lose their language for copy write reasons. However with the current personlization proposal it is only in at AAA. It is such a basic infringement on human rights that it needs to be single A (or higher - this is peoples ONLY way to communicate)

We can make a supporting technique to 1.1.3 , but the "or text" clause plus the requirement of 1.1.1 makes it a redundant technique.

Can we try and find some way to get this in as single A? Technology support includes concept codes or linking to a wordnet concept

Lisa Seeman

LinkedIn<>, Twitter<>

Received on Friday, 28 July 2017 13:13:21 UTC