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 10:48:12 UTC