Re: [orca-list] Accessibility of apps

[Krishnakant <krmane openmailbox org>]

I think some of the funding must exclusively go for documenting 
accessibility infrastructure.
For example the much awaited Orca scripting guide must be done by some 
one in a really dedicated way.
This will not just pool in a lot of Python developers like your's truely 
but also result in a favorable situation  where we will have a good 
number of Orca scripters while most part of the funding can then be used 
at bigger tasks like improving ATSPI or boosting the accessibility on 
things like QT and KDE desktop.
There were some tutorials which had started coming in and the first 2 or 
3 parts were really great.
That's the perfect way of getting more developers for Orca scripting 
(which to my knowledge can go a long way in making accessibility a much 
better experience on Linux).
Happy hacking.
Krishnakant.


On Tuesday 23 February 2016 02:19 AM, John Heim wrote:
> I am interested in helping with getting funding. I am President of the 
> International Association Of Visually Impaired Technologists and 
> former president of several other non-profits.  I have some 
> connections we might be able to use.
>
>
>
> On 02/20/2016 11:09 AM, MENGUAL Jean-Philippe wrote:
> > Sure, but it's a very very big project. I'm working on it in another
> > context (we're searching for financial support, maybe we'll try
> > crowd-funding, etc). And anyway, out of what can do a Hackhaton, except
> > if dedicated to LO with experts on it.
> >
> > Well, let's hope we'll find how to finance it, and will be done. Things
> > will happen in 2016 about it. But with a significant effort.
> >
> > Regards,
> >
> >
> > Le 20/02/2016 18:05, Fernando Botelho a écrit :
> > > Oh, I know you want smaller fish to fry, but LibreOffice please!
> > >
> > > Best,
> > >
> > > Fernando
> > >
> > >
> > >
> > >
> > > On 02/20/2016 02:56 PM, MENGUAL Jean-Philippe wrote:
> > > > Hi,
> > > >
> > > > It's a common assessement: if free software isn't accessible, it's 
> > > > not a
> > > > screen reader problem, but the app which doesn't send good info to
> > > > at-spi.
> > > >
> > > > ok. How to fix this? Explaining, bug reporting, etc. One idea is
> > > > hackhaton. We did one this week-end in Paris. We studied Audacity and
> > > > Linphone: 2 GTK apps, where essential issues are related to labels,
> > > > focus movements with keyboard, etc.
> > > >
> > > > But I realise that I have not a lot of further ideas of simple apps to
> > > > improve. I plan mumble, and other more complex things such as
> > > > libreoffice or Firefox, so complex for a general-hackhaton.
> > > >
> > > > Do you have ideas of apps on which we could report accessibility bugs
> > > > during an hackhaton, or help fixing, in GTK? Can you tell me apps you
> > > > don't access to (or access just partially)? And what is it for? No
> > > > alternative?
> > > >
> > > > It'll give me ideas for next hackhaton/bugreports. If they're in GNU
> > > > project, still better.
> > > >
> > > > Thanks for feedbacks,
> > > >
> > > > Regards,