Hi list.
I am still experimenting with my e7,
and a thought occurred to me about application accessibility in general.
I am still having problems removing widgits from my e7 home screen, I am
beginning to think it might be time to ask a set of eyes.
but I went on a hunt through google to see if there are any apps that
might make the touch screen more accessible to use.
I came across one called spb mobile shell which is a total interface
replacement, though of course it can be removed to get back to the old
interface.
I was interested in this app, because I believe it has a dedicated menu
button for functions to do with adding, and removing widgits.
Unfortunately I installed this application, and it took over the
interface, of course this now means talks won't read anything on the
phone, apart from its own functions and the menu for turning the phone
off, so I am going to have to get some eyes to help with removing it.
but this got me thinking and wondering, is it possible for a developer
to adapt there application for it to be accessible, or does talks have
to be adapted as well some times. is there any documentation out there
explaining what is needed in an application for it to be accessible with
talks?
as I have never heard of any such documentation, and it seems to me that
we are dependent on the talks developers to decide what applications
they want to be accessible with talks, for example, there are much
better web browsers out there than the ordinary symbian one, but none
are accessible with talks, and obviously that's either down to the
applications not having accessibility stuff in to start with, or because
talks has to be adapted to support them.
It would be good if there was some sort of documentation out there we
could point developers to and say this is what we need for an
application to be useable.
Of course its not likely any of them would make use of it, but I think
it would still be good if there was something we could give to
developers. as at the moment, we can complain all we like about
accessibility, but that's no good if you can't say hears some
documentation explaining about talks, and what is technically needed in
software for accessibility. At the moment, developers can try talking to
nuance, but why should they put all that effort in, making contact etc,
and then probably end up getting told that nuance has never heard of
talks which I believe happens to a lot of people because its such a
small product compared to the other software nuance sells.
_______________________________________________
Talks mailing list
Talks@talksusers.com
http://lists.talksusers.com/mailman/listinfo/talks
Hosting of this list provided courtesy of:
eHosting Limited: http://www.ehosting.com/
and
Talknav Inc. http://www.talknav.net/
