FLUID-492: JAWS difficulty exiting Virtual PC Cursor to navigate in Lightbox

Metadata

Source
FLUID-492
Type
Bug
Priority
Critical
Status
Closed
Resolution
Fixed
Assignee
Anastasia Cheetham
Reporter
Zachariah Cameron
Created
2008-04-10T19:24:42.000-0400
Updated
2008-12-12T16:22:36.000-0500
Versions
  1. 0.1
  2. 0.3
  3. 0.4beta1
  4. 0.4
  5. 0.5beta1
  6. 0.5
Fixed Versions
  1. 0.6
Component
  1. Reorderer

Description

In each of the environments listed, it was difficult to exit JAWS Virtual PC Cursor in order to use the I,J,K,M keys to navigate through the available images.
Ordinarily one enters <INS>z to drop out of the JAWS Virtual PC Cursor and in this case should simply be able to use the designated keys for navigation. In most cases it was possible to get around this by 'playing' with the arrow keys and then going back to the provided navigation keys.

Environments

Windows XP SP2; Vista Business; JAWS 7, 8, &9; Firefox2; IE7

Comments

  • Anastasia Cheetham commented 2008-04-17T14:16:48.000-0400

    Zach, can you describe the issue a bit more? What is it that happens when you enter <INS>z? Does it not drop out of Virtual PC Cursor?

    On our test machine, we were able to type <INS>z to drop out of Virtual Cursor mode, and after that the navigation keys (I, J, K, M) worked fine.

  • Zachariah Cameron commented 2008-04-23T16:31:15.000-0400

    Perhaps this gives a fuller and clearer description of the behaviour as I found it.

    <INS>z to exit Virtual PC Cursor

    DELL Precision 690 Win Vista Ultimate
    = = = = = = = = = =

    JAWS 9
    IE 7

    • - - - -

    JAWS voices:-

    • - - - -

    To use the keyboard:

    Select an image using i, k, m or j, or the arrow keys.
    View an image by pressing Enter.
    Move an image using CTRL + a direction key.

    which seems to imply that IJKM are sufficient to select an image.
    At that point if you drop out of Vitual PC Cursor these keys do not work. One
    must still tab into the windows.
    I am not sure this would be evident to the average JAWS user, nor am I certain
    if this is a function of the tool, or of the page design.

    JAWS 9
    Firefox 2

    • - - - -

    JAWS does not voice the entire

    To use the keyboard:
    Select an image using i, k, m or j, or the arrow keys.
    View an image by pressing Enter.
    Move an image using CTRL + a direction key.

    when tabbing through the screen. In my experience it sometimes voices nothing
    and other times voices only

    by pressing Enter.
    Move an image using CTRL + a direction key.

    In this configuration I can, thus far, find no way to have the instructions
    voiced in their entirety.

    Also, in Firefox, when tabbing through, this instruction screen is reached
    after getting to the graphic content so would not be immediately evident.

    Dell Precision M20 laptop Win XP SP2
    = = = = = = = = = =

    JAWS 7
    Firefox 2

    • - - - -

    JAWS voices the instructions 'To use the keyboard,,,' but following those instructions at that point does not do the job. One must hit the tab key to gain access to the images and, occasionally, a single tab is not sufficient.

    JAWS 7
    IE 7

    • - - - -
      Quite similar to exprience with Firefox and this version of JAWS but required more tabbing to get to the point where IJMK were properly functional.

    DELL Optiplex 755 Win Vista Business
    = = = = = = = = = =

    JAWS 9
    Firefox 2

    • - - - -

    To use the keyboard:

    Select an image using i, k, m or j, or the arrow keys.
    View an image by pressing Enter.
    Move an image using CTRL + a direction key.

    This is not read at all when tabbing around the document. Being sighted, I can see when the selection has fallen on this box. Seing that, if I press the down arrow I get

    by pressing Enter.
    Move an image using CTRL + a direction key.

    and knowing there is more there, I can get it voiced eventually.

    JAWS 9
    IE 7

    • - - - -

    Same as above.

    Difficult to get tabbed into the correct place.

    = = = =
    In each case, if you know what is needed, you can manage to get IJKM to work but you
    may lose your audience before they get there.
    You can also get the information by using the read all command but I would argue that ought not to be necessary.

  • Michael Elledge commented 2008-05-27T16:45:51.000-0400

    I've checked the Lightbox with IE 7 and JAWS 7 and found that it works, but only when the virtual cursor is turned off. Since many (perhaps most) screen reader users will have no idea that this may be the source of their problems, or know how to resolve it, it is critical that they be told that "Screen reader users must turn off the Virtual Cursor (ins + z)" for Lightbox to work. Of course, it would be best if they didn't have to go through that step at all.

    Here are several other suggestions to improve accessibility and usability for persons with disabilities:

    2) add a description of what the Lightbox tool does: "This is the Lightbox demo page. User the Lightbox tool to rearrange items on a page",
    3) indicate that a new page will open when an item is selected,
    4) indicate that alt + left arrow will return you to the main page from the selected item, and
    5) improve the page title for each selected items page ("Small cluster of blackberries" rather than the URL).

    If possible:
    6) indicate which item precedes and which item follows an item after it has been moved, and
    7) add mechanism for sorting items alphabetically (will provide consistent starting point for persons with cognitive issues or who are blind).

    I have attached word document which describes what happened with virtual PC turned on and off.

  • Justin Obara commented 2008-07-28T10:41:54.000-0400

    Going along with the comments above, it would seem that the instructions text needs to be updated.

    A screen reader should tell the user to do the following:

    1) Press tab to go to the lightbox

    2) turn browse mode off.
    It would be nice if this information was presented to screen readers only, as it wouldn't make sense to a non-screen reader user.

  • Justin Obara commented 2008-12-03T12:12:17.000-0500

    Bug Parade 0.6 release

  • Justin Obara commented 2008-12-12T16:22:36.000-0500

    fixed along with FLUID-1821