[jawsscripts] Re: Modifying Jaws script for navigating between landmarks
- From: "Jim Snowbarger" <Snowman@xxxxxxxxxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Sat, 17 Nov 2012 18:13:13 -0600
I ran into this very same problem yesterday, As don describes, where script
manager kept forcing the jkm back to the original assignment. I still can't
figure out where the heck script manager is keeping that information.
After getting my jkm scrambled several times, and having to fix it manually,
I finally made a copy of it, in case it happened again, and started the
practice Don describes.
Does anybody know where the heck Script manager is storing that original
assignment?
I thought the JKM was the master.
----- Original Message -----
From: "Don Marang" <donald.marang@xxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Saturday, November 17, 2012 2:20 PM
Subject: [jawsscripts] Re: Modifying Jaws script for navigating between
landmarks
I think part of your problem in manually assigning keys is the order it
is done. This may be overkill, but I do the following to make sure
Script Manager is not confused. Remember, it keeps several files in sync.
First, I write the basic script in Script Manager. I make sure to
provide all of the info, including an unused dummy assigned key
combination, in the Script Information dialog (Control + d). Save and
compile with Control + s and then exit Script Manager. Yes, I
temporarily close Script Manager!
Then open the .jkm key map file and make the desired changes. In this
case, adding the layered syntax. Save and close the file.
Now when you open Script Manager again, it loads the correct data and is
not confused. I used to keep both open at the same time, and each time
I recompiled my scripts, it would change the key map file back to the
original.
*Don Marang*
Vinux Package Development Coordinator - vinuxproject.org
<http://www.vinuxproject.org/>
On 11/17/2012 1:39 PM, Travis Roth wrote:
> It sounds like you followed the correct protocol.
> JAWSKey+Space&m is by default a select to mark scrip by JAWS.
> Usually a .jkm file will override the default key assignments for that
> app.
> So you may have uncovered a bug/feature that multi-layer keys cannot be
> overridden?
> Key assignments can only be made to scripts, not functions.
> (Btw it appears jawskey+space&n is not bound to anything...)
>
>
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Léonie Watson
> Sent: Saturday, November 17, 2012 12:08 PM
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Modifying Jaws script for navigating between
> landmarks
>
> Thanks Sina. I've edited the firefox.jkm file in a text editor to add the
> following:
>
> JawsKey+Space&m=MoveToMain
>
> Where MoveToMain is the name of my script. I've saved the .jkm file and
> recompiled my firefox.jss file (just for completeness). The firefox.jss
> file
> includes the following:
>
> Script MoveToMain ()
> MoveToTagWithAttribute (s_top, "main", "role", true) SayMessage
> (OT_MESSAGE,
> "Start of main content area", "Main content area") EndScript
>
> When I try this, Jaws says "Set a temporary place marker with Control +
> Windows + k, then you can select between that place and your current
> location".
>
> I'm wondering if the layered keystroke should be attached to a function,
> rather than a script? That seems a bit inspecific though. Otherwise, I'm
> completely mystified now. Any ideas?
>
> Léonie.
>
>
>
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram
> Sent: 17 November 2012 17:45
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Modifying Jaws script for navigating between
> landmarks
>
> Sure, so, the general JKM format is simply the first standard keystroke
> combination for the layer, followed by the second or third with ampersand
> characters delimiting them per layer.
>
> Here's a single layer in the form of the flexible web dialog:
>
> JAWSKey+Space&X=DoFlexibleWebDialog
>
> If you want multiple layers, for example, let's say you want to make
> yourself a little test environment or sandbox layer to just put all your
> keystrokes in without polluting the rest of the namespace, then you can do
> multiple layers like the below OCR example:
>
> JAWSKey+Space&O&W=RecognizeRealWindow
>
> I hope that helps.
>
> Take care,
> Sina
>
> Website: www.SinaBahram.com
> Twitter: @SinaBahram
>
>
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Léonie Watson
> Sent: Saturday, November 17, 2012 12:34 PM
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Modifying Jaws script for navigating between
> landmarks
>
> Thanks Sina. Agree avoiding Jaws key m is a good idea.
>
> Could you tell me how to bind a script to a layered keystroke though? I
> can't seem to do it using the create script dialogue. It recognises Insert
> +
> space, but not the layered m.
>
> I haven't been able to find anything about layered keystrokes in the help
> manual (yet), or by Googling.
>
> Any help would be much appreciated.
>
> Léonie.
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Sina Bahram
> Sent: 15 November 2012 21:16
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Modifying Jaws script for navigating between
> landmarks
>
> insert+space is layered, so you'll have to express it that way, not just
> insert+as insert+space. I think some others will respond though,
> so I'll check back to make sure you're good on this, if it doesn't work
> for
> you. be careful of stuff like jawsKey+m, as that can map to priorCharacter
> in laptop layout.
>
>
>
> Website: www.SinaBahram.com
> Twitter: @SinaBahram
>
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Léonie Watson
> Sent: Thursday, November 15, 2012 1:42 PM
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Modifying Jaws script for navigating between
> landmarks
>
> Thanks Sina and Travis. I've been experimenting with that function, but
> I'm
> having some trouble getting it to work.
>
> I'm currently using it to create a shortcut to move to the <body> element,
> since I know that should be in Jaws' list of tags. I've added a script to
> the firefox.jss file, and from within it I've called that function.
>
> Script MoveToMain ()
> MoveToTag (s_top, "body")
> EndScript
>
> It's currently bound to Jaws key + m as a keystroke. I've compiled the
> script, checked the keyboard manager to confirm the keystroke is tied to
> the
> script, and tested it in Firefox.
>
> Guessing I'm missing something obvious. Any suggestions?
>
>
> On a related note, Sina suggested binding it to Jaws key + space, m. I
> don't
> seem to be able to replicate that keystroke in the key assignment field of
> the create script dialogue though. It recognises the Jaws key + space, but
> not the additional keystroke.
>
> Léonie.
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Travis Roth
> Sent: 15 November 2012 00:06
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Modifying Jaws script for navigating between
> landmarks
>
> Hi,
> JAWS has a MoveToTag() function.
> You could try something like
> MoveToTag (s_top, "main")
>
> I am not sure if JAWS loads any tag it finds into its tag list, or only
> officially recognized HTML tags, but you could try and find what
> happens...
>
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Léonie Watson
> Sent: Wednesday, November 14, 2012 3:59 PM
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Modifying Jaws script for navigating between
> landmarks
>
> Good evening,
>
>
> I'd like to create a proof of concept script for Jaws. It's to demonstrate
> how Jaws might support a new HTML5 element that's been proposed.
>
>
>
> I think there are two possible options. Either to modify the script that
> handles navigation between landmarks on web pages with the semi colon
> quick
> nav key, or to write a new script that introduces a new quick nav key
> based
> on the proposed element.
>
>
>
> A potential catch is that this new element doesn't exist yet, so there is
> no
> browser support for it. Jaws would need to take it from the HTML because
> no
> information will be available via the browser's accessibility API.
>
>
>
> If this is something that's likely to be browser specific, Firefox is my
> preferred browser for developing this proof of concept functionality.
>
>
>
> I'm an occasional Jaws scripter, but it's been a long time since I used it
> in anger. I'd appreciate any advice on the best approach to take,
> scripts/functions I would need to modify, and any pitfalls I should be
> aware
> of.
>
>
>
> I've searched the list archives (and will keep trying), but if there is
> existing information around this anywhere, links and/or reading material
> happily received as well. Thanks.
>
>
>
> Léonie.
>
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
Other related posts: