/
IDI - Initiative Descriptions

IDI - Initiative Descriptions

May 13, 2011

Description Template

This is a template for descriptions for IDI initiatives. "Initiatives" encompasses projects, guides, tools, and other resources.

Draft 1

General Metadata

  • Initiative name: name of the project, resource, tool, or guide (Ex. "Decapod", "Inclusive Learning Handbook").

  • IDI Cluster: the IDI cluster(s) that best classify this initiative.

    • Development and design

    • Business case, policies, standards, and legislation

    • mobile & pervasive computing

    • implementation & information practices

  • Scope: keywords for the domain(s) in which the initiative operates.
    Example keywords:

    • health

    • inclusive education

    • knowledge sharing

    • mobile computing

    • GNOME end-user

    • literature

    • culture and the arts

    • civic engagement

  • Execution: keywords describing how the solution is implemented.
    Examples

    • personalization

    • transformation

    • digitization

    • guidance

    • community process

  • Technology: keywords describing the tools or techniques used in the execution.
    Example keywords:

    • OCR

    • stereoscopic 3D dewarping

    • Web

    • Javascript

    • Power Point

  • Output / Effect: what is generated by the initiative.
    Examples:

    • resource

    • tool

    • guide

    • assessment

    • community engagement

    • exemplar

    • "Design Handbook"

  • Standards and Specifications Implemented or Affected.
    Examples:

    • WAI-ARIA

    • ATAG 2.0

    • WCAG 2.0

    • ISO / IMS

  • Effect on inclusive design / IDI: how the initiative contributes to or involves inclusive design.

Project Specific Metadata

  • Contacts, friends, potential partners: people or groups the project is acquainted with or plans to collaborate with.
    Example:

    • For Decapod, this may be the Internet Archive, or Google Books.

  • Partners: Parties that contribute resources to the project.

  • Funders: The primary funders for the project.

  • Team Members

  • Communities:

  • Platform: The environment which this initiative is delivered / developed upon.
    Example

    • "Firefox on Ubuntu"

    • "PowerPoint"

    • "Web"

  • URL

  • Status: completed, needs funding, in progress, etc.

Example: Decapod

IDI Cluster:

  • development and design

Execution:

  • accessibility, information access, digitization, preservation, OCR

Scope:

  • literature, rare and fragile books.

Focus:

  • digitization of rare and fragile books using off-the-shelf low-cost hardware, and making the text usable in different applications.

Technology:

  • OCR, digitization, web, Firefox, ubuntu, gphoto, cameras / imaging, stereoscopic 3D dewarping

Partners:

  • DFKI, IDRC, JSTOR

Communities:

  • Ocropus, Decapod,

Contacts / Friends / Potential partners:

  • Nigeria, Karl Fogel, Book Liberator, etc. ("Friends"), IA

Team members:

  • CC, JH, JM, TB

What does it contribute to Inclusive Design / IDI:

  • Increased access to text that would otherwise been inaccessible.

Example: Peptalk

IDI Cluster:

  • development and design

Execution:

  • cultural personalization / customization, patient empowerment, education prescription,

Scope:

  • digital resources, health management, self-care, education

Focus:

  • customization of educational content for patient self-management of health care issues.

Technology:

  • web, LOR, XML, ISO/IMS

Standards:

  • ISO/IMS

Partners:

  • George Brown College, UHN, Peptalk Project.

Communities:

Contacts / Friends / Potential partners:

What does it contribute to Inclusive Design / IDI:

  • Brings inclusive design to area of patient self-management, health care, and education.

Example: GNOME ScreenMagnifier

IDI Cluster:

  • development and design

Execution:

  • accessibility

Scope:

  • GNOME desktop, end-user, adaptive technology

Focus / Description:

  • Screen enhancement for the GNOME desktop.

Features:

  • font manipulation, colours, brightness and contrast, magnification

Technology:

  • GNOME, GNOME shell, OpenGL, JavaScript, Clutter

Standards:

  • n/a

Partners:

  • AEGIS Europe, Ontario Research Fund,

Funder:

  • AEGIS

Communities:

  • GNOME Accessibility group, GNOME

Contacts / Friends / Potential partners:

  • Peter Korn / Oracle

Team members:

  • JS, JR, LH

What does it contribute to Inclusive Design / IDI:

  • A tool for allowing more inclusivity in existing applications.

URL:

  • live.gnome.org/GnomeShell/Magnification

Example: Unesco / ADOD

IDI Cluster:

  • Business case, policies, standards, & legislation; Implementation & information practices

Execution:

  • accessible office documents, accessible word processor, accessible spreadsheet, accessible presentation

Scope:

  • Digital office application suites and the documents that they produce

Project Focus:

  • Developing (1) an assessment framework (based on W3C-WAI’s WCAG and ATAG) for determining the accessibility of office documents and applications,

  • (2) user-friendly guidance to help users of existing office applications produce more accessible documents,

  • (3) and assessments of the accessibility of common office application suites.

Technology:

  • Digital office document formats.

Standards:

  • WCAG 2.0; ATAG 2.0

Partners:

  • UNESCO, Government of Ontario

Communities:

  • Office document users (e.g., business, government, education, etc.)

Contacts / Friends / Potential partners:

  • Many potential (developers, groups interest in translation such as Jeroen Baldewijns, Christophe Strobbe, Catherine Roy)

Team members:

  • Jan, Sabrina

What does it contribute to Inclusive Design / IDI:

  • Excellent AODA resource. Demonstrates our ability to identify and deliver solutions in important areas of accessibility.

URL: http://adod.idrc.ocad.ca/