WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Are Forms in MS Word Accessible?

for

From: Karen McCall
Date: Dec 1, 2021 12:44PM

I use a similar process. I know Adobe says to add the form controls before you tag the document but that process has never worked well and about 6 years ago I started working with a tagged form template and then adding the form controls.

One caveat to adding the lines for people to print on is related to accessibility. As you type in those types of form controls you can never get the text to line up on the printing/writing lines. This can be frustrating for those who want perfection and think that they are doing something wrong because the text isn't on the lines and, a further important barrier is that someone visually proofreading the answers can't read the text if a printing guiding line runs through it.

Tip: I use Word Count in Word to figure out how much space I need for a long answer. This is assuming I'm creating the form template. I create the form template in Word, save it as a tagged PDF, open it in Acrobat and remediate any accessibility check errors, create the form controls and then add them to the Tags Tree.

BTW, in the Appearance tab in the form control properties dialog you can add an underline to a form control for short answer questions like your name or address or signature. These don't require being artifacted but give a guiding line for printing.

Cheers, Karen

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Elizabeth Thomas
Sent: Wednesday, December 1, 2021 2:28 PM
To: Steve Green < <EMAIL REMOVED> >
Cc: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Are Forms in MS Word Accessible?

I agree about the problems with forms in Word.
I have done a fair amount of work on fillable PDF forms and have a process that works fairly well if you must author in Word. I author the form in Word but don't actually add any form fields. I also don't add any visual indicators of the form fields in Word (e.g., underlines or boxes) because I then would have to artifact them in the PDF. However, the tradeoff is that with no visual indicators of form fields, Acrobat can't really identify the fields (if you have form field auto detection on). Instead of underlines and boxes, I leave enough white space where the form fields will go. Some people prefer to add the visual indicators in Word and artifact them in the PDF. I have found it takes me longer to do it that way, but it might work better for you depending on the type of form you created.

I export the Word doc to PDF as a tagged document. Before I add the form fields, I use the reading order tool to tag chunks of text for any line with multiple form fields per line. for example, if name and email are on the same line, in the PDF I tag them as two separate paragraphs (you could also tag them as spans contained in the same paragraph tag, which might be more semantically appropriate ). I retag this text, because I want the reading order to be “name,” “form field for name,” “email,” “form field for email.”

Then I add all of the form fields in the PDF (with appropriate tooltips), and adjust the appearance of the fields, as appropriate, to be boxes, underlines, etc. Finally, I tag all of the form fields and put them in the correct place in the tag tree.

That's probably more detail than you want or need, but those are the basic steps if the source file is Word. It's a long, tedious process and future updates often require doing most of the work in the PDF. Consequently, when it makes sense to do so, I have the content authors create a web form instead. However, my agency has a lot of forms we provide for other entities to use, and the easiest way to do that is to create a fillable PDF form.

And this ends the longest email about PDF forms. Hope at least some of that was helpful. ;)

-Elizabeth Thomas
State of New Jersey, ADS, CPACC

Sent from my iPhone

> On Dec 1, 2021, at 6:41 AM, Steve Green < <EMAIL REMOVED> > wrote:
>
> Hi Jim,
>
> I have done a load of research into this and the answer is categoric - Word forms are hopelessly inaccessible to a variety of user groups even if you do absolutely everything possible. As you have found, converting to PDF just makes things worse and you have to add all the form controls again in Acrobat.
>
> The best solution is to author the form in InDesign and export as PDF. If you do everything right, my understanding is that you shouldn't need to fix anything in Acrobat.
>
> BTW, Ted Page of Accessible Digital Documents knows more about the topic than anyone I know. It's all he's done for the last 15 years, so you can trust what he says. We used to subcontract our document remediation to him, but he's always booked solid with training courses so we now do it all in-house again.
>
> I'd be happy to collaborate if there are any parts of this you don't fancy doing yourself.
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Jim Byrne Accessible Web Design
> Sent: 01 December 2021 11:17
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: [WebAIM] Are Forms in MS Word Accessible?
>
> Hi,
>
> I've been trying to figure out if it is possible to create accessible forms in Word - but there seems to be a lot of competing views on the issue.
>
> I've watched videos that imply that as long as you use good accessibility practice they will be accessible. And I've seen articles that say they might be technically accessible but in practice they are not - because of the way the security protection works:
>
> "You can't make Microsoft Word forms accessible (enough) …"
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faccessible-digital-documents.com%2Fblog%2Fyou-cant-make-microsoft-word-forms-accessible-enough%2F&amp;data%7C01%7C%7C3913c760b130413ee18e08d9b500b25c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637739836866659866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=uQDlIchtL9HAwCmMjT4leZ3HgmrFCs9kXiJp71il50g%3D&amp;reserved=0
>
> Are these security issues still relevant to the current version of Word?
>
> Assuming they can't be made accessible, what's the recommended practice for converting them to PDF? Again I've seen competing advice. The standard advice for creating accessible PDFs is to export them as tagged documents - but I've also seen advice (on the Adobe website) saying that, unless the forms are simple, the tagging should be done in the PDF editor itself and that documents should be exported untagged?
>
> As a test I created a form in a Word document and exported it to PDF, but when the I opened it the form fields had gone, apart from the checkboxes. Creating forms in word doesn't seem to be a work well. ????
>
> So is the best advice to create everything in Word apart from the forms - and create the form fields in the PDF editor? (I am aware that accessible forms can also be created on a web page.)
>
> Sorry for the long email. I've been getting frustrated trying to get a clear picture on this.
>
> Jim
>
>
>
>
>
>
>
>
>
>
> About Jim Byrne
> With over two decades of experience Jim Byrne is one of the UK's most experienced practitioners in the area of accessible web design. Jim provided feedback during the development of WCAG 2 as part of the Guild of Accessible Website Designers. He is the author of a number of technical books, training courses and accessibility guides. Jim was a winner of the equal access category of the Global Bangemann Challenge.
>
> Jim Byrne: Specialist in Accessible Website Design.
>
> Web: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.jimbyrne.co.uk%2F&amp;data%7C01%7C%7C3913c760b130413ee18e08d9b500b25c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637739836866659866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=7HDRHjdVtYjgBWHVPR3LxkseyYojqyIKm%2BwdROjp3ns%3D&amp;reserved=0
>
> Twitter: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2F%23!%2Fjimbyrnewebdev&amp;data%7C01%7C%7C3913c760b130413ee18e08d9b500b25c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637739836866659866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=SERsJaqeN%2Btn8CxPHC1eG2puTvRzV4sJAsgQDhyq4rI%3D&amp;reserved=0
>
> Facebook: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.facebook.com%2Fthirdsectorwebsitedevelopment&amp;data%7C01%7C%7C3913c760b130413ee18e08d9b500b25c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637739836866659866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=MwpZvBMhqYWZ2tra%2FtLQWNsJg%2BdVJvQdOrn84p6vVOw%3D&amp;reserved=0
>
>
>
> > >