WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: strange sr issue

for

Number of posts in this thread: 7 (In chronological order)

From: Jennison Mark Asuncion
Date: Wed, Sep 10 2014 9:55AM
Subject: strange sr issue
No previous message | Next message →

Hi,

I'm experiencing an issue that I haven't seen before, which is only
happening when a screen reader is running. In a set of otherwise
accessible web pages, on some pages, the screen reader will
immediately go to the bottom of the page. Again, this is not happening
on all pages, and has been seen with VO and Safari, NVDA and FF/IE,
and JAWS with IE/FF.

Has anyone else experienced this type of behavior? I figure it will
end up being something simple being overlooked. If folks have guidance
on things to check, in order to troubleshoot this, that would be
appreciated.

Jennison

From: deborah.kaplan@suberic.net
Date: Wed, Sep 10 2014 9:59AM
Subject: Re: strange sr issue
← Previous message | Next message →

I have recently encountered some pages with a form at the bottom of the
page which captures the keyboard focus via JavaScript, and drags the screen
reader cursor down with it. Could it be something like that?

Deborah Kaplan

On Wed, 10 Sep 2014, Jennison Mark Asuncion wrote:

> Hi,
>
> I'm experiencing an issue that I haven't seen before, which is only
> happening when a screen reader is running. In a set of otherwise
> accessible web pages, on some pages, the screen reader will
> immediately go to the bottom of the page. Again, this is not happening
> on all pages, and has been seen with VO and Safari, NVDA and FF/IE,
> and JAWS with IE/FF.
>
> Has anyone else experienced this type of behavior? I figure it will
> end up being something simple being overlooked. If folks have guidance
> on things to check, in order to troubleshoot this, that would be
> appreciated.
>
> Jennison
> > > >
>

--

From: Jennison Mark Asuncion
Date: Wed, Sep 10 2014 10:10AM
Subject: Re: strange sr issue
← Previous message | Next message →

Hi,

I'll recheck, but I've been told that when a screen reader is not
running, focus acts correctly on all pages.


Jennison
On 9/10/14, = EMAIL ADDRESS REMOVED = < = EMAIL ADDRESS REMOVED = > wrote:
> I have recently encountered some pages with a form at the bottom of the
> page which captures the keyboard focus via JavaScript, and drags the screen
> reader cursor down with it. Could it be something like that?
>
> Deborah Kaplan
>
> On Wed, 10 Sep 2014, Jennison Mark Asuncion wrote:
>
>> Hi,
>>
>> I'm experiencing an issue that I haven't seen before, which is only
>> happening when a screen reader is running. In a set of otherwise
>> accessible web pages, on some pages, the screen reader will
>> immediately go to the bottom of the page. Again, this is not happening
>> on all pages, and has been seen with VO and Safari, NVDA and FF/IE,
>> and JAWS with IE/FF.
>>
>> Has anyone else experienced this type of behavior? I figure it will
>> end up being something simple being overlooked. If folks have guidance
>> on things to check, in order to troubleshoot this, that would be
>> appreciated.
>>
>> Jennison
>> >> >> >>
>>
>
> --
> > > >

From: Pratik Patel
Date: Wed, Sep 10 2014 10:26AM
Subject: Re: strange sr issue
← Previous message | Next message →

Hello Jennison,

Do you have an example that you can point to? Or are these internal feet facing pages that we are not able to take a look at? If I had to guess, I would take a look at modal dialog and JavaScript.

Regards,



Sent from my iPhone

On Sep 10, 2014, at 12:10 PM, Jennison Mark Asuncion < = EMAIL ADDRESS REMOVED = > wrote:

Hi,

I'll recheck, but I've been told that when a screen reader is not
running, focus acts correctly on all pages.


