Fluid work update

Daphne Ogle daphne at media.berkeley.edu
Wed May 23 19:53:17 UTC 2007


Great comments Rich!  Continuing the discussion below...mostly with  
additional questions for discussion within the community.

On May 23, 2007, at 12:09 PM, Richard Schwerdtfeger wrote:

>
> Thanks Colin,
>
> comments:
>
> What browsers must be supported, when, and to what degree?
Good question.  Should the Fluid project align with supported  
browsers for Sakai, uPortal and Moodle or should we define our own?   
It seems like we should at least support those that the projects  
already support.  Are there browsers far behind the curve from an  
accessibility perspective that would be too challenging to support at  
this point?
>
> Designing and Building the First Fluid Component - this section  
> should include a style guide definition.
This is a great idea.  If we think of this as organic we could create  
it as we go and allow it to be Fluid :) as we define the styles.  I  
can add a page in the wiki under user experience.  Should we combine  
accessibility, visual and interaction guidelines or have a seperate  
page for each?  Can you point us to good accessibility style guides  
you've seen for a benchmark?
>
> Planning Heuristic Evaluations of Sakai, uPortal, and Moodle -
>
> I see a mention of cognitive and learning but I don't see a  
> breakdown of targeted users and transformations which should be  
> addressed and how these would then be usable.
Exactly, the work of defining these still needs to be done.  And we  
are really looking to those in the community with expertise in this  
area to help with the definition.  At the moment I think we are a bit  
caught up trying to get some "quick wins" (as Colin discussed in the  
roadmap) while fleshing out some of the long term goals...and still  
hiring new resources that Fluid allows for.   Perhaps this would be a  
good topic for an upcoming Fluid meeting...or a breakout working  
session in an upcoming Fluid meeting?
>
> For example, for a low vison how will we address content  
> enlargement - text only, text and images, the entire content  
> (through the browser).
> Should we address linearization for larger fonts. For example, in  
> the lightbox case you have a grid. If you enlarge the content  
> enough you end up with scrolling. You might then want to linearize  
> and swap the lightbox grid with a lightbox listbox which is left  
> justified.
> We will need to address how the design patters change when the  
> specified transformations occur.
This is great.  I'm looking forward to further conversations to  
define and flesh out these specifications.  So we decided to start  
Lightbox design and development within the contexts of default "drag  
and drop" behavior and keyboard-only behavior.  I'm interested in how  
others see the low vision needs coming into play.  Is this yet  
another property setting on the component or is this work that would  
be done in the Gallery tool itself?  IMHO -- these are exactly the  
kinds of conversations we need to be having as we further define what  
a component is and isn't.

In the meantime, I'm supposed to be iterating on the Lightbox  
behavioral spec which will help get us all on the same page about  
current work and to talk about these issues concretely around the  
Lightbox component.  I've promised to get the next version on the  
wiki before I end my day today.  I'll send a note to the group  
afterwards.

Thanks again for comments Rich!  The first step is identifying what  
we don't know so we can figure it out...

-Daphne
>
> Cheers,
>
> Rich
>
>
> Rich Schwerdtfeger
> Distinguished Engineer, SWG Accessibility Architect/Strategist
> Chair, IBM Accessibility Architecture Review Board
> blog: http://www.ibm.com/developerworks/blogs/page/schwer
> <graycol.gif>
> Colin Clark <colin.clark at utoronto.ca>
>
>
> Colin Clark <colin.clark at utoronto.ca>
> Sent by: fluid-work-bounces at fluidproject.org
> 05/18/2007 07:08 PM
>
> <ecblank.gif>
>
> To
> <ecblank.gif>
>
> fluid-work at fluidproject.org
> <ecblank.gif>
>
> cc
> <ecblank.gif>
>
> <ecblank.gif>
>
> Subject
> <ecblank.gif>
>
> Fluid work update
> <ecblank.gif>
> <ecblank.gif>
>
> Hi everyone,
>
> I've been working on a short term road map document that describes the
> work we're doing over the next couple of months. Please have a look at
> it and feel free to share your thoughts.
>
> http://wiki.fluidproject.org/display/fluid/May+2007+Short+Term+Road 
> +Map
>
> Here's a super-quick summary:
> * Designing and building our first Fluid component
> * Planning heuristic evaluations of Sakai, uPortal, and Moodle
> * Evaluating JavaScript toolkits
> * Expanding Sakai's UI design patterns
> * Presenting at Conferences and U-Camp
> * Incremental architecture of the Fluid framework
>
> I'll be following this up with a longer-term view of the project in  
> the
> coming weeks. It's great to see work progressing on the project so  
> early!
>
> Have a great weekend,
>
> Colin
>
> -- 
> Colin Clark
> Technical Lead, Fluid Project
> Adaptive Technology Resource Centre, University of Toronto
> http://fluidproject.org
> _______________________________________________
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work
>
> <graycol.gif>
> <pic22018.gif>
> <ecblank.gif>
> _______________________________________________
>
> fluid-work mailing list
> fluid-work at fluidproject.org
> http://fluidproject.org/mailman/listinfo/fluid-work

Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
daphne at media.berkeley.edu
cell (510)847-0308



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://fluidproject.org/pipermail/fluid-work/attachments/20070523/2c593e32/attachment.html>


More information about the fluid-work mailing list