E-mail List Archives

Search E-mail List Archives for

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

From: Craig Haydon
Date: Mon, Jan 12 2015 2:03PM
Subject: Jaws on Chrome reads links incorrectly
No previous message | Next message →

Hi Gang,
Here's a curly one.
I have a large complex site running AngularJS.
The first 2 links on the page are read by Jaws incorrectly, instead, the page title is read out! (when tabbing thru the links).
BUT, if you go in reverse (i.e shift tab) the first 2 links are read as normal (the first one is a skip to content link and the second one being a logo)

This weird behaviour only happens on Jaws (latest) on Windows running Chrome. IE behaves as expected ... and FF reads page title then the link...hmm..

Anyone with any suggestions what this might be?

From: Jonathan Avila
Date: Mon, Jan 12 2015 2:23PM
Subject: Re: Jaws on Chrome reads links incorrectly
← Previous message | Next message →

Craig, can you paste in the DOM of the links? Sometimes this can be caused by the implementation such as visibility of the links.

Jon


> On Jan 12, 2015, at 4:07 PM, Craig Haydon < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hi Gang,
> Here's a curly one.
> I have a large complex site running AngularJS.
> The first 2 links on the page are read by Jaws incorrectly, instead, the page title is read out! (when tabbing thru the links).
> BUT, if you go in reverse (i.e shift tab) the first 2 links are read as normal (the first one is a skip to content link and the second one being a logo)
>
> This weird behaviour only happens on Jaws (latest) on Windows running Chrome. IE behaves as expected ... and FF reads page title then the link...hmm..
>
> Anyone with any suggestions what this might be?
> > >

From: Craig Haydon
Date: Tue, Jan 13 2015 2:08PM
Subject: Re: Jaws on Chrome reads links incorrectly: Update
← Previous message | Next message →

Hi Jon,
The links are as plain as can be and are always visible.
<a tabindex="1" href="#content" title="Skip to content">Skip to content</a>


Even moving the html (skip to content) out of angular and putting as the
first element after the body didn't make a difference. Its definitely
angular (well I think soŠ but perhaps its JAWS??).. but no amount of
detective work has proved conclusive. Its very intermittent,
dev/int/staging all do it regularly yet current prod i can only make it
every so often. It seems somehow related to time and perhaps the order of
events. I am dubious about the manipulation of the page title/meta-data
when angular loads (service).. but can't prove it.

JAWS is seeing the link as being blank (i.e no text) and hence why it
defaults to reading the page title. I am aware that you can change link
text settings/option in JAWS, but currently its at default (i.e read link
text).

Debugging is difficult as the dev tools (chrome) can¹t be open at the same
time (with JAWS) as it crashes Chrome.


Thought someone may have seen this issue before... but maybe I am the
first.


PS: Hopefully I have replied to the correct return email.. Apologies if I
haven¹t.


On 13/01/2015 8:23 am, "Jonathan Avila" < = EMAIL ADDRESS REMOVED = > wrote:

>Craig, can you paste in the DOM of the links? Sometimes this can be
>caused by the implementation such as visibility of the links.
>
>Jon
>
>
>> On Jan 12, 2015, at 4:07 PM, Craig Haydon
>>< = EMAIL ADDRESS REMOVED = > wrote:
>>
>> Hi Gang,
>> Here's a curly one.
>> I have a large complex site running AngularJS.
>> The first 2 links on the page are read by Jaws incorrectly, instead,
>>the page title is read out! (when tabbing thru the links).
>> BUT, if you go in reverse (i.e shift tab) the first 2 links are read as
>>normal (the first one is a skip to content link and the second one being
>>a logo)
>>
>> This weird behaviour only happens on Jaws (latest) on Windows running
>>Chrome. IE behaves as expected ... and FF reads page title then the
>>link...hmm..
>>
>> Anyone with any suggestions what this might be?
>> >> >> >

From: Jonathan Avila
Date: Tue, Jan 13 2015 2:30PM
Subject: Re: Jaws on Chrome reads links incorrectly: Update
← Previous message | No next message

Perhaps it is a timing issue with content loading. Generally we don't recommend setting any tabindex above 0. Placement in the DOM is preferred.

Jon


> On Jan 13, 2015, at 4:10 PM, Craig Haydon < = EMAIL ADDRESS REMOVED = > wrote:
>
> Hi Jon,
> The links are as plain as can be and are always visible.
> <a tabindex="1" href="#content" title="Skip to content">Skip to content</a>
>
>
> Even moving the html (skip to content) out of angular and putting as the
> first element after the body didn't make a difference. Its definitely
> angular (well I think soŠ but perhaps its JAWS??).. but no amount of
> detective work has proved conclusive. Its very intermittent,
> dev/int/staging all do it regularly yet current prod i can only make it
> every so often. It seems somehow related to time and perhaps the order of
> events. I am dubious about the manipulation of the page title/meta-data
> when angular loads (service).. but can't prove it.
>
> JAWS is seeing the link as being blank (i.e no text) and hence why it
> defaults to reading the page title. I am aware that you can change link
> text settings/option in JAWS, but currently its at default (i.e read link
> text).
>
> Debugging is difficult as the dev tools (chrome) can¹t be open at the same
> time (with JAWS) as it crashes Chrome.
>
>
> Thought someone may have seen this issue before... but maybe I am the
> first.
>
>
> PS: Hopefully I have replied to the correct return email.. Apologies if I
> haven¹t.
>
>
>> On 13/01/2015 8:23 am, "Jonathan Avila" < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> Craig, can you paste in the DOM of the links? Sometimes this can be
>> caused by the implementation such as visibility of the links.
>>
>> Jon
>>
>>
>>> On Jan 12, 2015, at 4:07 PM, Craig Haydon
>>> < = EMAIL ADDRESS REMOVED = > wrote:
>>>
>>> Hi Gang,
>>> Here's a curly one.
>>> I have a large complex site running AngularJS.
>>> The first 2 links on the page are read by Jaws incorrectly, instead,
>>> the page title is read out! (when tabbing thru the links).
>>> BUT, if you go in reverse (i.e shift tab) the first 2 links are read as
>>> normal (the first one is a skip to content link and the second one being
>>> a logo)
>>>
>>> This weird behaviour only happens on Jaws (latest) on Windows running
>>> Chrome. IE behaves as expected ... and FF reads page title then the
>>> link...hmm..
>>>
>>> Anyone with any suggestions what this might be?
>>> >>> >>> >
> > >