<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Cambria",serif;
color:#1F3864;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:659650497;
mso-list-type:hybrid;
mso-list-template-ids:193745200 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoPlainText>We, too, have noticed the mis-tagging of TOCs and other elements for the past year, and it's getting worse with each new release or update from Microsoft and Adobe. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>(FYI, I can't address FoxIt or PowerPDF because they've never been able to make a correctly tagged PDF from MS Office, so what they produce now is no better or worse than what they did in the past.)<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>TOCs that are constructed correctly in MS Office export as a jumble of tags that are inaccessible for those using A T, especially screen readers. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Up until about a year ago, both Microsoft and Adobe had created a reliable method of making an accessible, tagged TOC in PDFs...and now suddenly they no longer do that.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Why has this happened?<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Since those of us who make and test accessible documents haven't changed our methods, the problem must come from something that Microsoft and Adobe have done to the software tools:<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Could be that ...<o:p></o:p></p><ol style='margin-top:0in' start=1 type=1><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>MS Word has changed how it encodes TOCs in Word documents.<o:p></o:p></li><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>Microsoft's Save As PDF utility has changed how it tags the TOC.<o:p></o:p></li><li class=MsoPlainText style='mso-list:l0 level1 lfo1'>Adobe's PDF Maker export utility (aka the Acrobat Ribbon) has changed how it tags the TOC.<o:p></o:p></li></ol><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>I actually don't know who changed what at this time, but I do know that what we're now getting from MS Office is a piece of junk that should not be allowed by the industry.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>People -- real human beings who use A T -- can't read the TOC. It is an inaccessible mess!<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>If you think that this will be a problem for yourself or those who will use your documents, then <b>I encourage you to download Karen's sample documents</b> and judge for yourself.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>And then we need to do something to correct this problem.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>--Bevi Chagnon<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><b><span style='color:#D0CECE'>— — —<o:p></o:p></span></b></p><p class=MsoNormal>Bevi Chagnon, founder/CEO <b><span style='color:#AEAAAA'>|</span></b> <a href="mailto:Bevi@PubCom.com"><span style='color:#0563C1'>Bevi@PubCom.com</span></a> <o:p></o:p></p><p class=MsoNormal><b><span style='color:#D0CECE'>— — —<o:p></o:p></span></b></p><p class=MsoNormal><b>PubCom: <span style='color:#C00000'>Technologists for Accessible Design + Publishing</span><o:p></o:p></b></p><p class=MsoNormal>consulting <span style='color:#D0CECE'>•</span> training <span style='color:#D0CECE'>•</span> development <span style='color:#D0CECE'>•</span> design <span style='color:#D0CECE'>•</span> sec. 508 services<o:p></o:p></p><p class=MsoNormal><b>Upcoming classes</b> at <a href="http://www.pubcom.com/classes"><span style='color:#0563C1'>www.PubCom.com/<b>classes</b></span></a> <o:p></o:p></p><p class=MsoNormal><b><span style='color:#D0CECE'>— — —<o:p></o:p></span></b></p><p class=MsoNormal><a href="https://mailchi.mp/dfadd677496c/heqcq8lsqb-2960773"><b><span style='color:#0563C1'>Latest</span></b><span style='color:#0563C1'> blog-newsletter</span></a> – Accessibility Tips at <a href="http://www.pubcom.com/blog"><span style='color:#0563C1'>www.PubCom.com/blog</span></a> <o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> athen-list <athen-list-bounces@mailman12.u.washington.edu> <b>On Behalf Of </b>Karlen Communications<br><b>Sent:</b> Thursday, June 13, 2019 8:56 AM<br><b>To:</b> 'WebAIM Discussion List' <webaim-forum@list.webaim.org><br><b>Cc:</b> 'Access Technology Higher Education Network' <athen-list@u.washington.edu><br><b>Subject:</b> [Athen] Comparing Results of Tagged PDF with Acrobat and Alternatives<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864'>Hi Everyone:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864'>I’ve started a series of comparison articles on the accessibility/tagging of PDF documents from Acrobat Pro DC, Foxit Phantom for Business and Nuance PowerPDF Advanced. Note that both Foxit and Nuance have versions of their software that don’t have tagging capabilities. The ones listed do.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864'><a href="https://www.karlencommunications.com/DocumentRemediation.htm">https://www.karlencommunications.com/DocumentRemediation.htm</a><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864'>I plan to take different elements, for example am now looking at how footnotes/endnotes are tagged by each of them, and putting the articles on this web page. I didn’t want to create a new web page and this one seemed the logical choice to house the content.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864'>Cheers, Karen<o:p></o:p></span></p></div></body></html>