Hi
I'll try and be nice about a response too (wink)
So some info that may help you.
If the application your working on isn't something easy for others to get their
hands on and test with when trying to help you then any questions really need
to be regarding theory rather than your exact issue as it's almost impossible
to answer otherwise. Bear this in mind while reading through my answers to your
points.
1. Document edit areas that are not standard and cannot be simply reclassify
often need you to rewrite all the basic reading commands. You need to look into
what text you can actually access as if you can't get the current line of text
with the Jaws cursor then it might be a non starter immediately.
2. This item in your list doesn't give any information as to what problem your
having with these or even what they are/do.
3. Again, no mention of what problem your having with these, not able to focus
the fields, field labels not read back, field contest not read back etc etc
Control IDs are rarely something you can use.
Usually, but probably not always, when they can be used they are 4 digits long.
Compare it to the window handle, it's probably the same and will change every
time the interface refreshes.
I think I may have had 1 application in the last 8 years where the ControlIDs
were useful.
And very quick comment on your observations.
While all software should be accessible and the institutions should do
everything they can to ensure this I'm not sure what the alternative to those
two packages would be as they are probably the two most popular.
Please also bear in mind that while everyone here is very helpful and will pass
on as much knowledge as they can for a particular issue, nobody is obligated to
help. Note that I am only talking for myself when I use the term everyone.
The tone in your message implies that your owed the answers and that kind of
thing gets my back up.
My moan over, see how you get on and if I can help further please do ask.
Bob
On 1 Feb 2017, at 17:41, Darrell Bowles <DGbowles@xxxxxxx> wrote:__________�
Hello all,
I am writing to discuss the possibility of writing scripts for Kurzweil
3000, currently at version 15.
While I understand that Kurzweil 1000, is geared twards people who are
blind, or require keyboard access, Kurzweil 3000 is a highly popular
educational tool. The developers have done some work making a good deal of
the program accessible, including adding a lot of keyboard shortcuts to menu
options. However, they are lacking in some major areas, wich include,
1. The edit area whare the document is, is not a standard edit field. The
window class is KESITEXT.
2. There are several options that JAWS reads as, Read Read only, Write Read
only, and Scan read only. I do not believe, by the feedback, that JAWS
gives me, that these are standard controls either. I will look in to
reclassifying these controls.
3. The window that shows the definition's of a word that is highlighted
(selected), is not a standard window. It is a form of dialog, that sits
overtop of the other edit window, neither wich are standard controls.
Just as a side note, well one side note here, I tried to get JAWS to jump to
the KESITEXT class window using the function that uses the control ID, and
while the script compiled, there was no result.
finally, I want to say something, and I'll try and be nice about it.
When I wrote before on this topic, I was told that this product is marketed
twards persons with Intelectual disabilities. That is all fine and good,
but when that product is being given to students for free, and it is not
fully accessible, the college could very well get in trouble. The university
that I attend is doing the same with Read and Write gold, and the NFB should
nail that college, but that's an entirely different story. All that to say
this:
I feel that I was dismissed, regarding this issue, and I am not asking
anyone to write my scripts. While I am new at script writing, and have a
long way to go still, I'm nearly asking for the tools to do what I need to
do. I will be examining the application within the next couple of days, and
will probably write to this list again with what I have found.
I remember when ITunes first came out, and it was completely inaccessible.
The NFB threatened apple because of an uproar made by the blind community in
America that they wanted access too. Before that time, Apple devices were not
Relevant to blind people, and I think the opinion is, this program isn't
either. I will write back when I know more.
Darrell
Those who hope for the hopeless have a dream. But those who hope for the
dream have the greater reward. I believe it is a form of dialog, that sits on
top of the edit window.
__________�
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
