Good afternoon James,
I think it might still be useful to do some human-screen-reader
testing on
the wire frames (i.e. where a human is the screen-reader). This
would be
easily accomplishable over the phone / skype and may reveal some
things
early on to make it easier for developers not to overlook
accessibility
related issues.
HTH,
Everett
Follow me on Twitter
http://twitter.com/ezufelt
View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt
On 20-Aug-09, at 5:31 PM, James William Yoon wrote:
It'd be awesome if we could do some early accessibility testing on
the
mobile app, but this is really dependent on when the developers
have a
functional prototype of the app.
In the interim, we were going to do a cheap faux-functionality
wireframes-in-screen test, where the user wouldn't actually be
looking
at text, but rather a mock image of the text (and of the screen
overall). It's unfortunate, but it really is a cheap, fast, and
effective option, albeit with the drawback that we can't do screen
reader testing on it.
Cheers,
James
On Thu, Aug 20, 2009 at 2:18 PM, Alison
Benjamin<[email protected]> wrote:
Hi,
The mobile app looks like a lot of fun to use :o)
I think we should take advantage of the iPhone's screen reader and do
UX testing with respect to this early on. I'm not deeply familiar
with
the design priorities for McCord but I think this will affect how
generalizable the app is.
Thanks,
Alison
On Thu, Aug 20, 2009 at 12:03 PM, James William
Yoon<[email protected]> wrote:
Just an update on what we're up to in terms of mobile design. We're
still building new screens, revising old ones, creating variations of
existing ones, and getting feedback and direction from Hugues
(McCord), Nicole (McCord), Nancy (SI American Art), and Titus
(Experius). One of our next steps is to start doing some user testing
of the wireframes.
In preparation for doing some of that user testing and demoing, we
have a couple of tasks ahead of us:
1. Write up the user testing protocol: Erin's been working on writing
up a testing protocol for our wireframes. They can found here:
http://wiki.fluidproject.org/display/fluid/Mobile+user+testing+protocol
; comments, revisions are very welcome as usual!
2. Set up the testing platform: we're planning to use
wireframes-in-screen testing to give faux-functionality, a la recent
publication by Bolchini (http://interactions.acm.org/content/?
p=1263).
In a nutshell, we'll have images of the wireframes on the mobile
device, with clickable hot spots which transition the user to the
next
appropriate screen (= image = wireframe). Jacob's helping us
maintain
a sense of the mobile experience by using the screen navigator to get
that sliding screen transition effect between screens.
Cheers,
James
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
