MouseTrap Requirements
(Difference between revisions)
Heidi.ellis (Talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | == | + | ==Questions for A11y Community== |
| + | * Do we need to implement focus on forehead or elsehwere? | ||
| + | * How to account for spasticity -- should this be a priority or worked on down the road? | ||
| + | * There are a number of features in Mousetrap that never worked in the first place, but intended for future development (finger-tracking, plug-in architecture), should those be preserved, or scrapped? | ||
| + | * Interface -- should it be simple, or full-featured? Should it simply be a program that moves the mouse with head movements, and leave the other features to other applications (Dasher and built-in on-screen keyboard and so forth)? | ||
==Requirements== | ==Requirements== | ||
Revision as of 17:40, 11 September 2013
Questions for A11y Community
- Do we need to implement focus on forehead or elsehwere?
- How to account for spasticity -- should this be a priority or worked on down the road?
- There are a number of features in Mousetrap that never worked in the first place, but intended for future development (finger-tracking, plug-in architecture), should those be preserved, or scrapped?
- Interface -- should it be simple, or full-featured? Should it simply be a program that moves the mouse with head movements, and leave the other features to other applications (Dasher and built-in on-screen keyboard and so forth)?
