hello, I've put James's wireframes for the framework demo up on the wiki: http://wiki.fluidproject.org/display/fluid/Framework+Demo+%28wireframes%29
heidi On 2010-09-30, at 2:57 PM, James William Yoon wrote: Hi all, I've attached an updated framework demo mockup to show where the proposed audiozations would fit in. It's a simple addition GUI-wise, but would of course require some of content-to-audio conversion routine in the back (something I imagine we'll be thinking more about in the course of Floe as well). James On Fri, Sep 24, 2010 at 10:30 AM, James William Yoon <[email protected]<mailto:[email protected]>> wrote: Hi Colin, Thanks for the feedback. You make some excellent points. 1. Keyboard navigation and labelling for the colour picker will be very useful Agreed--both keyboard navigation and colour labeling will be important to consider. On that note, at one point I wondered if it would make more sense to use distinctive, memorable labels that weren't colour names to overcome the problems associated with labeling comparable shades of colour. On further thought, however, I realized it's likely best to label the colours normally for at least two related reasons: 1) to avoid segregation of vision and screen reader users (different "content" between vision and screen reader users doesn't make sense here), and 2) to be consistent across modes, not just within. 2. Alternative renderings for the various visualizations. This is a tricky one. Information visualizations are visual artifacts designed to exploit the visual cognition capacity of humans. I think the idea of creating alternate modalities for each type of visualization that carries the same design intent would thus be very difficult or impossible (it would imply a natural mapping between visual and auditory cognition; does it exist?). We could, however, relatively easily provide various audiozations alongside the visualizations--not as alternatives to specific visualizations, but as complementary transformations of the same data. A reasonable description of the more complex visualizations could be useful Definitely. I started on some of descriptions of the visualizations--they're alongside the visualizations in mockups 03 and 03B (Latin filler elsewhere). and we might want to consider what a text-only or audio rendering might look like. Agreed. Interestingly, one can think of the demo beyond demonstrating the Infusion framework, and more as an exercise in content transformation. We have a set of data, represented in raw text form, and the intention of the demo is to take the message and convert it into different mediums: various visual modes, and perhaps various audio modes too (and maybe, in the future, even different tactile modes too). This also makes for some interesting thinking about learner preferences too. Do I learn best through the textual form, one of the visual forms, or one of the audio forms? And, what do/can I learn from one mode that I didn't learn from the other? Cheers, James <Fluid Infusion framework demo design, N-03.png><ATT00001..txt>
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
