Engage 0.3 Development Phases

Code entry areas not accessible to VoiceOver

Warning icon does not appear when users enter an invalid object code on the Object Code Entry screen

Empty bar appears below the navigation bar on an empty My Collection

Create, edit, and update unit tests for Engage 0.3

2

open

Document the API's for our components, framework , CSS, and data feeds.

open

Create a readme for the Engage release

open

Code cleanup and linting before release

open

Ensure all Engage-related components are correctly named and namespaced

open

Promote ScreenNavigator, NavigationList and Cabinet from Engage to Infusion

open

Upgrade to jQuery 1.4.2 and jQuery UI 1.8

0.75

open

TOTAL

2.75+

Cabinet headers are announced as heading level 2. VO user wouldn't know that he/she can expand it.

0.5

resolved

Screen focus not adjusting after expanding/collapsing of panels/descriptions

1

open

Implement a refresh method for cabinet

1

open

Create desktop friendly styles for Cabinet

1

resolved

Remove unnecessary options from cabinet

0.5

resolved

Refine and update the demo for the Cabinet component

0.5

open

Remove shelves from cabinet

resolved

Cabinet doesn't implement all of the necessary aria roles

resolved

TOTAL

4.5+

Create desktop friendly styles for Nav List

1

open

Refine and update the demo for the Nav List component

0.5

open

Implement a method for transforming models within the Nav List

0.5

resolved

Implement support for showing captions while in grid view

1

open

Change the navlist to not be dependent on the engageRenderUtils.js file

resolved

TOTAL

3

Review API of mFSS

0.5

open

Compile current engage specific css into an Engage mFSS theme

open

TOTAL

0.5+

Loading circle image is flickering for a second as a blank square, before loading.

0.5

open

Users should be shown a "loading..." screen when pages take a noticable amount of time to load

0.5

open

Roll the screen navigator into the mFSS demo

0.5

open

Add page transitions css effects into the screen navigator

2

open

Implement client-side document parsing

1

open

TOTAL

4.5

The Engage data mapping infrastructure is poorly factored, causing repetitive code and subtle musem-specific schema assumptions

open

Improve Engage's data access layer, removing redundancy across services

open

Data in CouchDB should be stored in the single database in order to allow fancy view manipulations (join, etc.).

open

TOTAL