Re: I'm dissappointed

erik burggraaf <erik@...>

Again, I don't disagree necessarily. I'm just stating fact about the differences, advantages, disadvantages, and what all this means for users and developers. I want people who are in the kind of position that Sandra is in to understand where things are headed and that regardless of the short term solution, the end result will be more inclusive development.

All this has been going on for 10 or 12 years already. It should come as no surprise to most of us. There are a huge number of factors. Obviously, we want full inclusion sooner than later. That requires us to balance the short term and long term goals. We need to get things done today, but we also need to keep our eyes on the prise, and advocate for new infrestructure that fits the new paradigm.

We have to realise that we are legally and socially entitled to consideration in development, that we have people with the skills to collaborate in bringing in the new design paradigm, that the laws and standards support us, that the new paradigm benefits every one, not only people with disabilities, and that the more we become adopters and advocates, the faster we forward the trend.



On January 1, 2018 8:27:59 PM "Pranav Lal" <pranav.lal@...> wrote:

<snip > This is one area where I disagree. Not that jaws has the features or
that they are useful, but that they belong in NVDA. I believe that it
is the responsibility of developers to label their graphics and
controls, draw and class their windows and controls properly, and
build keyboard/touchscreen support for their apps properly. This is
increasingly required by law, imposed by societal change, taught as
programming best practice, and demonstrably beneficial beyond the
needs of disability communities. Unfortunately, it's not all there
yet, but within the next three years, it will become legally and
socially inacceptable to build software without regard for
accessibility standards, just as you wouldn't build out with no regard
for UI, performance, security, and other common standards and best
practices. I believe the development philosophy of NVDA is based on
this. A screen reader should read the screen, conveying the
information already provided in accessible format, doing as little
interpretation as possible.
PL] Eric, I agree with Sandra. Philosophy is ok in the long run but I have to get work done now and will take the easiest path to do that work. Compliance is never 100%. What about all the legacy applications enterprises run? I need a solution for reading the screen and I see no problem in that solution giving me information in a way that is easiest for me to consume.


Join { to automatically receive all group messages.