RE: Free Chrome extension for personalization

I believe that it works – but from the user perspective what it does is completely impossible to determine (and hence very confusing).

I just checked the 21 other Chrome plugins that I have and all but one produce either a menu, cascading menu or some form of dialog box. The exception is Clearly which completely re-writes the page in a clear simply formatted way – something the user cannot miss!

When I click on the personalization plugin all I get is a button animation that shows that the click has been received. To most users this would appear to be a broken plugin. There is no way for the user to know that the plugin is what loads the button at the top of the screen. If the plugin provides no interactive functions then it is very confusing that it appears alongside all of the other interactive plugins.

So if we want to convince people that the plugin approach is an effective way to go, we need to either:

  *   Find a way to hide the plugin in the set of installed plugins or;
  *   Ensure that instead of adding options (like the Skin 1 button) to the page, and potentially disrupting its on-screen appearance, they should appear as menu options or dialog boxes  linked to the plugin (as is the standard plugin behaviour).

Basically, we need to demonstrate a plugin that conforms as best as possible to our own guidance on consistency and conforming to user expectations – otherwise we will be increasing the cognitive complexity not reducing it.

Best regards


From: lisa.seeman []
Sent: 09 February 2017 13:38
To: Michael Pluke <>
Cc: EA Draffan <>; public-cognitive-a11y-tf <>; W3c-Wai-Gl-Request@W3. Org <>
Subject: Re: Free Chrome extension for personalization

Mike, it works. It loads a button for the first personalization skin that we have (at the top of the page). You press it and the page becomes personalized according to the JSON profile. However it needs pages to use the semantics we have proposed. We can put in your interface recommendations into the next version.

so far not many pages use the sematics (understatement) . That would change if we move ahead with the relevant SC's, and also now place like were EA works can start adding it to their content they want to use and letting the plugin do the adapting the content for them.

Also places are implementing priority versions that will be much nicer.

I am happy to have a call and talk you though what it does and how to use it and here any more feature requests
All the best

Lisa Seeman

LinkedIn<>, Twitter<>

---- On Thu, 09 Feb 2017 14:19:22 +0200 Michael Pluke<<>> wrote ----
This is a plugin designed to help people with cognitive impairments yet, if I understand you correctly, it operates in a uniquely unusual way: by making a "Skin 1" button appear on the Web page. Presumably if there were multiple skins these would appear as options on the page.

I realise that this is an early proof of concept attempt, but I think that a plugin that does nothing when you click on it would seriously confuse most users who expect a plugin to offer a menu of functions when you click on it. I would expect it to offer me ways to personalize the appearance/behaviour of the Web page I'm on.

One problem with implementing normal plugin behavior could be that many users with cognitive impairments may not be familiar with how to interact with plugins to achieve special functionality, as they are already struggling with the basic functionality provided by the sites they visit.

If the plugin is only there to provide code to a webpage (which presents the personalization options), then it shouldn't appear as an apparently broken plugin alongside other normal plugins as it will just confuse users (as it did me).

Best regards


Get Outlook for iOS<>

From: lisa.seeman <<>>
Sent: Thursday, February 9, 2017 8:51 am
Subject: RE: Free Chrome extension for personalization
To: Michael Pluke <<>>
Cc: EA Draffan <<>>, public-cognitive-a11y-tf <<>>, W3c-Wai-Gl-Request@W3. Org <<>>

It contains the same open source script as the demo page. You can run the script either by pressing the "skin 1" button that shows at the top of the page when the extension is loaded, or by running the button that was on the original demo.

The point of the extension is it is a freely available download and the author does not have to include the script themselves. If I was an author I would use the include becuse then the author maintains control. However I do not think people felt that was interoperable enough and it has to also ne a free download.

WHat I would really like is for the LVTF to make a few skins for their user groups :)  Wayne, are you interested?

I am happy to help (but possibly after feb 23rd)
All the best

Lisa Seeman

LinkedIn<>, Twitter<>

---- On Thu, 09 Feb 2017 00:25:11 +0200 Michael Pluke<<>> wrote ----
These are useful illustrations of the personalisation-driven simplification. However, my problem is that:

  *   The  demo page operated like this prior to the chrome extension;
  *   It continues to work like this whether the chrome extension is enabled or disabled;
  *   Clicking on the chrome extension doesn’t seem to do anything.

Best regards


From: EA Draffan [<>]
Sent: 08 February 2017 19:49
To: lisa.seeman <<>>; public-cognitive-a11y-tf <<>>; W3c-Wai-Gl-Request@W3. Org <<>>
Subject: RE: Free Chrome extension for personalization

I have mocked up a quick collection of Powerpoint slides to illustrate Lisa's personalisation app.

Best wishes

Mrs E.A. Draffan
WAIS, ECS , University of Southampton
Mobile +44 (0)7976 289103<><>

From: lisa.seeman [<>]
Sent: 08 February 2017 14:19
To: public-cognitive-a11y-tf; W3c-Wai-Gl-Request@W3<http://mailto:W3c-Wai-Gl-Request@W3>. Org
Subject: Free Chrome extension for personalization

Today I made a Chrome extension for the personalization project

Personalization getting started<><>
it is under accessibility. it is for free.
If you want a page to test it you can use
It is a bit basic (I made the icon in paint..) but IBM are also intending to make one later in the year that will have a more professional look to it.

Note the core script is being refactored (by Thaddues) to work with the updated semantics at That should be ready by Monday

The core opensource script can be injected by the author in one line of code meaning the personalization will be available to any author who want so to use it, even if the user does not have the extension.

please let me know if we feel more implementation is needed at this point

All the best

Lisa Seeman

LinkedIn<><>, Twitter<><>


Received on Thursday, 9 February 2017 14:17:43 UTC