Accessibility

[Armin Krauss]

Hi Alison,

I think we start with Fluid Infusion since this is a much more mature
product. However,
there is no reason to exclude Engage.

For now let's concentrate on Infusion.

Armin



On Tue, Oct 27, 2009 at 14:36, Alison Benjamin <alison.benjamin at gmail.com>wrote:

> Hi,
>
> Cool, I'm happy to help on this.
>
> I added to this a subtask,
> Describe planned or completed UX testing that occurred with components.
>
> Do we envision this being just for Infusion, or for Engage as well?
>
> Thanks,
> Alison
>
> On Tue, Oct 27, 2009 at 2:25 PM, Armin Krauss <mackrauss at googlemail.com>
> wrote:
> > Hello everyone,
> >
> > I am currently working on the creation of a Wiki site that better
> explains
> > how we in Fluid understand
> > accessibility and how this is implemented in the components.
> >
> > To start this process I created a JIRA task
> > (http://issues.fluidproject.org/browse/FLUID-3330). Please
> > have a look and comment on the task and its sub-tasks.
> >
> > Furthermore, I will not alone be able to do this. Especially the
> description
> > of the components will require
> > the help of different developers.
> >
> > Once I created the Wiki page I will mail it to this list and add it to
> the
> > JIRA ticket. All comments via email
> > or as JIRA comment are welcome.
> >
> > Armin
> >
> > _______________________________________________________
> > 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/20091027/fc8f3088/attachment.htm>