Google DTorial: An interactive tutorial framework for blind users in a Web 2.0 world - Manual (Page 7)

participants were shown DTorial as the first exposure, and nine were shown the
HTML version as the first exposure. DTorial went through five iterations, and
averaged four participants per cycle. Table 1 summarizes user demographics,
experience, and conditions. DTorial went through five major design and evaluation
cycles. Each cycle had 3-4 users. Revisions after each cycle were based directly upon
user feedback and researcher observation.
6. Findings from Design and Evaluation Cycle
From the incremental design and evaluation with 17 real world users, we analyzed the
behavior and design changes of DTorial and created a high-level interaction model.
This set of design requirements is based on the results from our users and our iterative
design and evaluation cycle.
At the conclusion of 17 studies, most participants were extremely positive about
the prospect of using DTorial for their day-to-day learning. Through the design cycle,
we noticed a distinctive shift in comments from users. Originally, feedback focused
on the difficulty in switching modes and the complexity of Web 2.0 applications. At
the conclusion of our studies, feedback was primarily about phrasing of the content,
what topics to discuss, and adding additional functionality for a more robust user
experience. Overall, 12 of our users wanted to use DTorial in their learning process.
Out of the 5 who did not, all but one used the earliest versions of our software,
without the benefits of our incremental improvements. Moreover, their concerns were
addressed and added to the success of the later iterations of DTorial. One participant
who teaches other VIUs said the following about DTorial:
This [interactive tutorial] is a very smoothly integrated
environment for learning and getting your task accomplish… I think
they are both good, but I think the learning curve will be a little bit
more [steep] in [the HTML tutorial]. – P7
The remainder of this section, we will focus on what Web 2.0 designers can do to
help incorporate tutorials into their applications.
6.1 User Found 3 Modes of Interaction Confusing
The first requirement is based upon users’ aggravation with the complexity of Gmail
when using a screen reader: not all functionality was evenly distributed between the
three Screen Reader modes. In Appendix A, we notice that users can always read in
VCM and can control the Web application in both VCM and PCM. To control some
features of Gmail, a mode switch was required (e.g., using a hot-key), while others
times, mode switches were optional (e.g., accessing a check box). One user
characterized this complexity by saying:
You have [the Virtual Cursor] off to read, and off to perform some
of the keyboard commands, and you have other commands that you
have to use when the virtual cursor is on, and then you have to
remember that you have to have the virtual cursor on to turn forms