[jawsscripts] Re: Element attribute values.

  • From: "Sean Randall" <seanr@xxxxxxxxxxxxxxx>
  • To: <jawsscripts@xxxxxxxxxxxxx>
  • Date: Mon, 4 May 2009 11:21:54 +0100


The  "use virtual.jsb" statement appears in default.jss, which makes
everything in virtual available in default.
The trick is that whereas keys on scripts are usually either assigned to
common, desktop, or laptop keyboard layouts, these scripts are assigned to
"quick keys".   I'm assuming that whenever the virtual cursor is on and
focus is in an  appropriate web-based control (i.e. a web page, chm window,
pdf document etc) then  these keys become active.

This means that keys like "e" for edit and "f" for form don't get triggered
in general circumstances but are available when the cursor mode is right.
You could manually edit the JKM file to amend your chosen keystrokes to this
section; which is what I ended up doing for Thunderbird.  In that instance I
edited thunderbird and not default, of course, so for instance in normal
cases F moved between form fields but only in thunderbird did F move to the
next unread message, or whatever the key was supposed to do.

If you're customizing for the web you may want to decide whether you're
aiming for a "global" virtual change, or just a "browser"  one (where you'd
modify firefox and IE rather than everything).  The latter means that you
might not grab all browsers that render in standard HTMl controls (perhaps
some chm reference materials would use the accessibility value and you'd
have missed out). On the other hand, you'd be ading an extra key to
everywhere virtual pc is used, which might not be what you want.


Hope that clarifies some, shout at me if not...

-----Original Message-----
From: jawsscripts-bounce@xxxxxxxxxxxxx
[mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Léonie Watson
Sent: 04 May 2009 01:20
To: jawsscripts@xxxxxxxxxxxxx
Subject: [jawsscripts] Re: Element attribute values.

        I've had a look at the virtual.jss file Sean, thanks. It makes sense
for me to include these scripts in there, given what I'm trying to
accomplish. I'm a bit puzzled as to how it would work in practice though.

        Looking at a couple of scripts within the virtual.jss file, I
noticed that although they are checked to accept a key command, they don't
have them assigned. Looking at the InternetExplorer.jss file, I noticed that
it uses the "Use" statement to reference the virtual.jsb file, so assume
this is how the connection between the two is made.

        Am I right in thinking that all the scripts in the virtual.jsb file
are then available to the InternetExplorer.jss file? If so, how does the key
mapping fit in? Sorry for all the questions!

        This script is an exercise to support a suggestion that has been
made to the HTML 5 working group. The HTML 5 specification is being
developed at the moment, and someone has suggested that an additional value
for the rel="" attribute be included: accessibility.

        The idea being that web developers could include the attribute/value
combination on their pages, to reference links or other elements related to
accessibility. The HTML 5 working group prefer that there is a working case
for ideas, before they're added to the specification. A group from the web
standards community are putting together some test cases and working
examples, to see whether the idea has any real life application.



Email: tink@xxxxxxxxxx
Twitter: LeonieWatson

Visit and contribute to The JAWS Script Repository http://jawsscripts.com

View the list's information and change your settings at 

Other related posts: