RE: Accessibility
- From: "Ryan Stevens" <RYSteve@xxxxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Thu, 18 Aug 2011 21:11:08 -0400
Also, checkboxes read well, and I agree with you Rodney about textboxes and
command buttons.
Ryan
_____
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Rodney Haynie
Sent: Thursday, August 18, 2011 2:27 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Accessibility
Ok, well the controls within a VFP application are somewhat accessible when
you look at it from an end-user perspective.
When you move from control to control using the Tab key for example, JAWS
may not read things so well. You will definitely have to make use of the
JAWS cursor at times to read the label associated with a text box. But if
the developer named the textbox control well, i.e. txtFirstName), then you
will know exactly what it is the textbox wants. As opposed to txtText1.
Command buttons, if holding a text caption, will read well.
Option buttons will read well.
Comboboxes, depending on how it was setup by the developer, may be pretty
horrible, only telling you the value of the item you selected. Such as 19 of
37. But you can work-around it by making use of the JAWS cursor again, it
just will take longer.
Listboxes work well enough.
Basically, the app created from VFP can be pretty horrible if the developer
coded in specific ways. I know, that is a very generic statement, but it
will be impossible to comment too much more without having the exact app in
front of me.
Right now I am working with a VFP app, and I can move through the controls,
and do things without thought because I am use to the work-arounds, and I
had the ability to go into code and make changes if I really needed to do
so. Most end-user won't have this luxury of course, but that is where I am
at the moment.
Take care.
Rodney
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Mullins
Sent: Thursday, August 18, 2011 12:22 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Accessibility
Thenks for these comments guys, I'll certainly get back to you if I get to
the next interview stage. I don't know as I will be using VFP itself, it
sounds like it's an in-house language that uses an IDE that was created
using VFP. So the IDE application uses forms/controls/menus which were
obtained from the VFP toolbox and it's the accessibility of these with Jaws
I'm questioning.
Cheers
Chris
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Rodney Haynie
Sent: 18 August 2011 14:00
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Accessibility
Adding to these excellent comments, I will say it is very important to find
out what version of VFP the client is currently using for development of
those applications.
VFP8 and VFP 9 are the most accessible of the VFP versions. My experience is
that I could not do any development using Access Technology (in my case
JAWS) using VFP 7 or VFP 6.
I have a good amount of experience creating applications using FoxPro, going
back to 2.5 dos/windows. But I was not using Access Technology back then. I
started using AT when VFP 8 came out.
There are absolutely loads of work-around I use to developed in the
environment, but I try not to do much of any user interface creation any
more. I will defer that to a colleague, and then modify the forms and
reports once the generic structure is created and laid out.
So, if you have any specific VFP questions in the future, don't hesitate to
send them over the list.
HTH.
Rodney
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Ryan Stevens
Sent: Thursday, August 18, 2011 7:13 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Accessibility
Hi, Chris,
We have a couple of legacy apps for running monthly reports that were
written in Visual FoxPro. I will admit that I created them when I was still
using ZoomText and I've only done minor mods to them in the past few years.
With JAWS, working with the database tables is pretty accessible, as is
IntelliSense in the Command window. The code editor is readable, but I
often get a repetition problem when moving from line to line. Also, it does
not read highlighted text anywhere near correctly. Moving around the
Property window takes some playing around, including needing alot of the
JAWS cursor. I haven't placed any controls on a form in a very long time,
but from what I remember, the accessibility of both the form and the toolbox
are between slim and none. Overall, unless there is a JAWS script for VFP
9.0, I'd be rather wary of trying to work with it for heavy duty
development.
Ryan Stevens
_____
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Chris Mullins
Sent: Thursday, August 18, 2011 5:26 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: Accessibility
Hi
I've applied for a job where the Company have an in-house developed
programming tool, developed using FoxPro. Do any of you guys have any
experience of using FoxPro and if so, are the forms, menus and controls
likely to be accessible using Jaws?
Cheers
Chris
_____
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1392 / Virus Database: 1520/3841 - Release Date: 08/17/11
Other related posts:
