Re: [orca-list] Most accessible IDE for java

[Janina Sajka <janina rednote net>]

Thanks, Jose,

So a quick search yields 531 accessibility bugs. Looking through them I
certainly do see quite a few relating to GTK or to AT-SPI. But, there
are also quite a few relating to focus, or lack of keyboard support, or
relating to color and color contrast. I also see quite a few from
Windows.

So, I can't quickly assess whether Linux is any worse off than any other
platform supported by Eclipse when it comes to squashing accessibility bugs.

Maybe I should ask this way, is 531 an inordinantly high number of bugs?
Sounds like it could be, certainly. Is this historically high? About
average? And, how does it compare to any other category of outstanding
bugs?

I'm asking because I might have a small opportunity to suggest to IBM
that they've been ignoring a good IDE platform a bit too much. On the
other hand, they've also been losing staff quite steadily over the past
several years, so no promises. And, I should add I have no notion of
where Eclipse figures in their long range plans.

Janina



José Vilmar Estácio de Souza writes:
> It is managed by bugzilla.
>
>
> https://bugs.eclipse.org/bugs/
> On 12/20/2016 11:37 AM, Janina Sajka via orca-list wrote:
> > Not having ever filed a bug on Eclipse, I wonder about the tracking
> > system. Is it easy to identify which bugs are accessibility bugs? Is
> > there an accessibility keyword, or some similar identifier that one can
> > sort on?
> >
> > Janina
> >
> > Orca screen reader developers writes:
> > > José Vilmar Estácio de Souza <vilmar informal com br> wrote:
> > > > I like eclipse, but I'm disappointed with the current accessibility problems
> > > > presented in linux.
> > >
> > > Do you mean the Eclipse problems? Perhaps telling the developers that a number
> > > of people care about this will raise the priority of fixing those bugs.
> > >
> > > Although more attention has been given to accessibility in recent years,
> > > including the implementation  of accessibility APIs in applications, nobody
> > > seems to have solved the software engineering problem of bringing down the
> > > number and severity of bugs to an acceptable level and keeping it there. There
> > > are just too many accessibility bugs, and it doesn't seem to matter whether or
> > > not the software is developed by a large corporation with vast rsources (as in
> > > well known operating system and application  vendors) or by smaller groups
> > > with fewer resources.
> > >
> > > The solution is probably a combination of technical and social changes,
> > > including educational measures and more effective regulations.
> > >
> > > _______________________________________________
> > > 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
>
> -- 
> Assinatura Informal José Vilmar, Telefones: 21 2555-2650 e 21 98868-0859,
> Skype: jvilmar

-- 

Janina Sajka,   Phone:  +1.443.300.2200
                        sip:janina asterisk rednote net
                Email:  janina rednote net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:       http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures        http://www.w3.org/wai/apa