Re: [orca-list] Accessibility of apps

["B. Henry" <burt1iband gmail com>]

Agreed, and also, unless you are prepared to get involved with LO or Firefox teams for long term you might 
find your work wiped out at any time after it 
makes it in to the official code as these projects are huge with hundreds of devs both pro and occasional 
hackers in the mix. Significant changes can 
ocur that might requir major reworking of fixes. 
Go for lower hanging fruit at first, and then if there will be the human power and long term committment to 
get some LO specilist team menbers 
together...of course the sky is the limit. 
Speakup could actually use some major work as well, not to mention the seemingly likely future need for a 
complete reworking if console support is 
removed from the kernel. 

-- 
     B.H.
   Registerd Linux User 521886


  Peter Vágner wrote:
Sun, Feb 21, 2016 at 07:24:13PM +0100

> Hello,
>
> If you have a capable developer or two I would rather start with simpler
> tasks if I were you.
>
> For example take file-roller and engrampa as a base and make sure it is
> possible to inwoke files view context menu with the keyboard only i.e. by
> pressing the applications key. I am sure for clever GTK developer this would
> be simple hackathon style project and you will contribute significant fix to
> two apps at once with minimal possible overhead and you will increase a bit
> of a11y related awareness within GNOME and Mate teams.
>
> Another a bit more difficult but still doable thing would be contributing to
> Brasero. It has an issue that its file dialog and other views whele files
> are displayed don't react to keyboard presses it only reacts to hardcoded
> mouse clicks. For example create a new data disc project in Brasero, from
> its edit menu open Add files dialog, and in that dialog try to enter any
> folder. You will find you can't unless you will resort to mouse emulation.
>
> These are apps which are stable for years with minimal changes so it's very
> likelly you won't cause conflicts etc.
>
> Then another very very cool project would be looking to pcmanfm code, if you
> like I can give you some commits where you should start at and based off of
> that creating an ATK support for playlist view for DeaDBeeF music player.
>
> I think debugging Gecko and other Mozilla things or libreoffice is an
> overkill for home office style developers. They will soon realize that there
> is better fix or a lot of more work needed plus it requires a lot of
> studying. I really think we should start with much more simple things once
> we will become proficient enough to be recognized by the Mozilla or
> Libreoffice teams.
>
> Greetings
>
> Peter
>
>
> On 20.02.2016 at 17:56 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,
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
> Log bugs and feature requests at http://bugzilla.gnome.org