This Wiki page is edited by participants of the Cognitive and Learning Disabilities Accessibility Task Force. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Task Force participants, WAI, or W3C. It may also have some very useful information.

Adapting content for coga personalization

From Cognitive Accessibility Task Force
Jump to: navigation, search

Personalization (topic)


We need personalization because:

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

What are the tasks we need to be able to do

We want to be able to

  1. Add content - such a extra help and support
  2. Remove features - such as extra optional steps and content
  3. Change elements - such as using elements that this user know how t operate
  4. Address issues - such as implement appropriate safety protocols


We need to be able to add content and feature such as:

  1. Extra help
  2. Orientation information such as text that seas what you just did (you just selected priority shipping)
  3. Text to speech with highlighting
  4. Increase complexity as skills improve


We need to be able to remove or "hide" confusing elements, such as:

  1. extra or secondary features
  2. "special offers"
  3. adverts
  4. decrease complexity as skills improve

Note that all the information can be behind a "more" button or "legal" link. This will mean that all the information is still available - just not overwhelming.


User interface components to ones that the user know how to use such as:

  1. An “easy use” media player
  2. Standard dialogs, menus and widgets
  3. Standard icons for AAC users
  4. Started text, buttons and icons


Address extra issue such as:

  1. security and
  2. safe guarding

Ways this is done now

  1. User plug ins and software such as a text to speak enabled browser
  2. Web services that enable text to speech
  3. Browser options like auto-fill (which can get it wrong and add mistake)
  4. Add-on, toolbars or extensions will allow you to make Stylistic changes
  5. Extensions like Readability will remove adverts
  6. Simplify text
  7. Use the mobile web version
  8. Safeguarding and security currently is handled by having standard safety features are available for all users - or external products like parental controls or net nannys#Standard web personalization (note this is also a limitation because of personalized and advertised content can be confused with standard content)
  9. Haptic feedback (
  10. Live Chat help (can be intrusive and bad for ADD) (could be done not really now)
  11. Speach input like sire Google glass
  12. widget point software allow users to point to a word and get to a symbol


Doesn't address most what of what we need.

  1. No current of these allow using the user know symbols of a normal website with author specifying alternative symbol based rending -automated solutions like widget has ambiguity
  2. No way to switch
    1. an “easy use” media player
    2. Standard dialogs, menus and widgets
    3. Started text, buttons and icons
  3. Can not

Many users forget to use their AT or browser options, and want as little complex installations as possible Lack of additional help and support that is useful for Coga groups(allowing further support)

Frames block add-ons changing CSS via extensions

Semantic information

Personalization should allow for user override

Live Chat help boxes can be intrusive and complicate the page, need role or indi-ui term

Symbol support for interoperability:

  1. the noun project (icons)
  2. Max Laundal (concept coding framework)
  3. Arabic symbol dictionary
  4. ARASAAC symbol

Ways this could be done

  1. User CSS allowing an ARIA role for extra help to be loaded
  2. Aria or meta date link to dictionary in standard format- enables tooltips to be loaded with simple definitions
  3. GPII
  4. Fluid
  5. Create ARIA role for importance levels 1,2, and 3.
    1. Less important content is not loaded based on user settings or cloud settings.
    2. Aria Label? or title is used to provide text for a link which, when activated will allow the less important content to be shown. Such as title="legal" or title = "more offers"

Element names, Landmarks, Indi UI and ARIA roles can be linked to user preference interface.

  1. If there is an output we will need data binding