W3C home > Mailing lists > Public > public-personalization-tf@w3.org > December 2019

Explainer Edits

From: John Foliot <john.foliot@deque.com>
Date: Mon, 16 Dec 2019 11:54:47 -0600
Message-ID: <CAKdCpxxFy5cFYJGgFXwdR-CvDYHRt5oLtsAeUvfxjuf1fNG7mQ@mail.gmail.com>
To: public-personalization-tf <public-personalization-tf@w3.org>
Hi All,

Tried my hand at some editorial changes. I have included the Word Doc with
the "Track Changes" turned on, however I am proposing the following text:

1.1 Why We Need Personalization

We need personalization because:

·       The needs of an individual user may conflict with certain
established mainstream user-patterns.

·       Learning new design patterns, widgets, and user interfaces can be
confusing. The goal is to give users the ability to decide what works best
for them based on preference and ability. Personalization enable websites
to adapt to and meet the user's needs.

·       Extra support can be a distraction for people who do not need it,
so a robust solution requires the ability to increase or decrease levels of
complexity as people's skills improve or decline over time.

·       Ability to increase or decrease levels of complexity as people's
skills improve or decline over time.

·       Enable websites to adapt to and meet the user's needs.

Some users need extra support. This can include:

·       Symbols, iconography and graphics that they are familiar with

·       Tooltips or similar on-demand help or clue

·       Language they understand

·       Fewer or more constrained features

·       The ability to programmatically distinguish between native content
and third-party content on a page or screen

·       The ability to implement custom keyboard short cuts at the user-end

To achieve this, we need standardized terms and supportive syntax. These
can be linked to associated symbols, terms, translations and explanations.
They are then provided to an individual based on personal preferences.

*1.2 Use Cases*

Requirements for Personalization Semantics
elaborates many use cases that further contextualize the above summary of
user needs. These use cases form the basis of requirements for this

Examples include:

Assuming an author can make it programmatically known that a button sends
an email, and based on user preference settings:

·       The button might then render as an alternative term, and/or furnish
an additional tooltip that is understandable by the individual user.

·       It could automatically include F1 help that explains the send
function in simple terms.

·       It could be identified with a keyboard shortcut that is always used
for send (Submit).

In addition, the button could be identified as important and always
rendered or rendered in an emphasized form.

Another use-case is the use of Symbols. Some users might have a severe
speech and/or physical impairment and communicate using symbols, rather
than written text, as part of an Augmentative and Alternative Communication
(AAC) system. The use of symbols to represent words is their primary means
of communication for both consuming and producing information.

Symbol users face a wide variety of barriers to accessing web content, but
one of the main challenges is a lack of standard interoperability between
different symbol-sets, or a mechanism for translating how a concept is
represented in one symbol-set to how it may be represented in another

·       An assisted living home authors adult education courses and
life-skills content, for example, how to make dinner using a microwave.
Even within their core user-base, different users are accustomed to
different symbol-sets. The authors need to be able to create content for
all their users.

·       A large banking site wants people to be as autonomous as possible
while using their services. They have provided augmented symbol references
onto their core services so that the user-interface can be rendered usable
for users of symbol-sets, without specifying which symbol-set is being
used: they need to programmatically support multiple symbol-sets.

·       People who know different symbol-sets wish to talk to each other. A
government agency is making information sheets about human rights and
patient rights and are seeking feedback from impacted users. They add
symbols from a common symbol-set to support a majority of different users,
but they wish to also support people who use or require different symbols,
to enable them to both read the content, as well as edit it.

It should be noted that users who depend on symbols for daily communication
needs often also struggle the most with mistranslations, as they have
severe language disabilities. Inferring what was meant by using an
incorrect symbol will not be achievable for many users. This rules out
relying on machine learning until it is almost error free.

In another use-case, a user has dyscalculia and has difficulty
understanding numbers. They struggle with understanding websites that use
numbers to convey information. For this reason, the numeric information
must also be provided in an alternative format that the user can

·       The user wishes to get the latest weather report for their city and
goes to an online weather site. For the day’s forecast, it shows a high of
95℉ and a low of 40℉, which is not helpful for this particular user.
Allowing this numeric information to be presented instead as an image,
symbol, or as written text would benefit the user (i.e. instead of 95℉, a
picture of someone wearing shorts and a tee-shirt with the sun above or
simply a text alternative of “Very warm”, and instead of 40℉ a picture of
someone wearing a jacket with pants, or a text alternative of “Very cold”).

It is important to note that people with dyscalculia are often very good
with words, so long text can be better than short numbers.

Finally, consider someone with autistic spectrum disorder and with a
learning disability. They may be a slow reader but find numbers clear and
precise. They may go to the same website and find all the word and images
unclear and the animations cause cognitive overload. They want the same
information with more numbers and less words.

More examples can be found on
https://github.com/w3c/personalization-semantics/wiki/Use-cases. More
information on persona and user needs can be found in

Working examples of how this could be used in practice, with user
preferences, are available on the task force


*John Foliot* | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good

Received on Monday, 16 December 2019 17:55:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:44:01 UTC