Re: Forming an Accessibility Steering Committee



Very cool. It wasn't my intention to actually start the brainstorming
on this thread, but there you have it. :)

So now that all this great information is out in the wild, how do we
make it easy to find? I know the mailing list archives are recording
this information, but someone really has to be looking for it to find
it there.  Where else should we catalog these sorts of spurts so the
casual passerby (e.g., someone with Maemo experience looking for a
project, but perhaps without any accessibility background) will happen
upon it? The a11y wiki pages Willie is proposing? The GNOME SoC
projects like David suggested? Both places? Somewhere else?

I'm using the Maemo way-finding project as an example. What I'm really
looking for is some repeatable process encouraging these spurts,
drawing the information out of the community, and recording it where
it can be easily discussed and developed. Which brings me back to my
original post about making this one of the concerns of the steering
committee: how do we promote / manage future projects that go beyond
the immediate horizon?

Pete

On Dec 21, 2007 2:59 PM, Peter Korn <Peter Korn sun com> wrote:
> Hi Peter, David,
>
> Re: the Nokia as an open source-based accessible talking GPS, in fact
> the open source GPS software already available for the N800 will use
> Flite (which has been ported to the N800) to give speech output.  The
> main problem, as was already noted in this thread, is getting map data
> designed for a pedestrian.  The public databases for this info (e.g.
> Google) are designed for automobiles.  But once that piece is addressed,
> you should have everything needed to make the N800/N810 a talking GPS
> for accessibility use.
>
>
> Regards,
>
> Peter Korn
> Accessibility Architect,
> Sun Microsystems, Inc.
>
>
>
> >> Choice quote: "we have succumbed to the tyranny of the popular, the
> >> typical, the average, or the norm"...  but let's not!  We should be able
> >> to go so much farther and faster in FOSS land...
> >
> > Simply getting together to talk in an open forum helps spark new
> > ideas. Some of the best brainstorming sessions I've ever had have been
> > with my thesis adviser after reviewing other research papers. It's
> > amazing how many intriguing ideas can result from reviewing what other
> > people are doing to push the envelope.
> >
> > Of course, collaborating and working to resolve the problems here and
> > now is still the primary concern. But it would be nice to see some
> > time and cycles spent freely discussing projects that may appear a tad
> > "crazy" at first. Even if this small community of accessibility
> > developers doesn't have the time or resources to tackle them, getting
> > the ideas out there for other people to think about might entice them
> > to join the effort (the "Wow. That's cool. I can do that." effect).
> >
> > Here's the kind of "crazy" I'm talking about:
> >
> > Humanware makes a product called Trekker which provides spoken GPS
> > navigation aid for people with visual impairments. Their solution is
> > unique among competitors because it uses a standard PDA (the Dell
> > Axiom X51 I believe), overlays a custom rubber keyboard on top of the
> > touch screen for input, and provides speech output. The Trekker can be
> > bought as part of the Maestro package which also provides speech
> > displays and button input for applications including a text reader,
> > contact list, agenda manager, etc. The price is not listed on
> > Humanware's page, but other sites list it somewhere between $1500 and
> > $2000. While it seems high, it's actually cheaper than other, custom
> > manufactured devices suited to one and only one user group.
> >
> > So what could we do to push the envelope under the same premise, that
> > is, reuse existing, commodity hardware and platforms? The Nokia N800
> > line of Internet tablet products with Maemo comes to mind. It's
> > GNOME-based, supports open development, and has an API for
> > communicating with Bluetooth GPS receivers. The cost is around $300
> > for the N800 and roughly $100-$300 for a separate GPS receiver.
> >
> > There isn't much documentation on doing speech synthesis on the Maemo,
> > but it looks like at least a few people have tried. I have to believe
> > it's possible using flite or espeak. Granted, input is also a problem
> > since interaction is mostly driven by the touch screen. However, the
> > N800 does have more than a few physical buttons and the N810 has a
> > fully qwerty keyboard. A custom navigation app could make use of
> > either for stepping through directions en route. The user could plan
> > the route on their desktop computer where I/O is more full-featured,
> > and then sync it with the mobile device where a less interaction-heavy
> > UI could speak directions as the user follows his or her route.
> >
> > This setup seems ripe for doing something new. Speech-based
> > way-finding is just one possibility. I'm sure with some time spent
> > thinking on it, we as a community could come up with many, many more.
> >
> > I believe it's this kind of thinking the committee should promote and
> > document for others to see. Again, we as individuals may not get time
> > to work on implementing every concept. But I bet if we use an
> > idea-shotgun, and blast enough into the public-awareness, someone will
> > grab them and run.
> >
> > Pete
> > _______________________________________________
> > gnome-accessibility-list mailing list
> > gnome-accessibility-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
>
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]