Milestones

Milestone 1

Goal

Create a beta version of the tool which allows a user to perform an accessibility analysis on the current document or presentation and fix accessibility errors uncovered by this analysis.

Scope

For this version, we will focus on getting through an entire workflow of using the tool rather than detecting and fixing all types of accessibility errors. As a result, we will only detect a subset of accessibility errors:

Word

  • Alternative text for images
  • Titles should be the first piece of content within a document

PowerPoint

  • Alternative text for images
  • Non-empty title for each slide

Workflow

The workflow that this beta version will be centered around creating is:

  1. Analysis - parsing through document or presentation and finding accessibility errors
  2. Summary - present user with summary of errors and allow them to select and highlight individual errors on the current document or presentation
  3. Correction - present user with options to fix the given error (i.e. if an image is missing alternative text, present a text-box where she can type in a brief description of the image)

Tasks

Word

Much of the work is already done for Word. We can detect both types of errors. However, we still need to complete the last two steps in the workflow.

  1. Ensure that rules for detecting best practice violations are complete for both types of errors.
  2. Plug these in to backend module. Backend information can be found here.
  3. Develop GUI aspect to display a summarized view of accessibility errors.
    1. Alternative text - 5/17 images don't provide alternative text
    2. Title first content in document - Simply provide "Yes" or "No" as to whether the style "Title" is applied to the first piece of content within a given document.
  4. Translate between our XML view of the document and the object model view of document
  5. Use given translation to allow user to select an accessibility problem and highlight the problem area
  6. Provide a way to fix the accessibility problems and manipulate the actual object model
    1. Alternative text - Provide text box to enter description of the image
    2. Title first content in document - select the content that is above the title tag and give the user the option to move the content, delete the content, or to make the selected content the new document title.

PowerPoint

The progress on this module is far behind Word development. We currenlty can only detect one of the two types of errors.

  1. Write detection modules for the remaining error type: alternative text for images
  2. Plug the two detection modules into a backend module. Backend information can be found here.
  3. Develop GUI aspect to display a summarized view of accessibility errors.
    1. Alternative text - 5/17 images don't provide alternative text
    2. Non-empty title for each slide - 6/23 slides don't provide titles
  4. BLOCKER: Due to the nature of how PowerPoint presentations are structured, we can't simply get all of the OpenXML of the presentation through a simple property. We must in fact use the OpenXML SDK (completely separate) to parse the individual slides. This development is being done by Brett and is outlined here: Parsing PowerPoint presentations.
  5. Translate between our XML view of the presentation and the object model view of the presentation
  6. Use given translation to allow user to select an accessibility problem and highlight the problem area
  7. Provide a way to fix the accessibility problems and manipulate the actual object model
    1. Alternative text - Present to the user a dialog box into which she can enter the description of the image
    2. Non-empty title for each slide - Present to the user a dialog box into which she can enter a title for the slide. Place the newly created title box on the slide and allow the user to position it as she sees fit.
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License