Mercator Mapping GUIs to Auditory Interfaces Goals z

Mercator Mapping GUIs to Auditory Interfaces

Goals z Provide transparent access to X Windows applications for computer users who are blind or severely visually impaired. y. Build a framework to monitor, model, and translate graphical interfaces of X Window applications without modifying the application. y. Develop a methodology for translating graphical interfaces into nonvisual interfaces.

Mercator Design Considerations z Modality for nonvisual interface -- auditory or tactile. y. Substantial research in auditory interfaces (Gaver, Bly, Blattner et al) y. Users’ ability to monitor multiple auditory signals - the “cocktail party effect” (Cherry) y. Active versus passive interaction y. Low cost, standard audio devices y. Users’ possible lack of tactile sensitivity due to diabetes

Modeling Visual Interfaces

Auditory Widgets z. Correct level of abstraction z. Convey objects … and attributes

Navigation z Support two activities y. Allow users to “scan” interface y. Allow users to operate interface z Mouse navigation is unsuitable z Map interface structure into hierarchical tree structure y. Based on widget hierarchy y. Users walk tree structure to navigate y. Works with existing keyboard short-cuts

Mercator Architecture z. Three Main Goals: y. Capture -- high-level semantically meaningful information from X applications. y. Store -- a semantic, off-screen model of the graphical interface. y. Translate -- the stored information to present a consistent alternative interface.

Spectrum of solutions z. Modify the applications z. Modify the toolkit z. Interpose between application and window server

First Architecture

Second Architecture

How this worked z. Xt hooks, RAP, Xlib safety net z. Control flow z. Interface modeling z. Interpreted interfaces z. Simulating input

How to do this now. . .