[nvda] Re: NVDA and video intercept VS display hooks.
- From: "Jim Grimsby JR." <jimgrims@xxxxxxxxxxx>
- To: <nvda@xxxxxxxxxxxxx>
- Date: Mon, 30 Apr 2007 06:05:45 -0700
Hi not trying for a debate here. I agree a request should be maid and I am
the first to make it. How ever then watch to see what happens. The request
is maid and maybe you will get some thing done. Maybe how ever if you got
the tools in your screen reader to do it you will see results if you just go
do it.
For example foobar. Every time you move to a new play list the window
listing the files is not updated to reflect the change in play list.
You have to focus the tab list then focus the play list listing window. I
sent a request to foobar asking this be fixed. I am still waiting. But
using jaws I fixed the problem on the same night I sent the request with a
jaws script. Granted this does nothing for n v d a window eyes etc but at
least I am not having to jump threw hoops with foobar on my primary screen
reader.
So requesting is grate wonderful and I support it but waiting around and not
having access because we are waiting for thoughs requests to be granted I
just don't see it.
-----Original Message-----
From: nvda-bounce@xxxxxxxxxxxxx [mailto:nvda-bounce@xxxxxxxxxxxxx] On Behalf
Of James Teh
Sent: Sunday, April 29, 2007 4:41 PM
To: nvda@xxxxxxxxxxxxx
Subject: [nvda] Re: NVDA and video intercept VS display hooks.
Jim Grimsby JR. wrote:
> Well the bottom line here is we do not live in a perfect world and the
> bottom line here is the job of the screen readr to provide access not
> the job of the programmer.
I disagree. It is always better to have an application accessible out of
the box than have to implement all sorts of dirty hacks to make it
accessible in a screen reader. Doing the latter frequently results in
accessibility which is flawed and unreliable at best. I agree that a
screen reader should try to implement other methods where the developers
absolutely refuse to change anything to fix their inaccessible
applications, but where there is hope of a fix, this should always be
tried. It is precisely this ideal of placing the onus on the screen
reader that has led to so much poor accessibility in the Windows world.
Aside from all of this, accessibility can have other less obvious
benefits. For example, there is no need to use non-standard widgets if
the standard ones can achieve the same task; why reinvent the wheel?
Similarly, if accessibility is so hard to implement, there is a problem
with the separation of user interface from core logic, which is a sign
of very bad application design, something which is becoming all too
common in today's "release first, reliability later" world.
I'm not the type to say "if an application isn't made accessible, tough
luck; we can't support it". You're quite right - we do not live in a
perfect world and having this attitude is just biting off one's nose to
spite one's face. However, nor do I believe in the opposite idea of "we
shouldn't have to request that applications be made accessible; we
should just deal with the best we can and suffer poor accessibility".
Jamie
--
James Teh
Email: jamie@xxxxxxxxxxx
WWW: http://www.jantrid.net/
MSN Messenger: jamie@xxxxxxxxxxx
Jabber: jteh@xxxxxxxxxx
Yahoo: jcs_teh
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to: http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/ Report bugs or make feature requests at:
http://trac.nvda-project.org/ Message Archive:
http://www.freelists.org/archives/nvda
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.467 / Virus Database: 269.6.2/780 - Release Date: 4/29/2007
6:30 AM
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To modify your NVDA Email settings go to:
http://www.freelists.org/list/nvda
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.nvda-project.org/
Report bugs or make feature requests at:
http://trac.nvda-project.org/
Message Archive:
http://www.freelists.org/archives/nvda
- Follow-Ups:
- [nvda] Re: NVDA and video intercept VS display hooks.
- From: James Teh
- References:
- [nvda] Re: NVDA and video intercept VS display hooks.
- From: James Teh
Other related posts:
- » [nvda] Re: NVDA and video intercept VS display hooks.
- » [nvda] Re: NVDA and video intercept VS display hooks.
- » [nvda] Re: NVDA and video intercept VS display hooks.
- » [nvda] Re: NVDA and video intercept VS display hooks.
- » [nvda] Re: NVDA and video intercept VS display hooks.
- » [nvda] Re: NVDA and video intercept VS display hooks.
- » [nvda] Re: NVDA and video intercept VS display hooks.
- [nvda] Re: NVDA and video intercept VS display hooks.
- From: James Teh
- [nvda] Re: NVDA and video intercept VS display hooks.
- From: James Teh