Jennison
> On 9/10/14, = EMAIL ADDRESS REMOVED = < = EMAIL ADDRESS REMOVED = > wrote:
> I have recently encountered some pages with a form at the bottom of the
> page which captures the keyboard focus via JavaScript, and drags the screen
> reader cursor down with it. Could it be something like that?
>
> Deborah Kaplan
>
>> On Wed, 10 Sep 2014, Jennison Mark Asuncion wrote:
>>
>> Hi,
>>
>> I'm experiencing an issue that I haven't seen before, which is only
>> happening when a screen reader is running. In a set of otherwise
>> accessible web pages, on some pages, the screen reader will
>> immediately go to the bottom of the page. Again, this is not happening
>> on all pages, and has been seen with VO and Safari, NVDA and FF/IE,
>> and JAWS with IE/FF.
>>
>> Has anyone else experienced this type of behavior? I figure it will
>> end up being something simple being overlooked. If folks have guidance
>> on things to check, in order to troubleshoot this, that would be
>> appreciated.
>>
>> Jennison
>> >> >> >
> --
> > >

From: David Farough
Date: Wed, Sep 10 2014 11:43AM
Subject: Re: strange sr issue
← Previous message | Next message →

I have noticed something like this with one of our applications.
It uses version 3 of the Web Experience toolkit. one of the options in
the WET navigation menus accesses application help information.

When you activate the help menu option, from the menu, a new help page
is presented. Jaws will begin reading information on the page, but will
stop reading the page content at some point, the focus will then be at
the very end of the page. it is then necessary to move up to find the
place where Jaws stopped reading in order to hear the rest of the
content. I think in this case this happens due to something within the
WET Menus.

David Farough
coordonateur de l'accessibilité
/Application Accessibility Coordinator
Direction des services d'information technologiques /
Information Technology Services Directorate
Commission de la fonction publique /Public Service Commission
Courriel / Email: = EMAIL ADDRESS REMOVED =
Tél / Tel. (819) 420-8418


>
Ce courriel est destiné exclusivement au destinataire mentionné en titre
et peut contenir de l'information privilégiée, confidentielle ou
soustraite à la communication aux termes des lois applicables. Toute
divulgation non autorisée, toute reproduction ou réacheminement est
interdit. Si vous n'êtes pas le destinataire de ce courriel, ou n'êtes
pas autorisé par le destinataire visé, ou encore, si vous l'avez reçu
par erreur, veuillez le mentionner immédiatement à l'expéditeur et
supprimer le courriel et les copies.

>
This e-mail message is intended for the named recipient(s) and may
contain information that is privileged, confidential and/or exempt from
disclosure under applicable law. Unauthorized disclosure, copying or
re-transmission is prohibited. If you are not a named recipient or not
authorized by the named recipient(s), or if you have received this
e-mail in error, then please notify the sender immediately and delete
the message and any copies.

From: Bim Egan
Date: Wed, Sep 17 2014 4:48AM
Subject: Re: strange sr issue
← Previous message | Next message →

Hi,

I've seen this in a few applications that are written as a single page, but
scripted to show a given number of "page views", like a multi-part form, but
without having to run a server session. The focus landing at the bottom of
the page was an issue for all keyboard users though, not just those using
SR. The Visual focus was fine, it was just the keyboard focus that was a
problem.

It was cured by using JS to position the focus at the top of each new "page
view".

Bim


-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of David Farough
Sent: 10 September 2014 18:44
To: webaim-forum
Subject: Re: [WebAIM] strange sr issue

I have noticed something like this with one of our applications.
It uses version 3 of the Web Experience toolkit. one of the options in the
WET navigation menus accesses application help information.

When you activate the help menu option, from the menu, a new help page is
presented. Jaws will begin reading information on the page, but will stop
reading the page content at some point, the focus will then be at the very
end of the page. it is then necessary to move up to find the place where
Jaws stopped reading in order to hear the rest of the content. I think in
this case this happens due to something within the WET Menus.

David Farough
coordonateur de l'accessibilité
/Application Accessibility Coordinator
Direction des services d'information technologiques / Information Technology
Services Directorate Commission de la fonction publique /Public Service
Commission Courriel / Email: = EMAIL ADDRESS REMOVED =
Tél / Tel. (819) 420-8418


