New keyboard accessibility plugin demo - Image Viewer design

Jonathan Hung jhung at ocad.ca
Wed Oct 20 16:01:48 UTC 2010


Hi everyone,

With the date of the 1.3 release pushed back (Justin is going to send an
email about this shortly), we now have time to implement a new demo for the
keyboard accessibility plugin.

If following this email thread, this would be Option #1 mentioned in
Anastasia's email sent on October 18.

I will be updating the wireframes and will send the latest version to this
mailing list for feedback.

Thanks!

- Jonathan.
---
Jonathan Hung / jhung at ocad.ca <jhung.utoronto at gmail.com>
IDRC - Interaction Designer / Researcher
Tel: (416) 977-6000 x3959
Fax: (416) 977-9844



On Tue, Oct 19, 2010 at 4:38 PM, Jess Mitchell <jessmitchell at gmail.com>wrote:

> Nice!  I like the example.  And thanks AC for the link ;)
>
> Jon, are you imagining if we go the direction of '2b' that we'd tighten the
> example up a bit -- for instance, there is a lot of text on those pages that
> isn't necessarily necessary for demonstrating the tab keyboard piece.  Or
> perhaps I'm assuming it's just the interactions among the tabs that is
> particularly interesting...
>
> ?
>
> J
>
>
>
> On Oct 19, 2010, at 9:37 AM, Jonathan Hung wrote:
>
> > Hi Anastasia,
> >
> > I'm good with Option 2b and cleaning up the example where needed.
> >
> > - Jonathan.
> >
> > ---
> > Jonathan Hung / jhung at ocad.ca
> > IDRC - Interaction Designer / Researcher
> > Tel: (416) 977-6000 x3959
> > Fax: (416) 977-9844
> >
> >
> >
> > On Mon, Oct 18, 2010 at 2:23 PM, Cheetham, Anastasia <acheetham at ocad.ca>
> wrote:
> >
> > Jon and I reviewed his Gallery Viewer mock-up this afternoon and
> discussed some tweaks to the keyboard interaction. I think this will be a
> good demo of the keyboard accessibility plug-in.
> >
> > Our question now is with the timeframe for implementing it. Justin's goal
> for code freeze is Wednesday this week i.e. two days. That's a bit tight to
> implement an exemplary demo from scratch. Justin favours postponing it to
> 1.4, but then that leaves us with the question of what to do for a
> keyboard-a11y plug-in demo for 1.3 (since the current portal demo is
> broken).
> >
> > So our options seem to be:
> >
> > 1) Focus on implementing an all-new demo, and get something completed in
> time for code freeze.
> >
> > 2) Postpone the new demo 'til the next release, and either
> >
> >  a) remove the current not-working portal demo (and put in a "Coming
> Soon" sign), or
> >
> >  b) use Colin and James' Philosophy Lesson demo as a temporary portal
> demo for 1.3, to be replaced in 1.4 with the Gallery Viewer.
> >
> > Personally, I favour option 2b, but I'm wondering what other people
> think.
> >
> > --
> > Anastasia Cheetham     Inclusive Design Research Centre
> > acheetham at ocad.ca            Inclusive Design Institute
> >                                        OCAD University
> >
> >
> > _______________________________________________________
> > fluid-work mailing list - fluid-work at fluidproject.org
> > To unsubscribe, change settings or access archives,
> > see http://fluidproject.org/mailman/listinfo/fluid-work
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20101020/7ab15961/attachment.html>


More information about the fluid-work mailing list