<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:x="urn:schemas-microsoft-com:office:excel" 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=utf-8">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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-GB" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">That would be the wrong conclusion to draw. Andrew Kirkpatrick is the Director of Accessibility at Adobe – he has been there 15 years and is also Co-Chair and Editor for WCAG. See
<a href="https://www.linkedin.com/in/akirkpatrick/">https://www.linkedin.com/in/akirkpatrick/</a>. He advocates very hard for accessibility in Adobe products.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">The real problem is that people expect to use these extremely complex applications without any training at all, and they expect the application to read their mind and magically do all the things
they want but haven’t learned to do. All it takes is a one-day training course that costs about $200 per person, but instead people flounder around for months or years and blame it all on Adobe. Frankly, I think it’s unprofessional for people to behave this
way.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Susan is actually overstating the case against InDesign. With a day’s training, it is not difficult to create a highly accessible PDF from InDesign that requires little or no remediation in Acrobat.
That said, if you are not also creating a print version of the document, InDesign may well not be the most appropriate application to be using.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Steve<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> athen-list <athen-list-bounces@mailman12.u.washington.edu>
<b>On Behalf Of </b>Dan Comden<br>
<b>Sent:</b> 10 May 2021 19:12<br>
<b>To:</b> Access Technology Higher Education Network <athen-list@u.washington.edu><br>
<b>Subject:</b> Re: [Athen] Making accessible info with InDesign?<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Adobe has had over 20 years to figure out how to make the PDF process and products accessible. After all this time, it is difficult to come to any conclusion other than the company does not really care about accessibility.<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, May 10, 2021 at 7:22 AM Susan Kelmer <<a href="mailto:Susan.Kelmer@colorado.edu">Susan.Kelmer@colorado.edu</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Okay, to be fair...<br>
<br>
InDesign is for laying out material. It is what Adobe Pagemaker used to be (for those of you who have been around a while). You make text boxes and add pictures and manipulate layout, and come up with a file that can be printed onto paper. Ala 1990. InDesign
and Pagemaker were a replacement for the manual labor of physically creating the paper print using exacto knives and glue and light boards (for those that have been around even longer). In operation, it is not intended to be a program that provides all that
accessibility for the outputted file. I do not fault Adobe for this. There is, as far as I know, NO program that will do this completely effectively.
<br>
<br>
If you want to have an accessible output, you will have to do what you've always done - work it out in Adobe Acrobat Pro on the completed file. InDesign is not a text-based program, like Word is. Word is easy to output into a reasonably accessible PDF. InDesign
was never intended for that purpose, and runs on an old Pagemaker backbone that would have to be written from the ground up.<br>
<br>
And the only way for that to be a priority for companies like Adobe is if there is money in it. No one is clamoring to Adobe to make InDesign produce accessible PDFs. Until they are, that won't change.<br>
<br>
Susan Kelmer <br>
Alternate Format Production Program Manager<br>
Disability Services<br>
Division of Student Affairs <br>
T 303 735 4836<br>
<a href="http://www.colorado.edu/disabilityservices" target="_blank">www.colorado.edu/disabilityservices</a>
<br>
<br>
Due to the nature of electronic communication, the security of this message cannot be guaranteed. If you've received this email in error please notify the sender immediately and delete this message.
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
athen-list mailing list<br>
<a href="mailto:athen-list@mailman12.u.washington.edu" target="_blank">athen-list@mailman12.u.washington.edu</a><br>
<a href="http://mailman12.u.washington.edu/mailman/listinfo/athen-list" target="_blank">http://mailman12.u.washington.edu/mailman/listinfo/athen-list</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<br>
-- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">-*- Dan Comden
<a href="mailto:danc@washington.edu" target="_blank">danc@uw.edu</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"> Access Technology Center
<a href="http://www.uw.edu/itconnect/accessibility/atl/" target="_blank">www.uw.edu/itconnect/accessibility/atl/</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"> University of Washington UW Information Technology</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>