>
Ce courriel est destiné exclusivement au destinataire mentionné en titre et
peut contenir de l'information privilégiée, confidentielle ou soustraite à
la communication aux termes des lois applicables. Toute divulgation non
autorisée, toute reproduction ou réacheminement est interdit. Si vous n'êtes
pas le destinataire de ce courriel, ou n'êtes pas autorisé par le
destinataire visé, ou encore, si vous l'avez reçu par erreur, veuillez le
mentionner immédiatement à l'expéditeur et supprimer le courriel et les
copies.

>
This e-mail message is intended for the named recipient(s) and may contain
information that is privileged, confidential and/or exempt from disclosure
under applicable law. Unauthorized disclosure, copying or re-transmission is
prohibited. If you are not a named recipient or not authorized by the named
recipient(s), or if you have received this e-mail in error, then please
notify the sender immediately and delete the message and any copies.


messages to = EMAIL ADDRESS REMOVED =

From: Hans Hillen
Date: Fri, Sep 19 2014 5:09PM
Subject: Re: strange sr issue
← Previous message | No next message

Hi Jennison,

I've seen this occasionally in a specific screen reader, not consistently
in all screen readers though. I've always attributed it to overall screen
reader bugginess. If you have a URL for me I would be interested to have a
closer look at it.

On Wed, Sep 17, 2014 at 10:48 PM, Bim Egan < = EMAIL ADDRESS REMOVED = > wrote:

> Hi,
>
> I've seen this in a few applications that are written as a single page, but
> scripted to show a given number of "page views", like a multi-part form,
> but
> without having to run a server session. The focus landing at the bottom
> of
> the page was an issue for all keyboard users though, not just those using
> SR. The Visual focus was fine, it was just the keyboard focus that was a
> problem.
>
> It was cured by using JS to position the focus at the top of each new "page
> view".
>
> Bim
>
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of David Farough
> Sent: 10 September 2014 18:44
> To: webaim-forum
> Subject: Re: [WebAIM] strange sr issue
>
> I have noticed something like this with one of our applications.
> It uses version 3 of the Web Experience toolkit. one of the options in the
> WET navigation menus accesses application help information.
>
> When you activate the help menu option, from the menu, a new help page is
> presented. Jaws will begin reading information on the page, but will stop
> reading the page content at some point, the focus will then be at the very
> end of the page. it is then necessary to move up to find the place where
> Jaws stopped reading in order to hear the rest of the content. I think in
> this case this happens due to something within the WET Menus.
>
> David Farough
> coordonateur de l'accessibilité
> /Application Accessibility Coordinator
> Direction des services d'information technologiques / Information
> Technology
> Services Directorate Commission de la fonction publique /Public Service
> Commission Courriel / Email: = EMAIL ADDRESS REMOVED =
> Tél / Tel. (819) 420-8418
>
>
> >
> Ce courriel est destiné exclusivement au destinataire mentionné en titre et
> peut contenir de l'information privilégiée, confidentielle ou soustraite à
> la communication aux termes des lois applicables. Toute divulgation non
> autorisée, toute reproduction ou réacheminement est interdit. Si vous
> n'êtes
> pas le destinataire de ce courriel, ou n'êtes pas autorisé par le
> destinataire visé, ou encore, si vous l'avez reçu par erreur, veuillez le
> mentionner immédiatement à l'expéditeur et supprimer le courriel et les
> copies.
>
> >
> This e-mail message is intended for the named recipient(s) and may contain
> information that is privileged, confidential and/or exempt from disclosure
> under applicable law. Unauthorized disclosure, copying or re-transmission
> is
> prohibited. If you are not a named recipient or not authorized by the named
> recipient(s), or if you have received this e-mail in error, then please
> notify the sender immediately and delete the message and any copies.
>
>
> > > messages to = EMAIL ADDRESS REMOVED =
>
> > > >