<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.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;}
--></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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">A properly tagged and remediated PDF should have no spacing issues in play since the tag structure would have been remediated to eliminate these kinds of issues.
JAWS and NVDA can read these just fine, and even the latest version of Adobe Reader on OSX and Voice Over now respects tag structure.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Users really shouldn’t want to use the JAWS OCR feature, it should be something of a last resort. My argument both as an accessibility professional and a blind
user again is that documents should be tagged and structured accessibly so I should have no need to use an OCR feature.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">A valid argument could certainly be made for the signature being decorative although I would in turn argue as a screen reader user that knowing that an image
of a physical signature is useful information to have<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;line-height:13.5pt;background:white">
<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333"><img width="336" height="68" id="Picture_x0020_1" src="cid:image001.png@01D1DD13.3B479880" alt="The Ohio State University"><br>
</span><b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#BB0000;background:white">Peter Bossley</span></b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333"><br>
Accessibility Analyst<br>
</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#BB0000;background:white">Office of the CIO</span><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#333333">
<br>
017 Telecommunications Network Center, 320 W. 8th Ave, Columbus, OH 43201<br>
614-292-8571 Office<br>
<a href="mailto:bossley.5@osu.edu"><span style="color:#0563C1;background:white">bossley.5@osu.edu</span></a>
<a href="http://ocio.osu.edu/"><span style="color:#0563C1;background:white">ocio.osu.edu</span></a>
<o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">
<hr size="2" width="100%" align="center">
</span></div>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> athen-list [mailto:athen-list-bounces@mailman13.u.washington.edu]
<b>On Behalf Of </b>Joshua Hori<br>
<b>Sent:</b> Tuesday, July 12, 2016 8:47 PM<br>
<b>To:</b> Access Technology Higher Education Network <athen-list@u.washington.edu><br>
<b>Subject:</b> Re: [Athen] Sending signed PDFs<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Not sure the alt text is needed for the signature as their name will be posted on the bottom anyways. A blank alt would work as it’s a decorative item to those
with screenreaders. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Word and PDF is probably best as most visually disabled users toss PDF attachments in the trash. I can’t get my users to use the OCR built into JAWS due to the
issues present with image PDF’s, searchable PDF’s, and tagged PDFs. JAWS reads image PDF’s but doesn’t do anything for the searchable and tagged, even if they’re messed up with spacing between characters. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The best possible practice would be to make a memo site and post them all there with an automated email notifying users of memo updates and quick search capabilities.
Memos get lost too easily in emails. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Joshua<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> athen-list [<a href="mailto:athen-list-bounces@mailman13.u.washington.edu">mailto:athen-list-bounces@mailman13.u.washington.edu</a>]
<b>On Behalf Of </b>Bossley, Pete<br>
<b>Sent:</b> Tuesday, July 12, 2016 12:31 PM<br>
<b>To:</b> Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu">athen-list@u.washington.edu</a>><br>
<b>Subject:</b> Re: [Athen] Sending signed PDFs<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Ideally the PDF with the signature would be accessible, tagged, with good structure; and the signature would be an image with appropriate alt text. E.g. Peter
Bossley’s signature.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> athen-list [<a href="mailto:athen-list-bounces@mailman13.u.washington.edu">mailto:athen-list-bounces@mailman13.u.washington.edu</a>]
<b>On Behalf Of </b>Jiatyan Chen<br>
<b>Sent:</b> Tuesday, July 12, 2016 12:13 PM<br>
<b>To:</b> Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu">athen-list@u.washington.edu</a>><br>
<b>Subject:</b> Re: [Athen] Sending signed PDFs<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Unless you have extra staff or mechanical way to convert files, the simplest way for the central office is to post the Word (unsigned, with correct structure) and the PDF (signed and scanned) together. Least amount of work those folks
have to learn/do = easiest way to convince them to do it.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">--<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Jiatyan Chen<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 2016 Jul 12, at 08:34, Joseph Sherman <<a href="mailto:Joseph.Sherman@cuny.edu">Joseph.Sherman@cuny.edu</a>> wrote:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Our central office has a habit of sending out signed memos generated in Word, signed, scanned as PDF, and emailed or posted. What is best practice for accessibility? Should they
run make accessible on the scan to OCR and auto tag the PDF? Or have two PDF versions, one not signed but generated from Word with tags? Or is there a better option?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Joseph<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>