[Athen] FW: MS WORD 2016 Compability Inquiry

Chagnon | PubCom chagnon at pubcom.com
Sun Dec 4 21:09:02 PST 2016

We've found that you'll get the best, most accurate and accessible PDF if
you use the most current software tools.

Today, those are Word 2016 and Acrobat DC (which installs PDFMaker ver. 15.0
in MS Office).

We remediate dozens of documents a week for clients. Just checked a few
samples and all had the correct tags in the tag tree as well as in the Order
Panel (TURO tool).

I recommend that you update your Acrobat to DC and keep your Word 2016.

Don't go backwards. And never assume that outdated software knows about
today's standards.

Remember, it takes two pieces of software to create an accessible PDF: the
source application software (Word 2016) and the converting software (Acrobat
PDFMaker 15.0). You won't get solid results if one of them is out of date.
(Which is why we need to work with both Adobe and Microsoft to get the
accessibility problems resolved.)

Have attached a remake of your PDF. Took your Word document and opened it in
Word 2016, exported to accessible PDF with Acrobat DC/PDF Maker 15. Open my
version in Acrobat and you'll see the tags in the Order Panel/TURO are
accurate and match the tag tree.

FYI, you can see which versions of the source application and converting
software were used to create a PDF by doing the following:

1. Open the PDF in Acrobat Pro.

2. File / Properties.

3. First tab, Description.

4. Towards the middle you see the source and convertion software. PDF
Producer shows which software and version was used to convert the source to
the PDF.

--Bevi Chagnon

- - -

Bevi Chagnon | <http://www.pubcom.com/> www.PubCom.com

Technologists, Consultants, Trainers, Designers, and Developers

for publishing & communication

| Acrobat PDF | Print | EPUBS | Sec. 508 Accessibility |

- - -

From: athen-list [mailto:athen-list-bounces at mailman13.u.washington.edu] On
Behalf Of Hadi Rangin
Sent: Sunday, December 4, 2016 3:42 AM
To: 'Access Technology Higher Education Network'
<athen-list at u.washington.edu>
Cc: Marinette Fargo (mfargo at uoguelph.ca) <mfargo at uoguelph.ca>
Subject: [Athen] FW: MS WORD 2016 Compability Inquiry

Hi Marrinette,

As the MS Office list is a closed list and under NDA, unfortunately, I can't
engage the team in a conversation with non-members. However I am forwarding
your question to the Athen list and I am positive someone will have answer
for you.

If you are not a member of this public list, you might want to consider to
join it.

From: Marinette Fargo [mailto:mfargo at uoguelph.ca]
Sent: Thursday, December 1, 2016 6:22 AM
To: Hadi Rangin <hadir at uw.edu <mailto:hadir at uw.edu> >;
msoffice at uwashington.edu <mailto:msoffice at uwashington.edu>
Subject: MS WORD 2016 Compability Inquiry

Hello Members of the Office Accessibility Working Group,

I hope this message finds you all well. I was a former member of the MS
Office accessibility working group and I am reaching out to you to ask for
some guidance.

I am wondering if anyone in the group has recently encountered issues with
converting documents created in MS WORD 2016 to ACROBAT PDF?

I've attached a MS WORD Doc that has been created accessible and should
carry proper tags into Acrobat. However, this is not the case. The resulting
PDF looks like the tags are correct in the tag tree but not according to the
TURO tool. If you expand the tag tree, there are many empty containers and
tags that have carried over from the WORD doc.

I took this to out internal IT department to ask them to do some testing and
they have notified me that it is a compatibility issue between WORD 2016 and
Acrobat Pro XI. Their recommendation was for me to revert back to WORD 2013
as a solution but our campus has already upgraded everyone to WORD 2016 so
this is obviously not an ideal solution.

I present training workshops on document accessibility and this issue is
generating quite a bit of confusion and conflicting information so I am
looking for any additional info I can get to help us find a better solution
or at least verify the cause of the issue.

I appreciate any feedback or suggestions you are able to offer.

Take Care,


Library Accessibility Services,

McLaughlin Library - Room 124

University of Guelph
Phone: 519-824-4120 ext. 58925

Office Hours: 8:30am - 4:30pm (Monday - Friday)

CONFIDENTIALITY NOTICE: This electronic message and all contents contain
information that may be privileged, confidential or otherwise protected from
disclosure. The information is intended for the addressee(s) only. If you
are not an addressee, any disclosure, copy, distribution or use of the
contents of

this message is prohibited. If you have received this electronic message in
error, please notify the sender by reply e-mail and destroy the original
message and all copies.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20161205/2634b0c5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Original Checklist when using an existing PDF_Word2016-AcrobatDC.pdf
Type: application/pdf
Size: 194253 bytes
Desc: not available
URL: <http://mailman12.u.washington.edu/pipermail/athen-list/attachments/20161205/2634b0c5/attachment.pdf>

More information about the athen-list mailing list