[nvda] What would it take for a graphics dictionary
- From: "Michael Whapples" <mikster4@xxxxxxx>
- To: <nvda@xxxxxxxxxxxxx>
- Date: Tue, 27 Mar 2007 21:36:00 +0100
Hello,
There was a question about nvda and outlook express and the status of messages,
and the answer someone suggested is that it is done with graphics. This leads
me to the question, if it is graphics, are the other screen readers doing it
through graphic dictionaries, and what would this take to be implemented in
nvda? How do they identify different graphics? Surely not just with a list of
graphics and an associated text description, or is it really that basic (and if
so how do you stop it swamping your HD?)
So how valuable would a graphics dictionary be, and how many uses would it
have? Considering that is it something that needs further consideration at the
moment, or can it wait? I know there are certainly other areas which will
improve the usability of NVDA, I would just like to get an idea of what will
yield the best results for the time spent on it, so an idea of the priorities
and where a graphics dictionary is in the list.
From
Michael Whapples
- Follow-Ups:
- [nvda] Re: What would it take for a graphics dictionary
- From: John Greer
- [nvda] Re: What would it take for a graphics dictionary
- From: James Teh
Other related posts:
- » [nvda] What would it take for a graphics dictionary
- » [nvda] Re: What would it take for a graphics dictionary
- » [nvda] Re: What would it take for a graphics dictionary
- » [nvda] Re: What would it take for a graphics dictionary
- » [nvda] Re: What would it take for a graphics dictionary
- [nvda] Re: What would it take for a graphics dictionary
- From: John Greer
- [nvda] Re: What would it take for a graphics dictionary
- From: James Teh