Content simplification

Chalghoumi, Hajer hchalghoumi at ocad.ca
Tue Jul 5 18:07:28 UTC 2011


Hi all,

Some weeks ago, I prepared this text on educational digital content simplification.  As I explain in the text, the work aims to help digital content developers understand a little more about how to make content accessible to students with cognitive limitations or low reading achievement. 

This work is vey parctical and has a solid research background. I think the guidelines it contains can be  complementary to those you are developping and to the existing ones dealing with physical, connectivity and interface levels of accessibility.

Please have a look to it and contact me if you need any further info about it.

Have a nice day.


________________________________________
From: fluid-work-bounces at fluidproject.org [fluid-work-bounces at fluidproject.org] on behalf of Clark, Colin [cclark at ocad.ca]
Sent: Monday, July 04, 2011 5:08 PM
To: Fluid Work
Cc: D'Souza, Michelle; Antranig Basman
Subject: Content simplification demo

Hi,

James, Antranig, Michelle and I are experimenting with a demonstration of content simplification using UI Options and Infusion. Our initial idea, which we'd like to use as a practical starting point for examining the issue in more depth, is to provide a "simplicity spectrum slider" in UI Options. This slider will enable users to dynamically adjust the degree of distraction reduction in the user interface, media, content sections, etc. For our first iteration, the page's layout will be preserved, but users will be able to "turn off" distractions based on their personal needs.

James has started some really nice wireframes here:

http://wiki.fluidproject.org/display/fluid/Content+simplification+conceptualization

Michelle, Antranig and I are going to dive in and start implementing this as a demo we can showcase during presentations about Floe and the GPII over the next little while. Here are some of our to dos:

 * Look into new HTML5 semantics and see if there is a clear match with importance hierarchy
 * Investigate strategies for automatic dimming of sections using CSS3
 * Implement a static HTML page based on the wireframes
 * Build multiple stylesheets within three categories:
     1. The page's default look and feel
     2. Some basic, out of the box "dimmer" styles
     3. Page-specific refinements to #2

Since we don't want to get in the way of the impending Infusion 1.4 release, we'll fork UI Options work on this feature independently from the rest of the release.

This really is just the tip of a very interesting iceberg, which we'll continue to explore as we dive deeper into the process of user interface personalization. I can imagine that, for example, we should be able to use this same importance hierarchy with the Renderer to produce simplified versions of a full HTML page tailored specifically for mobile, etc.

Colin

---
Colin Clark
Lead Software Architect,
Inclusive Design Research Centre, OCAD University
http://inclusivedesign.ca

_______________________________________________________
fluid-work mailing list - fluid-work at fluidproject.org
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Guidelines for text simplification- version Fluid2.pdf
Type: application/pdf
Size: 431889 bytes
Desc: Guidelines for text simplification- version Fluid2.pdf
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20110705/fdc1d9cb/attachment.pdf>


More information about the fluid-work mailing list