[nfbcs] FW: JAWS scripting help requested for Remedy User client.

Sat May 11 20:15:40 UTC 2013

Tracy,
Please reply on this list how you get along. I know Gary Wunder tried to use the program and so did a man I work with at USDA.

Susie

-----Original Message-----
From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Tracy Carcione
Sent: Saturday, May 11, 2013 7:52 AM
To: NFB in Computer Science Mailing List
Subject: Re: [nfbcs] FW: JAWS scripting help requested for Remedy User client.

Thanks Louis!  I'll give this a try next week.
Tracy

----- Original Message -----
From: "Louis Maher" <ljmaher at swbell.net>
To: "NFB in Computer Science Mailing List" <nfbcs at nfbnet.org>
Sent: Friday, May 10, 2013 6:44 PM
Subject: [nfbcs] FW: JAWS scripting help requested for Remedy User client.

>
> -----Original Message-----
> From: Louis Maher [mailto:ljmaher at swbell.net]
> Sent: Friday, May 10, 2013 5:41 PM
> To: 'NFB in Computer Science Mailing List'
> Subject: RE: [nfbcs] JAWS scripting help requested for Remedy User client.
>
> Folks,
>
> The web-based Remedy can be quite accessible if you turn its accessibility
> features on.  The program shipps with accessibility disabled.
>
> My company calls the Web-based Remedy ITSM for IT service management.  To
> turn the accessibility features on requires the help of an ITSM
> administrator who can edit your profile.  I used ITSM in training last
> fall,
> but I have not used it much since then.
>
> Here are my rough notes on how to turn the accessibility in ITSM.
> Remember
> to call BMC for help if you need more help.
> -----
> "7603_Design Section 508 Applications.pdf  7604 Section 508 User
> Accessibility Options White Paper.pdf.  From 7604 Section 508 User
> Accessibility Options White Paper.pdf :   To ensure the best performance
> when you use BMC Remedy ITSM products with
> accessibility options, make sure that your software is configured
> correctly.
>
> NOTE
> You must have BMC Remedy AR System administrator permissions to change
> these
> settings.
> Configure your software as follows:
> Set preferences for each accessibility user in the BMC Remedy AR System
> User
> Preferences form. The accessibility options appear on the Accessibility
> tab.
> Each user must have a separate entry in the BMC Remedy AR System User
> Preferences form.
> From the Accessible Mode drop-down list, choose Default, Screen Magnifier/
> Low Vision, or Screen Reader/No Vision.
> From the Accessible Message drop-down list, choose No Action, Message
> Action, or All Actions.
> In the mid tier system that supports the deployed application, for the
> Preference Server setting, specify the server that contains the
> accessibility user preferences.
>
> Settings and software recommendations for using text-to-speech readers
>
> BMC Remedy IT Service Management 7.6.04
>
> Configuring the JAWS screen reading software This section explains the
> procedure to configure the BMC Remedy ITSM applications to use the JAWS
> screen reading software.
> To configure the JAWS screen reading software
> 1 Open the JAWS screen reading application.
> 2 Choose Utilities > Configuration Manager.
> Make sure that the focus is on the Configuration Manager window.
> 3 Choose Set Options > HTML Options. In version 7.6.04, choose HTML
> Options.
>
> Make sure that the focus is on the HTML Options dialog box.
> 4 Click the Links tab.
> 5 From the Text Link Options radio button group, select the Use Title
> Format
> option. In version 7.6.04, select the Use Title option.
> 6 Click OK.
> 7 Close the Configuration Manager.
> 8 On the relevant dialog box, confirm the Save Configuration option.
> 9 If you are using JAWS 11, for each machine:
> a Click Insert+Shift+V to open the Personalized Site Setting dialog.
> b Under Link Settings, highlight the Filter consecutive duplicate links
> option and click Execute.
> c Make sure the setting is set to Off.
> "----
>
> Note that JAWS 11 was invogue when this version of ITSM was shipped.
>
> Our ITSM BMC technical support person was Ed Moreno.  I do not have any
> current contact information for him.
>
>
> Regards
> Louis Maher
> 713-444-7838
> ljmaher at swbell.net
>
>
> -----Original Message-----
> From: nfbcs [mailto:nfbcs-bounces at nfbnet.org] On Behalf Of Steve Jacobson
> Sent: Friday, May 10, 2013 2:18 PM
> To: NFB in Computer Science Mailing List
> Subject: Re: [nfbcs] JAWS scripting help requested for Remedy User client.
>
> There is a setting that you can put into the AR.INI file for Remedy that
> makes it a little more useable.  You add a section and a setting that
> looks
> like this:
>
> [Accessibility]
> AccessibleMode=2
>
>
> A google search turned it up for me.  It was also in the Remedy Help, but
> the format was wrong there from what I could tell.
> There is also an option on the VIEW menu that causes a descriptive message
> about the current field with focus to be displayed on or above the Status
> Line.  I can't remember what it says, but the meaning is clear when you
> find
> it.  Unfortunately, I have not found a way to make the appearance of that
> information stay on by default.  Some fields work differently where you
> press ENTER on them to get a list of values and one just has to understand
> how some of these fields work.
>
> Maybe this will get you far enough to not need a script right away, or at
> least buy you some time.
>
> Best regards,
>
> Steve JacobsonS
>
> On Fri, 10 May 2013 09:00:14 -0400, Tracy Carcione wrote:
>
>>Hi Darrell.
>>I don't have any hints, but, if you get something working, I'd sure
>>like to see what you've got.  I was able to use an old version of
>>Remedy reasonably well, but my company switched to the web-based
>>client, and it's been impossible.  I can find some things, and other
>>things not at all. Luckily, it's only a tiny part of my job, and I've
>>been able to have someone else do it for me when I need it.
>>Tracy
>
>>----- Original Message -----
>>From: "Darrell Shandrow" <darrell.shandrow at gmail.com>
>>To: <nfbcs at nfbnet.org>
>>Sent: Thursday, May 09, 2013 7:02 PM
>>Subject: [nfbcs] JAWS scripting help requested for Remedy User client.
>
>
>>> Hello Everyone,
>>>
>>> I recently started a new job with a company that uses BMC's Remedy
>>> User software, version 7.6.04, for processing technical support cases.
>>> I have JAWS 14, which I am attempting to script to work with the
>>> Windows client version of Remedy.
>>>
>>> When the Remedy application for this company was developed, custom
>>> controls were used, thus making the mid-tier (web-based client) not
>>> an option for my particular setup.
>>>
>>> When scripting JAWS, I am noticing a situation where the current
>>> window, as defined by functions like GetCurrentWindow() seems to be
>>> split into at least three separate areas. When I am in one of these
>>> areas, I am unable to access information in other areas, even though
>>> it is visible and I can locate it using the JAWS cursor.
>>>
>>> Most of my scripts rely on the FindString() function in conjunction
>>> with GetCurrentWindow() to find information and read it, click
>>> something or take some similar action.
>>>
>>> My primary purpose for scripting Remedy is to allow me to assign
>>> keyboard commands to important fields, so I don't have to
>>> inefficiently use tab or shift+tab to navigate the forms.
>>>
>>> Does anyone out here have any ideas how I can use FindString() in a
>>> way that gets past this seemingly insurmountable screen boundary, or
>>> any other scripting techniques I may be able to use to get the job
>>> done?
>>>
>>> Thanks in advance for any help any of you can provide to point me in
>>> the right direction.
>>>
>>> Regards,
>>>
>>> Darrell
>>>
>>> _______________________________________________
>>> nfbcs mailing list
>>> nfbcs at nfbnet.org
>>> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>> To unsubscribe, change your list options or get your account info for
>>> nfbcs:
>>> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/carcione%40access.
>>> net
>>>
>
>
>>_______________________________________________
>>nfbcs mailing list
>>nfbcs at nfbnet.org
>>http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
>>To unsubscribe, change your list options or get your account info for
> nfbcs:
>>http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/steve.jacobson%40vis
>>i.com
>
>
>
>
>
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/ljmaher%40swbell.net
>
>
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/carcione%40access.net
>

_______________________________________________
nfbcs mailing list
nfbcs at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for nfbcs:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/susan.stanzel%40kcc.usda.gov

This electronic message contains information generated by the USDA solely for the intended recipients. Any unauthorized interception of this message or the use or disclosure of the information it contains may violate the law and subject the violator to civil or criminal penalties. If you believe you have received this message in error, please notify the sender and delete the email immediately.