W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2004

Re: moving text and Assistive Technology

From: david poehlman <david.poehlman@handsontechnologeyes.com>
Date: Thu, 9 Dec 2004 09:27:26 -0500
Message-ID: <001b01c4ddfb$3848ee50$6401a8c0@DAVIDPC>
To: "John M Slatin" <john_slatin@austin.utexas.edu>, Léonie Watson <lw@nomensa.com>, "Charles McCathieNevile" <charles@sidar.org>, <w3c-wai-ig@w3.org>

I have all refreshes suppressed and did not hear anything that sounded like 
movement but as I used the arrow keys to move through the page I heard edit 
a lot.  Now, when I used f to jump from form field to form feild, those 
edits were not included in the jump.  Also, when I tabbed, they were skipped 
so I don't exactly know what is going on with the page.

Johnnie Apple Seed

----- Original Message ----- 
From: "John M Slatin" <john_slatin@austin.utexas.edu>
To: "Léonie Watson" <lw@nomensa.com>; "Charles McCathieNevile" 
<charles@sidar.org>; <w3c-wai-ig@w3.org>
Sent: Thursday, December 09, 2004 8:44 AM
Subject: RE: moving text and Assistive Technology



Charles, when I went to the page at

http://www.bendigo2004.com/

JAWS 5.1 continually repeated the word "edit" as it read down the page (this 
is the way JAWS signals the presence of an <input> of type="text"). 
However, as far as I can tell there is only one text input element on the 
page (it does not have a label). The repetition may be an artifact of the 
moving text elsewhere on the page-- I don't know how else to account for it.

As for the moving text itself, I'm not certain whether JAWS reported it or 
not-- I did hear some things that sounded as if they might be coming from a 
news-ticker sort of thing-- there were numbers like 22.04 and 19-something, 
if that helps you determine whether what I heard was indeed the moving text.

John


"Good design is accessible design."
John Slatin, Ph.D.
Director, Accessibility Institute
University of Texas at Austin
FAC 248C
1 University Station G9600
Austin, TX 78712
ph 512-495-4288, f 512-495-4524
email jslatin@mail.utexas.edu
web http://www.utexas.edu/research/accessibility/






-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf 
Of Léonie Watson
Sent: Thursday, December 09, 2004 4:48 am
To: Charles McCathieNevile; w3c-wai-ig@w3.org
Subject: Re: moving text and Assistive Technology



Charles,

    Jaws v5.1 does appear to have a problem with this page, although I'm not
certain of a direct relationship with the moving content.

    From the point on the page immediately below the submit button of the
search form, to the graphical link with the file path: images/victorianlogo,
Jaws treats the entire content as a text input form field.
    It is possible to activate Forms Mode with Jaws, but not possible to
input any text having done so.

    The effect of this is that Jaws speaks the word "edit" on every line as
I arrow up and down the page. Conversely, if I use the Jaws quick nav key
"f" to cycle through form fields on a page, the only fields acknowledged are
the text input and submit button of the search form.

Regards,
Léonie.
----- Original Message ----- 
From: "Charles McCathieNevile" <charles@sidar.org>
To: <w3c-wai-ig@w3.org>
Sent: Thursday, December 09, 2004 4:19 AM
Subject: moving text and Assistive Technology


>
> Hi folks,
>
> I am evaluating the Bendigo Commenwealth Student Games 2004 site as a
> favour, and I came across something that made me think.
>
> Checkpoint 8.1 requires that scripts (and things) are directly
> accessible. I recall that there were problems with the Tiflowin screen
> reader (once widely used in spanish, now apparently common only in
> South America) refocusing whenever things moved on the screen.
>
> I understand the problems caused by movement in terms of tracking
> things, but I am wondering if anyone can tell me of any named
> assistive technology that breaks down when something moves. In this
> case the effect is achieved by javascript being used to continually
> change a set of CSS position properties in a style attribute - the
> page in question is http://www.bendigo2004.com/
>
> For extra value an idea of who is using the particular technology
> would be useful.
>
> I am not interested in general answers - I understand the general
> issues. I am looking for any specific data that can be empirically
> tested and verified.
>
> (This is the stuff that EuroAccessibility was doing - it seems a shame
> that they have stopped).
>
> -- 
> Charles McCathieNevile           charles@sidar.org
>                 http://www.sidar.org
>
>
>
----- Original Message ----- 
From: "Charles McCathieNevile" <charles@sidar.org>
To: <w3c-wai-ig@w3.org>
Sent: Thursday, December 09, 2004 4:19 AM
Subject: moving text and Assistive Technology


>
> Hi folks,
>
> I am evaluating the Bendigo Commenwealth Student Games 2004 site as a
> favour, and I came across something that made me think.
>
> Checkpoint 8.1 requires that scripts (and things) are directly
> accessible. I recall that there were problems with the Tiflowin screen
> reader (once widely used in spanish, now apparently common only in
> South America) refocusing whenever things moved on the screen.
>
> I understand the problems caused by movement in terms of tracking
> things, but I am wondering if anyone can tell me of any named
> assistive technology that breaks down when something moves. In this
> case the effect is achieved by javascript being used to continually
> change a set of CSS position properties in a style attribute - the
> page in question is http://www.bendigo2004.com/
>
> For extra value an idea of who is using the particular technology
> would be useful.
>
> I am not interested in general answers - I understand the general
> issues. I am looking for any specific data that can be empirically
> tested and verified.
>
> (This is the stuff that EuroAccessibility was doing - it seems a shame
> that they have stopped).
>
> -- 
> Charles McCathieNevile           charles@sidar.org
>                 http://www.sidar.org
>
>
>
Received on Thursday, 9 December 2004 14:28:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:18 GMT