WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Artifacting visual labels in PDF forms

for

From: Karlen Communications
Date: Mar 12, 2019 9:39AM

I agree. We have to be able to read the text of a form, not just have access
to the form controls. Failing to tag the text/labels or any other text on a
form would fail the form for accessibility.

I've also seen instances where the text of a form including headings and
informative/instructional text has been "tagged" as a read only form control
thus forcing us to read everything on a form and preventing us from really
distinguishing the text/instructions from the form fields we need to fill
out. Also a failure in terms of accessibility.

Cheers, Karen

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
Philip Kiff
Sent: Tuesday, March 12, 2019 10:58 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >; Dona Patrick
< <EMAIL REMOVED> >
Subject: Re: [WebAIM] Artifacting visual labels in PDF forms

It's not a common practice that I know about. I have also always included
it.

Artifacting the labels would be mean that users attempting to understand the
form structure without entering Forms mode would be unable to access the
visible field label, which seems like a tagging failure to me.

Phil.

Philip Kiff
D4K Communications

On 2019-03-12 10:46 AM, Dona Patrick wrote:
> I am checking some PDF forms created in LiveCycle and noticed that the
> author has chosen to artifact the visual labels before the form
> fields. The form fields are correctly marked up with the same tooltip as
the label.
>
> Is this common practice? I have always included the visual label in
> the tag structure and have never heard that it should be artifacted.
>
> Thanks,
>
> Dona
> > > archives at http://webaim.org/discussion/archives
> http://webaim.org/discussion/archives