Support Personalization

[lseeman]

Support Personalization

Enable personalization: Contextual information and author settable properties of regions and elements are programatically determinable so that personalization is available.

[Contextual information includes: context of elements; concept and role; relevance and information for simplification; position in a process.

Author settable properties includes: type of distraction, type of help, type of transaction and type of reminder, instructions and status of an element.] - note this could be in the main text or in the definition

Exception: Information does not need to be exposed when there is not a standardized way of exposing it in the technology or the platform.

Suggestion for Priority Level

(A)

Related Glossary additions or changes

    <dl>
      <dt>&nbsp;</dt>
      <dd>&nbsp;</dd>
      <dt>&nbsp;</dt>
    </dl>
    <dl>
      <dt><em>Contextual information</em></dt>

Defined terms and tags that give meaning to the content such as context of elements; concept and role; relevance and information for simplification; position in a process

Personalization

User interface that is driven by the individual user's prefrences.

Author settable properties

Properties that can be set by the author or by a script, such as: type of distraction, type of help, type of transaction and type of reminder, instructions and status of an element. Typical they set the type of the role or element at a second level taxonomy

    <p>&nbsp;</p>

What Principle and Guideline the SC falls within.

This could fall under:

WCAG 1 Perceivable - Guidline 1.3 Create content that can be presented in different ways (for example simpler layout) without losing information or structure

Or under:

WCAG 3 Understandable - Guidline 3.2 Make Web pages appear and operate in predictable ways.

Description

The intent of this success cryteria is to support user preferences or needs of the user. For example, having familiar terms and symbols is key to being able to use the web. However what is familiar for one user may be new for another requiring them to learn new symbols. Personalization could include loading a set of symbols that is appropriate for the specific user, ensuring that all users find the icons simple and familiar.
Technology holds the promise of being extremely flexible and the design of many systems includes the expectation that users will be able to optimise their interaction experience according to their personal preferences or accessibility requirements (needs).

Benefits

This Success Criterion helps users who need extra support or a familure interface. This can include:

        <ul>
          <li> Symbols and graphics that they are familiar with </li>
          <li> Tool tips </li>
          <li> Language they understand </li>
          <li> Less features </li>
          <li> Separating advertisements, so they do not confuse them with native content </li>
          <li> Keyboard short cuts </li>
        </ul>

We need personalization because:

        <ul>
          <li>Different user needs can conflict </li>
          <li>Learning new design patterns (and widgets) can  be confusing - we want to allow users to stick with what works for them </li>
          <li>Extra support can be annoying to people who do  not need it </li>
          <li>Making content predictable is necessary for  accessibility but can often be considered boring design </li>
          <li>Ability to change levels of complexity (increase  or decrease) - As people skills improve or decrease over time or context. </li>
          <li>Enable us to really meet the user needs </li>
        </ul>

This helps people with many diffrent cognitive disabilities including people with:

        <ul>
          <li>Language related disabilities </li>
          <li>Memory related disabilities </li>
          <li>Focus and attention related disabilities </li>
          <li>Disabilities that effects  executive function and decision making </li>
        </ul>

Togther this can effect 11% of school age people and over half of people over 60 years old - including mild cognative imparment an Age-Associate Memory Impairment (AAMI).

Research on these benefits can be found at [cudd-1] and the task forces issue-papers on personalization and preferences. Also see the example of an adaptive page.

  <h3 id="resources">Related Resources</h3>

