W3C home > Mailing lists > Public > public-personalization-tf@w3.org > October 2018

Re: Personalization Introduction

From: Janina Sajka <janina@rednote.net>
Date: Tue, 16 Oct 2018 13:46:42 -0400
To: "lisa.seeman" <lisa.seeman@zoho.com>
Cc: Charles LaPierre <charlesl@benetech.org>, public-personalization-tf <public-personalization-tf@w3.org>
Message-ID: <20181016174642.GC2087@rednote.net>
OK, but if we're expanding COGA we should follow the usual conventions,

"... the Cognitive Accessibility Task Force (COGA), ..."

Lisa Seeman writes:
> hi My 2 cents is we should not assume people know what coga is. and we should add a sentence that it supports user needs beyond what it currently possible, and try and make it wider. I also changed the reference to UNICEF a bit so it is a bit more accurate. I also think braking up into paragraphs can help it be absorbed Here are my edits:   Summary: The Personalization TF now part of the APA would like your help in deciding which implementation schema we should use for our Personalization modules we have been developing. This work came out of COGA (cognitive accessibility), the former Indie-UI WG, and other WAI groups and has been worked on previously under ARIA. The goal of the Personalization task force is to enable the adaptation of web content to user needs far beyond what is currently supported, so that more usergroups can be included in the digital world and content can adapt to more scenarios such as stress and illness. Sometimes users may need simplification of text and concepts or translation into symbols. Others may need content that is free of numbers, minimizes distractions, or provides additional help. The author augments the content to identify contexts, options, simplifications, or replacements. User agents or other technologies use these semantics to augment or adapt the content based on identified user preferences. Examples: The content might specify that, "9 out of 10 people prefer coffee over tea". The author would identify the "9 out of 10” phrase and provide "almost all" as the number free alternative. People who use symbols to communicate often don’t understand symbols from another set. This work solves this problem enabling linked data  symbols (with UNICEF) with standard tokens can then be mapped to each unique symbol set. The task force has 3 modules and an explainer document in editor draft status. Below are links to these documents and to a Google Document comparing the implementation strategies we have explored. The task force needs your help to select the best implementation schema for the personalization semantics. We have eliminated RDFa, HTML Microdata, and ARIA attributes as not practical at this time.  >  > <Links to modules & Google Doc> 


Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Tuesday, 16 October 2018 17:47:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:57 UTC