Re: [orca-list] new a11y Dev Team was Most accessible IDE for java

I am a Python developer with fair understanding of C language and pretty expert at GNU/Linux with Ubuntu.

I also have worked on inter process communication in the old days.

So I would be most interested to contribute.

I have waited for some good documentation on Orca scripting.

But if a team is being made for a broader issue, I am all for it.

Let me know how you think we go ahead and I will put my views as well.

Happy hacking.


On Wednesday 28 December 2016 12:20 AM, chrys87 web de wrote:
Howdy Guys,

That topic brings me to something i discussed on sonar list a few weeks ago. The problem in a11y is more 
general. There are not many companys that are intrested in provide good a11y support on linux world. Thats 
why we should learn to fix problems  and improve  the Situation  by ourself. To help Joanie and all other 
people that currently  do most of the work for us.
Thats why I currently  form a new Dev Team (AIT = accessibility  improvements and Toolkits).

Currently  we are about 5 people. If you are intrested  in helping or improve  the situation let me know.  if 
you are not a programmer but you are intrested  in learning its no problem.  you will get an skilled guy on 
your side that can learn and coach you.
If you are a Dev feel free to contact me. More people will have more fun and the world  might more easy if 
you are not alone ;).
Our plan is to fix ugly a11y bugs and provide useful tools (like SOPS, OCRdesktop  or OCRpdf).
Currently  i m working on an modular modern and feature rich console screenreader  with my team. Its in an 
good shape and will get an offical announcement  soon.

What you guys think about?
Looking  for feedback,

Cheers  Chrys

Am Mi. Dez. 21 20:51:00 2016 GMT+0100 schrieb Jason White via orca-list:
Krishnakant <krmane openmailbox org> wrote:
Yes from your perspective where there are different requirements and
paradimes, you are absolutely correct.
Of course current systems have few big advantages.
I have to work with my sighted colleagues day in and day out.
I have to exactly point out things to them graphically or you may say the
way they see it visually.

I work with sighted colleagues too, but I usually don't need to know how
applications are presented visually to perform my task. I think this level of
information should be available, but it isn't good as the default approach to
presenting a braille or spoken interface. There are people who have the need
you describe, and this should be supported, but there are better ways of
creating effective spoken interaction.

There's a broader move toward virtual agents and spoken interaction at the
moment. The Linux and free software community is regrettably not at the
forefront of this work yet. If you've ever used an Amazon Echo (even if only
in a technology demonstration), you'll know first hand what a high-quality
spoken interface can do. People who buy such a device don't want to talk to it
about buttons, menus, sliders, entry fields etc. - they want to use the
vocabulary of the application domain.

If there's a sustained move toward the notion that applications need to
support such high-quality language-based interactions, then perhaps we'll move
beyond the treadmill of GUI accessibility, with all of its problems, and
toward a world in which user interfaces are inherently interactive and
language-based as well as graphical - either or both according to the user's

orca-list mailing list
orca-list gnome org
Orca wiki:
Orca documentation:
GNOME Universal Access guide:
Log bugs and feature requests at

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