New keyboard accessibility plugin demo - Image Viewer design

[Jonathan Hung]

Hi Jan,

That's an excellent suggestion, but I don't think the keyboard plugin
supports hotkeys at the moment. We can add hotkeys separately, but may risk
confusing it with the functionality of the keyboard plugin. I think there
was some talk about hotkeys, but I'm not sure if that is a feature that is
planned. I would support the idea of adding hotkey support to the keyboard
plugin - it seems logical.

I think we should leave hotkeys out of the demo for now.

---
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 Thu, Oct 21, 2010 at 3:59 PM, Richards, Jan <jrichards at ocad.ca> wrote:

>  For the star setting, maybe also allow pressing “1”, “2”...?
>
>
>
> Cheers,
>
> Jan
>
>
>
> --
>
> (Mr) Jan Richards, M.Sc.
>
> jrichards at ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
>
> Inclusive Design Research Centre (IDRC) | http://inclusivedesign.ca/
>
> Faculty of Design | OCAD University
>
>
>
> *From:* fluid-work-bounces at fluidproject.org [mailto:
> fluid-work-bounces at fluidproject.org] *On Behalf Of *Jonathan Hung
> *Sent:* October 21, 2010 3:37 PM
> *To:* Fluid Work
> *Subject:* Re: New keyboard accessibility plugin demo - Image Viewer
> design
>
>
>
> Hi everyone,
>
> Attached is an updated wireframe for the keyboard plugin demo. The design
> is essentially the same, but with a notable reduction in use of context
> messages which now only appear for the 5-star widget and the keyboard
> instructions.
>
> Please take a look at the design and let me know your thoughts!
>
> - 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 Wed, Oct 20, 2010 at 12:01 PM, Jonathan Hung <jhung at ocad.ca> wrote:
>
> 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: <https://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20101022/8e308962/attachment.htm>