Resources are for information purposes only, no endorsement implied.

      <ul>
        <li> Open source project of  <a rel="nofollow" href="https://github.com/ayelet-seeman/coga.personalisation/tree/Script-Options">example script</a> that a web author can use or include that read the user settings   in the JSON files and adapt the page for the user needs example script and <a rel="nofollow" href="https://github.com/ayelet-seeman/coga.personalisation/tree/ExampleWebPage/">example of adaptive page</a></li>
        <li><a href="https://rawgit.com/w3c/coga/master/issue-papers/personalization-preferences.html">Issue-papers on personalization and preferences</a></li>
        <li><a href="https://rawgit.com/w3c/coga/master/gap-analysis/#table-7-clear-and-understandable-content-and-text">Gap analysis Table 7 - Clear and understandable content and text </a></li>
        <li> <a href="https://rawgit.com/w3c/coga/master/gap-analysis/table.html/#table-6-familiar-interface">User needs Table 6 (less polished but more up-to date version)</a></li>
        <li><a rel="nofollow" href="https://w3c.github.io/wcag/coga/user-research.html">Background research document</a></li>
        <li> <a rel="nofollow" href="https://rawgit.com/w3c/coga/master/issue-papers/links-buttons.html">Semantics for adaptive interfaces</a></li>
      </ul>
    <p>.</p>
    <h2><a id="user-content-testability" href="https://github.com/w3c/wcag21/wiki/Proposals-for-new-Success-Criteria#testability" aria-hidden="true"></a>Testability</h2>

General test

For HTML and Web Content

Step 1. Identify the role of elements

    <p>Step 2. Identify the context of  regions and controls </p>
    <p>Step 3. Check that the context and role is clear from the markup - if not add the role and context from native HTML, ARIA and COGA (where it is supported)</p>
    <p>Step 4. Ensure content conforms to those standards where they can be used for personlisation or additional support.and set the applicable auther settable properties</p>
    <p></p>
    <h2><a id="user-content-techniques" href="https://github.com/w3c/wcag21/wiki/Proposals-for-new-Success-Criteria#techniques" aria-hidden="true"></a>Techniques</h2>
    <p>&nbsp;</p>
    <p><strong>Techniques include: </strong></p>
    <ul>
      <li>Use semantics and standardized techniques to provide extra help (<a href="https://rawgit.com/w3c/coga/master/techniques/index.html">COGA Techniques</a> 4.1).</li>
      <li>Provide semantics that symbols on key content (<a href="https://rawgit.com/w3c/coga/master/techniques/index.html">COGA Techniques</a> 4.2)</li>
      <li>Enable user agents to find the version of the content that best fits their needs.</li>
      <li>Use of aria-invalid and aria-required</li>
      <li>Use of aria epub on document content</li>
      <li>Use of aria landmarks - but with coga context where supported </li>
    </ul>
    <div>
      <h3 id="Failures">Common Failures for Success Criterion</h3>
      <p>The following are common mistakes that are considered failures of Success Criterion 3.1.1 by the<acronym title="Web Content Accessibility Guidelines"> WCAG</acronym> Working Group.</p>
      <ol>
        <li>standardized semantics for personalization were appropriate and not used.</li>
        <li>standardized platform technique for personalization were appropriate and not used.</li>
      </ol>
    </div>

 

Examples of Success Criterion 3.1.1

(May be added after December 1st)

• Example 1. An app for the heating system that has terms and icons on that the user does not understand, and has many options that makes it overwelming

  Also see the example page at http://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html

   

   

   

    <section>
    <div>

Working groups notes

    <p>old wording - </p>
    <p>Use <a data-link-type="dfn" href="https://rawgit.com/w3c/coga/master/extension/index.html#dfn-semantics">semantics</a> and <a data-link-type="dfn" href="https://rawgit.com/w3c/coga/master/extension/index.html#dfn-safe-standardized-techniques">safe standardized techniques</a> that enable the content to be adapted to the user scenario including <a data-link-type="dfn" href="https://rawgit.com/w3c/coga/master/extension/index.html#dfn-enabling-additional-support">enabling additional support</a> and <a data-link-type="dfn" href="https://rawgit.com/w3c/coga/master/extension/index.html#dfn-personalization">personalization</a>. </p>
    <p>&nbsp;</p>
    <p>An alternative way to word this would be to require personalization support for a full list of items, such as familiar icons, text, simplification , less options, extra help etc. This seemed more scary for authors and would limit the form of personalization away from how the user wants specific information handled. However it may be worth revising.</p>
    <p>&nbsp;</p>
    <p>&nbsp;</p>
    </div>
    </section>