WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: a possible jaws bug and if it is can someone file it

for

From: Bryan Garaventa
Date: Jan 8, 2014 5:09PM

I understand, this has been a problem in JAWS going back many years, though
it's been getting better over the years as well.

It has to do with JAWS's ability to recognize dynamic content changes in the
DOM. In this case, it's a specific state change in the accessibility tree
that JAWS is failing to recognize.

----- Original Message -----
From: "Lucy Greco" < <EMAIL REMOVED> >
To: "WebAIM Discussion List" < <EMAIL REMOVED> >
Sent: Wednesday, January 08, 2014 4:01 PM
Subject: Re: [WebAIM] a possible jaws bug and if it is can someone file it


> Answers inline
>
> I see what you mean. I agree that the state should be conveyed when the
> focused element changes programmatically.
>
> The problem is that this should only happen when the state changes on the
> element that currently has focus. Or in JAWS' case, the element that
> sounds
> like it has focus where the Virtual Cursor is pointing.
> [] lg yes but in this demo the focus for the keyboard stays on the expand
> not it does not move the focus as far as I can tell if I use speak current
> line it reads the expand link
> I
> This is easier to accomplish in NVDA, because as you arrow down the page
> in
> Browse Mode, everything that you hear is given focus.
>
> In JAWS though, focus may be on another element on the page, and as you
> arrow down the page, keyboard focus is not moved to the element you are
> hearing.
>
> It should be possible for FS to do it, but they will need to make sure
> that
> when state changes on other elements on the page as part of a
> configuration
> script for instance, that all of their states are not automatically
> announced at the same time as well, which would sort of defeat the
> purpose.
>
>
>
> ----- Original Message -----
> From: "Lucy Greco" < <EMAIL REMOVED> >
> To: "WebAIM Discussion List" < <EMAIL REMOVED> >
> Sent: Wednesday, January 08, 2014 3:27 PM
> Subject: Re: [WebAIM] a possible jaws bug and if it is can someone file it
>
>
>> Ok I just tested in i.e. 10 and found a different but similar problem.
>> When I tab to the link and click it will speak the state change but if I
>> click it again it does not tell me that the state changed back. We want
>> the link to change whenever the user clicks it and it does do so but
> jaws
>> needs to say witch state it is currently in.
>> And if I keep clicking it never tells me that the state changes. The
>> difference in i.e. to ff is that I can tab away and back again and it
>> will tell me once again the state change but only the first state change
>> to get it to tell me I can't click the link without tabbing away from
> the
>> link.
>> Also I think it's not controllable but in i.e. the user does not have
> any
>> way to go to the focused text that has been opened like in Firefox I
> think
>> that's a known jaws thing.
>>
>> Lucia Greco
>> Web Access Analyst
>> IST-Campus Technology Services
>> University of California, Berkeley
>> (510) 289-6008 skype: lucia1-greco
>> http://webaccess.berkeley.edu
>>
>>
>>