Innovator ProfileNCTI's Innovator Profiles offer a closer look at the work and worlds of assistive technology designers, manufacturers, and distributors. Click here to view all Innovator Profiles. |
||
|
Tim Lalor Software Developer By Eric Morrison |
|
Description of technology: |
Ai Squared produces ZoomText, a premier screen magnification and reading solution for computer access. |
|
Finding out about needs: |
Tim says that inputs for development come both from internal ideas and external feedback. Often idea generation substantially leads the market. Chuckling, he relates, "We've got a bunch of bright guys here, and there are a lot of ideas floating around - more than there is time to execute." Many of those are deferred for practical reasons, including some cases in which features are not amenably measurable against potential market demand. Inputs from users often come directly from trade shows and the dealers, resellers, and key customers who frequent them. Ai Squared also benefits from alpha releases to small user test groups and keeps a tallied archive of features that real users request. As certain feature requests grow, they may drive the ability to resurrect an idea that was conceived earlier: “Those are the ones where when we finally get something from the field that we've been wanting to do… it provides the license to go off running and really make it work." |
|
Intrigued by: |
Tim is perpetually intrigued by “usability testing.” He says, “The core has been designed, the internal workings are ironed out… now its how it’s getting exposed. How do we get this technology to the user?” He stresses that Ai Squared “Separates the developer from the usability testing and feedback to ensure feedback isn’t tainted. ZoomText should be a natural extension of the user interface.” |
|
Seeing the world in new ways: |
Much of present development work is driven by the realization at Ai Squared that complex computer interactions generate from inputs that originate from the user and those coming from the computer system itself with its links to networks. This includes system messages, blinking indicators, and pop-ups. One of the challenges for ZoomText, therefore, is the management of attention itself: guiding the user's attention to the most critical activity occurring on the screen while remaining accountable to user intent. Of this “tracking,” Lalor says, “We try to figure out the right place to be (in terms of ZoomText's cursors and directional features) at the right time." This is a significant challenge since it is difficult to know all applications ZoomText users handle or to predict all contexts of use. |
|
On design principles: |
Tim emphasizes that ZoomText is a utility, not an application - "It enables you to use what you have on your machine - we try to be the conduit." Thus, he describes principles that guide design in terms of practical utility and transparency: “Are their expectations met with the machine – their word processor, email… less with our product. That’s my goal, that there’s no perception at all on their part (of ZoomText).” |
|
On users: |
He expresses the concerns of many AT designers in regard to the wide variety of needs that ZoomText’s users present: “I think the users are so varied that we try to meet so many needs. The concern I’ve had is that you may do less for so many more in living some things out.” Still, he emphasizes the positive feedback Ai Squared has received on many extended features. |
|
On training and use: |
He says that real challenge in final development is based more in compatibility with the plethora of platforms and applications than in actual use, but that design should be informed by a variety of inputs to make ZoomText powerful and intuitive to use. |
|
Views on the market: |
Tim talks about the challenges of meeting the needs of a mainstream market, and states an approach: “We could continue testing and fixing (to meet the needs of every type of user) and never release!” Thus, the emphasis shifts: “We try to hit the big core applications or application suites. Then we continue to evolve support outside of those.” As an example, Tim cites the need the company ultimately recognized for support of the Mozilla browser as it became more popular. |
|
Success indicators - making a difference: |
On success, Tim emphasizes the equalization potential in AT: “I'm thinking of people who call me when someone gets a job… we get a call from their employer saying, ‘We need this ‘ZoomText’ for this user - they can't work.’ This enables them. Once the missing piece is there, they're like the next guy. So I think, that's the key – they can do their work.” |
|
Wants to know more about: |
What Tim wants to know more about is simple – use and users: “Some of what I’ve struggled with is trying to nail down the specific use cases.” He cites a dearth of available information on practices: “I haven’t found a lot of documentation. Case studies! That’s one thing I could use!” |
|
On new horizons: |
One of the horizons Tim is interested in is the potential of the dual monitor market. He seeks to know user patterns in this arena: “How do users see themselves using that? How many users would actually make use of a second monitor or put in another [monitor] card? So that's been one we've struggled with." |
|
Provocative views & quotes: |
When asked if pre-service engineers receive adequate preparation in human factor design for persons with special needs, Tim responded, "No, I don't think you do." He recognized progress "by some groups" is being made, and qualified his position, saying, "You may get more of it nowadays, but I was never exposed to any of that." Overall, Tim sees most of design in the AT field as an extension of mainstream engineering principles - "It's figuring out how can we apply (those) ideas and techniques to a different group… apply them so that people can make use of something that exists (in mainstream engineering practice)." |
|