Hi

Well, it's nice to finally hear Intuit and accessibility in the same sentence.  
I have started playing around with Quicken 2015 using a test Quicken data file. 
 The Quicken scripts that come with JAWS 16 are the same scripts as those from 
JAWS 2003 with a few modifications by Intuit and will say Quicken 2003 scripts 
if you press JAWSkey+q.  It looks like one function was modified and one 
function and 1 script were added for JAWS 2015.  The function that was added 
would read the title and contents of the current field.  But I didn't see it 
being called at all.  The new script will read the title for each field and the 
field value for each field in a row.  But you have to have your transaction 
register set up as a one line display.  I have read that this script is invoked 
by pressing control+1, butt this script does not have a key assigned to it in 
the script itself or the JKM file.  If you want to use this script, you can 
create a Quicken.jkm file in your JAWS user settings folder containing the 
following two lines.

[common keys]
Control+Shift+1=SpeakQuickenListRowData

I used control+shift+1 because control+1 will bring up the One Step Update 
dialog in Quicken 2015.  I don't know what if any changes have been made by 
Freedom Scientific to the Quicken scripts since the Quicken 2003 days.  

If you're using any version of  Quicken with JAWS 16, you are using these 
modified scripts.  Because I download some transactions, I have to upgrade 
Quicken every 3 years and modify the scripts for the parts of Quicken I use.  I 
no longer have Quicken 2003.  But the JAWS 16 Quicken scripts seem to act the 
same using Quicken 2012.  

In my brief experience of running Quicken 2015 under Windows 7, I have noticed 
the following while in a transaction register.

1. The new script added by Intuit will read the title for and value of each 
field in the row where the PC cursor is.  His seems to work well in you're in 
the first line of a transaction, but not if you're in the second line.  But 
your register is supposed to be a one line display, which mine is not.

2. A say line will read the title and value of each field in the row where the 
PC cursor is placed. Instead of just reading the value of the current field.

3.  JAWSkey+c will not say the name and row of the active cursor.

4.  When you tab to the different fields in a transaction or arrow up and down 
to a different transaction, the title and value of the field where you land are 
not automatically spoken, and since the SayLine will read the entire row, I 
haven't found a way to just read an individual field.

5.  The account list (control+a) can  only be used with the JAWS cursor to 
select or edit an account.

6.  If I alt+tab away from Quicken 2015 in Windows 7, I cannot alt+tab back to 
it.  I have to bring up the active window list by pressing JAWSkey+f10 to get 
back to it.

7.  You do have to create an Intuit id to use Quicken 2015.  But I'm not sure 
how different this is from Quicken.com which would upload your quicken data to 
the cloud if you let it.  But I have read that you do have to create an Intuit 
account for each Quicken data file you use.

In Windows 8.1, I have never had much luck trying to get JAWS to read the 
register screens  in either Quicken 2012 or 2015.

If you're considering upgrading from Quicken 2003, you'll find some things that 
have changed.  In Quicken 2003, all of the account registers were the same 
using the same windows structure.  But somewhere between Quicken 2004 and 2006, 
the transaction register for investment accounts, (brokerage, mutual funds, 
etc.), were changed to transaction lists with a whole new windows structure and 
much less accessibility.  In Quicken 2003, you could export and import 
transactions to or from a QFX file for any account.  With later versions, you 
cannot import or export transactions to a QFX file for any investment account.  
Also you can only import transactions from a QFX file to cash accounts.  

Although this is a start, my conclusion is that Quicken 2015, or any version 
after 2003, will not be as accessible as Quicken 2003 using JAWS.  Following is 
an email sent to another list from the person in charge of accessibility at 
Intuit about Quicken 2015.

-----Original Message-----
From: jawsscripts-bou...@freelists.org 
[mailto:jawsscripts-bou...@freelists.org] On Behalf Of Ted Drake
Sent: Tuesday, December 16, 2014 04:15
To: jawsscri...@freelists.org
Subject: [jawsscripts] Re: Quicken 2015 JAWS scripts

Hi Andy
I'm sorry about your confusion with the Quicken script updates with JAWS.

Intuit’s Quicken team has been working to increase the accessibility of
Quicken 15 for Windows. You’ll find many improvements in keyboard
functionality and object identification in the latest version of Quicken.
During this process, we realized the existing JAWS scripts could be updated
to further increase functionality. Please note, this was developed for
Quicken 15, but should work with prior versions.   We are working with a
group of screen reader users to prioritize and solve existing accessibility
issues. I will contact you off-list for more information.

The following improvements were made via the updated JAWS script

 a. Ability to read the list row data along with headers - On "Account
list", "Bills and Income reminders" and "Account register" screens (Ctrl +
1)
b. Ability to read field header and cell value on moving from one field to
other - On Account register screen
c. Removed the double reading of cell value in account register screen.

Limitations or Known issues with Quicken JAWS scripting

 a. It can read only whatever is visible on the screen
 b. Sometimes, it does read the next column value for current cell if
current cell doesn't have enough width (this is a limitation - due to small
column widths)
c. This script does not work if column header values are spanned across
rows (This is a limitation again as we write scripts based on co-ordinates)
 d. It is not reading the balance column value on account register screen

 Intuit thanks Deque’s Sujasree Kurapati for her work on these scripts.


> From: "Andy B." <sonfir...@gmail.com>
> Subject: [jawsscripts] Quicken 2015
> Date: Mon, 15 Dec 2014 20:52:36 -0500
>
> Fs released this update:
>
> http://www2.freedomscientific.com/downloads/JAWS/JAWS-whats-new.asp#Enhancem
> ents. It mentions that support for Quicken 2015 was added through the
> provided scripts from Intuit. Unfortunately, someone must have forgotten
> the
> scripts, Intuit never gave them to FS, or I am doing something wrong. I
> picked up a copy of Quicken 2015, but the newest versions of the scripts is
> from Quicken 2003. Quicken still acts inaccessible and completely unusable.
> What do I do now? Do I get my money back? I tried looking around on Google,
> but there is nothing anywhere about Quicken and JAWS working together,
> except for the 2003 version.



-----Original Message-----
From: JAWS-Users-List [mailto:jaws-users-list-boun...@jaws-users.com] On Behalf 
Of Rick Justice
Sent: Tuesday, December 30, 2014 01:54
To: jaws-users-list@jaws-users.com
Subject: Re: [JAWS-Users] Quicken 2015

Dave,
I haven't heard anything about it as far as accessibility goes, but understand 
that creating an on-line account with Quicken is required.
For that reason alone, it wouldn't matter to me if Jaws would work with or not.
I have become more aware that if these XP machines give up on me I will 
probably have to find another program for tracking my finances, or lack 
thereof, and for writing checks.

HTH,
Rick Justice

Tomorrow's another day, another way!
and if tomorrow never comes, problem solved!

----- Original Message -----
From: "David Ferrin" <ow...@jaws-users.com>
To: <jaws-users-list@jaws-users.com>
Sent: Tuesday, December 30, 2014 12:52 PM
Subject: [JAWS-Users] Quicken 2015


So has anybody taken the plunge so to speak? I have been using 2003 for over
11 years already as it has served me fairly well although it will not
install on my 64 bit 7 pro system. Now at this point it is not a problem
keeping a 32 bit system around I foresee a time when there will be nothing
but 64 bit units on the shelf.

If so please detail any experiences good or bad.
David Ferrin
A complex system that does not work is invariably found to have evolved from
a simpler system that worked perfectly.



For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/ 


For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/


For answers to frequently asked questions about this list visit:
http://www.jaws-users.com/help/

Reply via email to