Infusion Builder Rev 2 design - feedback needed

Jonathan Hung jhung at
Tue Feb 1 19:03:59 UTC 2011

Hi Justin and Anastasia,

Both of you brought up similar points about the use of the Ignore feature.
After some discussions with both of you, I agree that it is confusing that
Ignore is present for the 3rd party modules, and not for Infusion. Also,
after some thought and discussions with James, it seems that the Ignore
feature would be difficult to implement in a checklist in a way that is
clear and logical for someone using an AT. (It's possible to do, but
requires more metadata and markup than one would expect for this kind of

So for now, the Ignore feature is going to be omitted unless there's a nice
way to implement that makes sense for both sighted and non-sighted users.

As for categorization of components and wording of text, this isn't final
and definitely requires refinement. I will be sure to approach y'all in the
next few days to do some "card sorting" of components.

I'm working on another iteration. Hope to have it out very soon.

Thanks for the feedback!

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

On Tue, Feb 1, 2011 at 9:52 AM, Cheetham, Anastasia <acheetham at>wrote:

> Jonathan, I purposely had a look at the new illustration before reading
> your explanation, to get a sense of what a user might experience. Here are
> my first impressions:
> - The "ignore" column in the third-party modules is not clear: What does it
> mean to ignore something? It's possible that in a live scenario, where I
> could observe checkboxes turning themselves on and off as I make other
> changes, this might become more clear.
> - Why is the "ignore" option only on the third-party modules, and not on
> anything else?
> After reading our description/explanation, here are my thoughts:
> - I'm still not clear on the different interface for the Infusion Core
> stuff and the third-party stuff: Why does only the third-party stuff have
> the "ignore" option? What happens if I select a component (which will
> automatically select the Framework), then deselect the Framework, then
> select another component? Will Framework come back on? Should I be able to
> "ignore" it?
> I guess I'm still not quite clear what the "ignore" function does. Perhaps
> it might be helpful to see a sequence of steps, to show what would turn
> on/off when, and what happens when the user 'ignores' something?
> --
> Anastasia Cheetham     Inclusive Design Research Centre
> acheetham at            Inclusive Design Institute
>                                        OCAD University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the fluid-work mailing list