WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: weird screen reader problem with table containing form fields

for

From: Laura Roberts
Date: Mar 20, 2024 10:11AM

I had manually created text form fields on this and decided to start over
and let Acrobat auto-detect form fields. Retagged it (thank god it is only
1 page) and it's working fine now. So something went awry with manual form
fields....

Laura

On Wed, Mar 20, 2024 at 11:32 AM <EMAIL REMOVED> <
<EMAIL REMOVED> > wrote:

> Hello there
> Have you tried manually navigating the table?
> And if so, exactly how are you going about it?
> JAWS has a layered table command where you could hit insert spacebar and
> the letter T and then you’d be able to up arrow down arrow left and right
> arrow through it
> Or press alt control up down left and right arrow to navigate through it.
> Does that work?
> Dean Vasile
>
>
> 617-799-1162
>
> > On Mar 20, 2024, at 11:22 AM, Laura Roberts < <EMAIL REMOVED> >
> wrote:
> >
> > The table is a simple table with one header row.
> > There's one merged data cell at the bottom row, but I was able to set
> > colspan just fine with no errors in PAC, no reading order issues.
> > It's laid out like this:
> > [image: image.png]
> > When JAWS reads it, it reads:
> > all the header cells
> > R1C1 (text), R1C2 (form field (and it does enter forms mode)), after
> > exiting forms mode on R1C2, it says table end and exits the table
> >
> > I don't see anything wrong in the tags or reading order that would
> account
> > for this.
> >
> > Here's the tag tree for that row:
> > [image: image.png]
> >
> > Taking the tag object out of the P tag makes no difference. Don't know
> why
> > it would, but I figured I'd give it a shot.
> >
> > Tired this morning, hoping it's something dumb and obvious I missed.
> >
> > --
> > Best regards,
> > Laura Roberts
> > 413-588-8422
> > > > > > > > > > <image.png>
> > <image.png>
> > > > >


--
Best regards,
Laura Roberts
413-588-8422