Re: Personalization thoughts & takeaways from TPAC

Thanks John, great summary.

At the end of the Plenary day each group would asked to give a 2 minute update of what was discussed during the 1 hour session.  This is what I reported to the 100+ members who showed up at the end of a very long day of plenary sessions.

Personalization How Should it be Implemented

The goal of the Personalization task force is to enable the adaptation of web content to user needs far beyond what is currently supported.  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.

We discussed various options of how to “attach” these new semantics to web elements.

Some options that was suggested a new attribute named “Purpose” be considered which would help not only the personalization concerns we have addressed but is something that would also be helpful for the groups as well such as the Publishing WG.

Also, User Preferences (such as font size, color, spacing etc.) was something that was brought up as a need.  As for finding how to attach these attributes we have identified there may be other options such as using web Components or web Annotations to help Personalize the content.  Next steps will be to discuss these options and reach out to Web Platforms to help focus our identified ways to attach our semantics to web content and ask TAG for an initial review of our Explainer and 3 modules before we go down the wrong rabbit hole.


Thanks
EOM

Charles LaPierre
Technical Lead, DIAGRAM and Born Accessible
Twitter: @CLaPierreA11Y
Skype: charles_lapierre
Phone: 650-600-3301



On Oct 25, 2018, at 10:53 AM, John Foliot <john.foliot@deque.com<mailto:john.foliot@deque.com>> wrote:

Relevant Minutes:

https://www.w3.org/2018/10/22-WebPlat-minutes.html#item04

https://www.w3.org/2018/10/24-personalization-minutes


Web Plat meeting:

  *   Web Plat guidance is to likely for us ask for 1-3 new attributes

  *   They would like to see the taxonomies slightly more mature (we should do a concatenated version as well)

  *   Terence Eden: HM Gov (UK) are keen to help on this. (Spoke with Terrence Thursday - will forward meeting agenda/invite for our next call to him)

  *   Don't go for a micro-syntax.

  *   Avoid AUI-* attributes. Concerns because there is a CSS vendor that already uses that prefix, my (Brian Kardell) company also uses it, probably others.

  *   Suggest not prefixing it - there are multiple use cases outside the personalisation semantics. Siloing it into accessibility will actually reduce uptake in useful scenarios.

Plenary Day Presentation:

  *   Correlation with Web Publishing (Ivan Herman) - we should follow up. They too are interested in a general purpose attribute (purpose="").

  *   The role of Web Annotations in crowd-sourced augmentation should be investigated (idioms and expressions - also think about "slang")

  *   Q: do we have a longer-range vision statement? Where? Role of machine learning and AI?

  *   Concern around "name" (comments about "personalization" such as "change my font size and remember it" in i.e. Captions)

  *   Some people in the captions world worry about the change of subtitle text. Different constituents have different views on how it should work. It also has privacy impacts, in case of JavaScript access to that type of personalization.

  *   We are going to (we should) ask for a TAG review

JF
--
John Foliot | Principal Accessibility Strategist
Deque Systems - Accessibility for Good
deque.com<http://deque.com/>