WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: change in forms mode behaviour in JAWS 12

for

From: Ryan Hemphill
Date: Dec 12, 2011 1:54PM

Found it.

Here's what you need to do. For whatever reason, the JAWS bug is because
the forms content and the rest of your text are in the same container. I
managed to stop this from happening by separating them into different
containers altogether. I would put your heading in one container and the
form in another. Do not let them be on the same level of the DOM and the
problem should stop.

<div id="container1">
<h1>Heading</h1>
and Content
</div>
<div id="morecontent">More content</div>
<div id="form-container">
<form></form>
</div>

In response to Jared, you're right - the FS team should be resolving this.

I have also found that unless someone tries their hand at a hack, the real
source of the problem remains unknown in many cases, esp when it comes to
screen readers. While getting the bugs fixed is good, I can't wait for FS
to resolve it in their next release or their update of the current version.

Without at least seeing a hack that resolves the problem, it takes longer
to figure out where to look for the source of the issue. I suspect they
already have their hands full. I guess my point is, if they know the hack,
they at least have some idea of where to look.

Ryan



On Mon, Dec 12, 2011 at 3:21 PM, Jared Smith < <EMAIL REMOVED> > wrote:

> On Mon, Dec 12, 2011 at 1:16 PM, Ryan Hemphill wrote:
>
> > I'm going to hammer away at this a little more. No promises, mind you -
> > but with a little luck I may figure out how to resolve this.
>
> How about reporting this to Freedom Scientific so they can fix this
> bug? Nobody from FS is on this list (that I'm aware of). It seems a
> better solution to fix at the source rather than suggesting hacks and
> settings to work around the bug.
>
> Jared
>