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

[Tom Masterson <kd7cyu gmail com>]

To make accessibility universal there are a couple of things that need to 
happen.

1.  We need to make it part of the education system and start teaching 
it's importance and how to do it as part of coding classes.  It is not 
taught and therefore not even thought of by most developers.

2.  Make it easy if not almost automatic so that developers don't have to 
spend extra time adding it.  Especially when using an IDE it should 
automatically add at least some form of accessibility items even if it is 
something silly like "button" for a button but atleast get something 
there.  When designing a User interface adding accessibility should be 
just as easy as dropping a widget on the screen and at most filling in 
some extra info which should come up as part of the other stuff used for 
building the widget.  When you are coding on short timelines having to 
think about and spend extra time adding other classes or otherwise to make 
something accessible does not fall into the plans.

By adding it into the education you make it something that people will 
think of and by amking it as easy as possible you make it more likely to 
be used in this era when you are expected to build fully functional 
sections of code in 1 to 2 weeks.

Tom

On Mon, 19 Dec 2016, Jason White via orca-list wrote:

> 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