<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On Tuesday 12 April 2016 07:56 PM,
Vikas Tara wrote:<br>
</div>
<blockquote cite="mid:570D059E.5030303@hamaralinux.org" type="cite">On
12/04/16 14:35, Raju D V wrote:
<br>
<blockquote type="cite">There are a lot of such issues which makes
packaging Ubiquity for
<br>
Debian/hamara a difficult and time consuming task.
<br>
<br>
Considering the time which has been lost trying to port Ubiquity
on
<br>
Debian/hamara, we have decided to ditch Ubiquity for the time
being and
<br>
use live-installer from Linux Mint.
<br>
<br>
Live-installer is an easy to use OS installer and works fine
with debian
<br>
based systems.
<br>
<br>
Compared to Ubiquity the only place where live-installer fails
to
<br>
perform well is the accessibility part.
<br>
If we can get live-installer completely accessible then it is a
worthy
<br>
option to Ubiquity.
<br>
<br>
Making this change will help us releasing the Debian based
Hamara Sugam
<br>
distro in a shorter time frame and in a better way.
<br>
<br>
Looking forward to your opinions,
<br>
</blockquote>
Thanks Raju and for all the effort on Ubiquity so far, however
this does seem to be right time to throw in the towel.
<br>
<br>
I'm keen to work on the accessibility side so am looking into how
to make that happen.
<br>
<br>
Would be interested in any pointers from anyone - as I've not
worked on bringing orca support to an application before.
<br>
</blockquote>
It will be a difficult task although not impossible.<br>
Firstly is the said application (installer in this case ) using gtk?<br>
if yes then gtk has got classes that implement accessibility.<br>
That library is called AT-SPI meaning accessibility toolkit service
provider interface.<br>
meaning there is a class for making input fields accessible, then
there is one for button, checkbox etc.<br>
As developers or modifiers of any application written in gtk, one
has to inherit these classes in every widget.<br>
Then for the application the atspi service should be integrated
which provides accessible events such as locus of focus.<br>
Orca or any other screen reader is then programmed to consume these
standard events and get the accessible information out.<br>
it then sends this information to a speech synthesizer like Espeak
through either dbus or some thing similar.<br>
So I guess that makes it quite a work to do.<br>
Debian's text based installer has become accessible off late so that
is one distant option available.<br>
So if a blind person has little bit of hacking knowhow as in how to
change the boot time parameters to start with voice (kernel has the
speakup module by default ) and then how to understand a few
technical terms then it will be possible to Install Debian through
the keyboard with command line mode.<br>
So this is the current situation.<br>
If installer itself is not accessible then there is no question of
calling distro an accessible one.<br>
Further more, Orca not just makes things accessible for blind, but
also for low vision people, and those who are def and blind as well,
through braille display output support.<br>
<blockquote>There are plans in order to make some thing for people
with CP also.<br>
So all in all it become a big population.<br>
Thanks a million vik for this due consideration, there are very
few people in the community who go so far with seriousness about
accessibility.<br>
Ease of developing, low challenges and not much work to do are
most reasons why many developers avoide to take this challenge.<br>
For example GNUKhata has been made totally acccessible no matter
what.<br>
I am seeing the eferts put by Mate guys in accessibility and I am
really impressed.<br>
I see Hamara taking this seriously as well.<br>
</blockquote>
happy hacking.<br>
Krishnakant.<br>
</body>
</html>