W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > June 2015

RE: personalistion for the gap annalisis

From: Rochford, John <john.rochford@umassmed.edu>
Date: Sun, 28 Jun 2015 16:07:26 +0000
To: "lisa.seeman" <lisa.seeman@zoho.com>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Message-ID: <55BD19D83AA2BE499FBE026983AB2B583941DF1C@ummscsmbx01.ad.umassmed.edu>
Hi Lisa,

What is the significant advantage to merging those three papers? I ask especially because I’m always thinking of cost/benefit. Why would the work needed to merge the three papers be worth the effort compared to leaving them separate?


John Rochford<http://profiles.umassmed.edu/profiles/display/132901>
UMass Medical School/E.K. Shriver Center
Director, INDEX Program
Instructor, Family Medicine & Community Health
Twitter: @ClearHelper<https://twitter.com/clearhelper>
[Facebook Button]<http://www.facebook.com/pages/New-England-INDEXShriver-CenterUMass-Medical-School/227064920160>[Twitter Button]<https://twitter.com/NEINDEX> [WordPress Logo] <http://www.disabilityinfo.org/blog/>

From: lisa.seeman [mailto:lisa.seeman@zoho.com]
Sent: Wednesday, June 24, 2015 9:03 AM
To: public-cognitive-a11y-tf
Subject: personalistion for the gap annalisis

short review of :
•  adapting content for coga personalization<https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Adapting_content_for_coga_personalization> ,Gathering User Preferences<https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Gathering_User_Preferences>, Syntax for adaptable links and buttons<https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Syntax_for_adaptable_links_and_buttons> and portable preference

Firstly we would like to merge these papers.

GPII - cog a is potentially support but not yet,as
a, it is not yet  well supported and implemented
b, tools are on sensory accessibility and not coga.
Similar conclusion for  ISO/IEC 24751, (Individualized adaptability and accessibility in e-learning, education and training.  Part 1: Framework. Part 2: Need and Preference Terms Registration.  Part 3: Core Application Profile.

However we feel GPII will incorporate what we do when we do it

The plan is that the JSon and scripts in  "easy personalistion" can address most of what is described in adapting content for coga personalization<https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Adapting_content_for_coga_personalization> and then we can relie on GPII to address portable preferences in the future.

Missing from our roadmap and techniques - enabling the  use  to replace  widgets/ components like video player, whilst keeping the content the same. This will enable a player to be  loaded that the user understands how to work. idealy this should work with
mavis or Brian (new projects https://github.com/OpenDirective/brian)within our Json notation. This needs to enclude player settings such as diffrent levels of complexity.
We also need to address graded help for json

All the bestLisa Seeman
Athena ICT Accessibility Projects <http://accessibility.athena-ict.com> LinkedIn<http://il.linkedin.com/in/lisaseeman/>, Twitter<https://twitter.com/SeemanLisa>

Received on Sunday, 28 June 2015 16:07:56 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:53 UTC