FluidInfusion widgets

The Product/Outcome
Exploitation Plans
Intellectual Property Rights
Technical & Socioeconomic considerations/challenges and impact
Collaborators and Future Work
Success stories

Fluid Infusion "Reorderer Family" - dragging an item of Column A to Column B or C

The Product/Outcome
  1. Title of (final) product/outcome: Fluid Infusion
  2. Developer (AEGIS beneficiary): IDRC
  3. Purpose/main functionality & intended use: Fluid Infusion is a set of dynamic web components, based on jQuery, designed for accessibility, flexibility, and usability. The intended use of Fluid Infusion is to create flexible, accessible and personalisable user interfaces for web applications. Fluid Infusion will also continue to be used as a research platform by the IDRC and others in the area of accessible web application design and auto-personalization. See more in D3.2.1a, D3.2.1c, D3.2.2, D3.2.3 and D1.4.2 (here).
  4. Platforms/Operating Systems/Devices:
    • Web browser supporting WAI-ARIA (e.g. Firefox v3.6+)
    • For users with severe visual impairments, we recommend either JAWS or NVDA (Keyboard-only testers do not need a screen reader)
  5. Main innovation and comparison to the State of the Art: The key innovations in Fluid Infusion v1.4 include improved use of WAI-ARIA to convey role and state information to screen readers and the ability to restyle the Infusion components on the basis of user preferences (UIOptions), especially in “compound widgets” that provide functionality beyond desktop-type widgets. Compared to the state of the art such as jQuery UI (http://jqueryui.com/) and others (see the line “ARIA compliant” at http://en.m.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks ), Fluid Infusion widgets tend to be more complex (e.g., controlling layout, etc.), make more extensive use of WAI-ARIA and have superior keyboard accessibility. The Dojo widget set (http://dojotoolkit.org/widgets ) does make effective use of WAI-ARIA and was also contributed to by the IDRC team.
  6. Restrictions:
    • Components will work best with browsers that support ARIA (e.g. Mozilla Firefox v.3.6+)
    • For users with severe visual impairments, we recommend either JAWS or NVDA
    • Users with disabilities should: a) be able to operate their assistive technology (AT) (if any) effectively and b) be experienced with accessing websites in general.
    • Developers must have experience building web applications (e.g., with jQuery UI)
  7. Maturity level/Stage: Fluid Infusion is fairly mature. The widget set is now in version 1.4, having received an accessibility upgrade of both its use of WAI-ARIA and its screen reader usability as part of the AEGIS project. The degree of its maturity is further demonstrated by the existence of meta-components within Fluid Infusion, such as UIOptions (http://fluidproject.org/releases/1.4/demos/uiOptions/demo.html ) that enable the components to be auto-customized at run-time by the end-user
  8. Open Source (Yes/No): Yes
  9. Download/info: http://www.fluidproject.org/products/infusion/
  10. End-user documentation: End user documentation is already provided for every component on the Fluid Infusion website.
  11. Contact details (of the principal developer): Colin Clark ( This e-mail address is being protected from spambots. You need JavaScript enabled to view it )
Exploitation Plans
  1. Uptake by Open Source community:
Intellectual Property Rights
  1. Intellectual property rights: None besides open source protection
Technical & Socioeconomic considerations/challenges and impact
  1. Possible market applications – further research: All sectors making use of dynamic web content
  2. Marketability: Fluid Infusion is marketable to some extent, and is in use production use by several organizations and applications, including SAKAI and ATutor. That said, Fluid Infusion is not a mainstream competitor to jQuery UI. Instead, it remains primarily a proof-of-concept and a research platform in use by such large international research projects as Cloud4All and the FLOE Project (http://floeproject.org/).
  3. Deployment (so far or near future): While free, Fluid Infusion can be considered “for sale” on the Fluid Infusion site (http://www.fluidproject.org/products/infusion/ ).
  4. Expected impact:
    • For developers: Infusion is an open architecture designed to put developers back in control of their application’s user experience. It includes a growing collection of UI components—reusable interactions that go deeper than most widgets. Created by a community of developers and interaction designers, Infusion components are built from the ground up with accessibility in mind in order to suit users’ personal needs. Infusion components can be easily adapted and reworked to suit developers' creativity. The Fluid framework provides an easy way to build JavaScript-based user interfaces that are highly flexible and reusable. Built using Web standards and the jQuery toolkit, Fluid Infusion provides a lightweight application development framework supporting simple Model View Controller (MVC) techniques. It provides support for common client-side development patterns, making it easier to write components with less code.
    • For users with disabilities: Each user can have a consistent, personally-optimized user experience that suits their diverse needs and works across tools.
  5. Customers: Blind (without useful residual vision), assuming they use a screen reader, motor impaired (upper limbs), assuming they use keyboard navigation (e.g., via conventional keyboards, adapted keyboards, scanning keyboards, voice control, etc.) and web application developers who wish to develop accessible applications for them.
  6. "Go-to-market approach": Fluid Infusion is already in the market, but we do not intend to market it extensively. Instead, we intend to continue to make use of it for a variety of research projects. In addition, the way accessibility was handled in the relatively complex Fluid Infusion components should help to inform future work with the vastly more commercially successful jQuery UI.
    “Friends of GNOME” has been key dissemination action for Fluid Infusion. Additional Canadian dissemination events are tentatively planned for 2012 and 2013. IDRC has dissemination through their AEGIS Project (Ontario) website (http://aegis.idrc.ocad.ca/). Also, through events organized at the IDRC, such as Accessibility Camp Toronto (http://www.accessibilitycampto.org/), during various tours of the IDRC by University, Government and Industry groups and as part of the OCAD Masters of Inclusive Design program (http://idrc.ocad.ca/index.php/workshops-aamp-trainings/masters-program).
    The Fluid Infusion widgets are being disseminated through the dedicated web site of Fluid project, where all subsequent releases can be found (http://www.fluidproject.org/products/infusion/). Are also used in the context of research projects such as GPII-Cloud4All(gpii.net), Decapod (https://sites.google.com/site/decapodproject/), CollectionSpace (http://www.collectionspace.org/), etc. Additional Canadian dissemination events are tentatively planned for 2013.
    The Fluid Infusion widgets will also be used in a new Fluid Video Player widget that can be accessed here. The Flexible Learning for Open Education (FLOE) project (http://www.floeproject.org/frontpage; http://wiki.fluidproject.org/display/fluid/OER+Commons+authoring+tool+high+fidelity+mockups+%28February%29) will be another opportunity for dissemination and exploitation.
  7. Commercialisation barriers: Fluid Infusion was not intended to be a mass-market product. Instead it was founded as an agile research and development platform that would easily enable innovation in the areas of interest to the Fluid Project community members (including the IDRC). As a result, community members are able to add and modify Fluid Infusion components much more quickly than they could effect change in a major mass market toolkit.
Collaborators & Future Work
  1. Collaborations: Fluid Infusion is developed by a community of developers, including developers from SAKAI and Uportal.
  2. Further research and development steps-future collaboration: Fluid Infusion continues to be developed as part of research projects, such as FLOE.(
Success stories FAQ
Please check at: http://wiki.fluidproject.org/display/fluid/Infusion+FAQ