Active Topics
-
The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 1 hr ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 1 day, 21 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 6 hrs ago - more...
 |
|
2010-11-15
, 14:25
|
|
Posts: 889 |
Thanked: 2,087 times |
Joined on Sep 2010
@ Manchester
|
#2
|
Originally posted here and reposted in this thread, in an attempt to pool the ideas into the original accessibility features thread.
I've done a quick search on google for braille and linux and there seems to quite be a bit of progress in this field.
My first thought was that one could map the keyboard and other buttons to launch certain apps. eg using shortcutd one could map the camera button to bring up the phone app. A lot of work has been done by the maemo community to adopt the various keys, sensors and slides, and these could all be integrated into an 'maeccessibility' ui layer. This is along the lines of what TiagoTiago discusses in his thread (and I will duplicate this post there to try to keep any real ideas/development together on there).
But then I remembered the vibrating function of the n900, and obviously the vibrating screen function would have to be enabled, but the connection I made was with Braille. There have been great efforts made in the wider community to enable blind people to use computers, and within that the linux community is no exception.
From the link above I had a cursory glance at some of the links therein.
As alluded earlier on, there has been work in the Symbian world. Kurzweil KNFB Mobile Reader actually seems to meet exactly the OP's requirements. This is not opensource. There's also an Opensource GPS software for blind users called Loadstone built for the S60 platform. I bet these people will be looking to update their software for newer Nokia models, and which programming platform will they have to use? Qt4.7 of course.
Going back to Braille though and the really exciting area for me was SeebyTouch. Now this piece of kit does need a flat surface to work on, but it is lightweight and portable. It can work via Usb, which the n900 can now do. It is completely free - they have even included a complete spec of the hardware so anyone can build it. I wonder if Nokia were to get involved, maybe offering the developer a few R+D n900 devices, whether they would be interested in porting and adapting it towards a mobile device. If not I'm sure there is the talent out there to do it anyway.
I think the key thing here is that any progress made now can be ported across to future devices thanks to Qt4.7. So maybe it's not what the OP wanted (although some progress can be made through the development of Voice commands/eSpeak and adapting the various keys, switches, sliders and sensors) there is the possibility of really making a difference for Blind and Partially sighted people through the Open source movement.
 |
| Tags |
| fo with the, requests |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 02:37.
The idea is to allow the N900 to be operated without the user needing to see it (either a sighted person looking away or someone that is visually impaired)
A few features i can think of right now
Screen reader compatible with hildon, gtk and whatever java uses (am i missing any other big one?) as well as with the terminal.
Saying out loud what key was pressed.
Saying what is under the last tap on the screen, and only when the tap is repeated (less than N pixels away from the previous) actually perform the function that would usually happen when you tap there.
Some sort of image to sound conversion for both camera image and screen, with zoom to where the cursor is as well as whole frame modes (with the zoomed mode dragging on the screen would move the "window" that is being converted into sound isntead of actually passing the dragging to the program running). Is there a vOICe port for freemantle?
Text to speech battery level (somthing like "Battery level: N of X bars left" )
The screen reader(s) should be capable of both reading the whole screen as well as reading just what changed, and also should be compatible at least with microB , reading web pages properly, there might be the need for additional keyboard shortcuts for things like navigating between links, buttons textfields etc in webpages.
With the features already described i would expect the screen reader would work for reading caller ID, time on the clock etc