<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=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;}
@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: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;}
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:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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">Optacon was a device invented in the late seventies by a Stanford professor with a daughter who was blind. He formed the company, TeleSensory, to market it –
they were perhaps the first access technology company. They also created the first Braille notetaker, the VersaBraille.<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 Optacon has a camera on a cable you slide across a printed page. The black-and-white image from the camera is converted to a tactile image on an array of
vibrating pins. The early Optacons had 144 pins; the later ones had 100. A typical 12-point character will fill the array, showing a tactile image of that character. You can use the Optacon to examine any printed material, even handwriting, but your brain
has to do all the interpreting, and you are seeing less than a half-inch of the material at any time. “Tracking” or moving the camera straight across a page and staying on a line of print is the hardest task to master.<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">Because it is so difficult to use, nobody ever created a competing device.<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">Training to learn the Optacon was long and arduous. Blind people who faithfully practiced daily for a year could read print at about 80 words per minute.<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">I taught myself so my speed is more around nine words per minute, because I could not afford the training. I can read page numbers and check page orientation
with it, and I can also see if there are pictures on a page. I use it mostly to skim through a book to examine the layout, and sometimes to check things I’ve printed myself. I don’t really do any reading with it. There is also a device to read a CRT screen
with the Optacon but I gave mine away.<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">Another thing that made the Optacon difficult was proportional spacing and all the kerning and ligatures in fonts. This is less of an issue for me because in
training myself, I printed out examples of every font I could find. The Optacon training manual is all in easy Courier. It tends to give one a false sense of success!<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>
<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 <athen-list-bounces@mailman12.u.washington.edu>
<b>On Behalf Of </b>Robert Spangler<br>
<b>Sent:</b> Friday, September 07, 2018 7:48 AM<br>
<b>To:</b> Access Technology Higher Education Network <athen-list@u.washington.edu><br>
<b>Subject:</b> Re: [Athen] Editing PDFs with a Screen Reader<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">What is an Optacon? I use various scanning apps on my phone for the purpose of reading print documents.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Thu, Sep 6, 2018 at 1:39 PM Deborah Armstrong <<a href="mailto:armstrongdeborah@fhda.edu">armstrongdeborah@fhda.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">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">This is a really great explanation of why PDF remediation with a screen reader is not an accessible process. Clearly written!</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">I would add that OmniPage is reasonably accessible, and it for me does better OCR than Adobe Pro produces with automatic settings.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">When I get a publisher PDF, even if it seems to read out loud OK, I run it through OmniPage and make a few changes in its mostly accessible editor. If
the student wants the book right away I tell them they can have the unaltered PDF and to email me what remediations they truly need. This saves me a lot of work, because only some students need some remediations.
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Another solution if your student wants to see and hear the book is to give them the unaltered PDF and a word document with the entire text that you’ve
cleaned up some with an accessible program like K1000. Changing the reading order in K1000 is of course perfectly accessible.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Another feature I love in K1000 is its ranked spelling which lets me clean up the worst errors quickly. Instead of presenting spelling errors in chronological
order, it presents them in frequency of occurrence order. So I can zap 97% of the errors in five minutes.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Both K1000 and OmniPage have accessible ways of moving pages around or knowing what page you are on.
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">It’s too bad nobody has made a modern Optacon. When I dropped an unbound book on the floor and got some pages out of order, and I was the only one in
the office, I was glad I could still sort of use mine!</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">--Debee</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><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" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> athen-list <<a href="mailto:athen-list-bounces@mailman12.u.washington.edu" target="_blank">athen-list-bounces@mailman12.u.washington.edu</a>>
<b>On Behalf Of </b>Karlen Communications<br>
<b>Sent:</b> Friday, August 31, 2018 6:35 AM<br>
<b>To:</b> 'Access Technology Higher Education Network' <<a href="mailto:athen-list@u.washington.edu" target="_blank">athen-list@u.washington.edu</a>><br>
<b>Subject:</b> Re: [Athen] Editing PDFs with a Screen Reader<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864">Screen readers and Text-to-Speech tools are always in ”virtual view” of HTML and PDF documents.
This means that the adaptive technology is reading from the buffer not the text layer of the document, In PDF, this is the Tags Tree. It is the reason we can’t add notes or other comments to PDF documents – where we think we are in the document is not where
we are, it is where we are in the buffer. It is also why we can’t follow notes or comments in PDF documents. For us, there is no connection between the note or comment and the “text on the page.”</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864">While we can go down the Tags Tree, open the tags and review some of the content/that is showing,
we can’t tell if content has been missed or tagged correctly based on what is on the visual representation of the page we are working from.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864">You do need eyesight to fully remediate PDF documents.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864">Cheers, Karen</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-CA" style="font-size:14.0pt;font-family:"Cambria",serif;color:#1F3864"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<b>From:</b> athen-list <<a href="mailto:athen-list-bounces@mailman12.u.washington.edu" target="_blank">athen-list-bounces@mailman12.u.washington.edu</a>>
<b>On Behalf Of </b>Robert Spangler<br>
<b>Sent:</b> Friday, August 31, 2018 9:05 AM<br>
<b>To:</b> Access Technology Higher Education Network <<a href="mailto:athen-list@u.washington.edu" target="_blank">athen-list@u.washington.edu</a>><br>
<b>Subject:</b> [Athen] Editing PDFs with a Screen Reader<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Hello:<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
I am in charge of our alternative formats program. As a screen reader user, I do not find Adobe Acrobat Pro or Abbyy Finereader to be the most accessible. I find them laggy, they sometimes freeze and I have not found a way to edit PDFs directly.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Is this possible for blind folks to do with a screen reader? Ultimately, I need to be able to remediate PDFs. I would like to do tagging, edit the text, do chapter breaks, etc. I know I can do chapter breaks especially if there are bookmarks in the PDF,
but I find this difficult to do, to determine the page numbers easily, if there are not bookmarks.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Normally, we have student workers who handle the editing and I just do the administrative stuff, such as sending out the texts. We have summer classes, though, when the student workers are not here, so this task ultimately falls to me!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
I would love to hear from people, especially blind people, who are working with remediating PDFs. Is this possible? Are there accessibility problems with these programs? Admittedly, I've just accepted that most PDFs are not always edited adequately and I
deal with it, but I don't want to tell my students this. Haha. I usually run it through OCR and that's sufficient for me except for when the order of the reading is incorrect.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Looking forward to responses.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Robert<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Robert Spangler<br>
Disability Services Technical Support Specialist<br>
<a href="mailto:rspangler1@udayton.edu" target="_blank">rspangler1@udayton.edu</a><br>
Office of Learning Resources (OLR) - RL 023<br>
Ryan C. Harris Learning & Teaching Center (LTC)<br>
University of Dayton | 300 College Park | Dayton, Ohio 45469-1302 <br>
Phone: 937-229-2066<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Fax: 937-229-3270<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Ohio Relay: 711 (available for individuals who are deaf or hard of hearing)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt;margin-left:.5in">
Web Site: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__go.udayton.edu_learning&d=DwMFaQ&c=WORo6LNFtQOb4SPVta8Jsg&r=K_2Yg4I05GGnHlSOevlp3QeE5-JEqtmoUnmP0YVj9ZM&m=NS6Bk8hB7g4EqHf06xQXAt98sM4ynBrgA6aH6fAFYcY&s=SE2K9eRPMfVmyX0gQLSHzF-X3TtwOEZzPIu29qov2Ro&e=" target="_blank">
http://go.udayton.edu/learning</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<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="https://urldefense.proofpoint.com/v2/url?u=http-3A__mailman12.u.washington.edu_mailman_listinfo_athen-2Dlist&d=DwMFaQ&c=WORo6LNFtQOb4SPVta8Jsg&r=K_2Yg4I05GGnHlSOevlp3QeE5-JEqtmoUnmP0YVj9ZM&m=zSd-G2OVJD5hDKTrm7NWbQdUtoLoAEBZUmUJTFYyo4Q&s=u03_Bw-kD2UoYWFEZyNtRjLTbxNTozqo3inVfYoQV3w&e=" 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">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Robert Spangler<br>
Disability Services Technical Support Specialist<br>
<a href="mailto:rspangler1@udayton.edu" target="_blank">rspangler1@udayton.edu</a><br>
Office of Learning Resources (OLR) - RL 023<br>
Ryan C. Harris Learning & Teaching Center (LTC)<br>
University of Dayton | 300 College Park | Dayton, Ohio 45469-1302 <br>
Phone: 937-229-2066<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Fax: 937-229-3270<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Ohio Relay: 711 (available for individuals who are deaf or hard of hearing)<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Web Site: <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__go.udayton.edu_learning&d=DwMFaQ&c=WORo6LNFtQOb4SPVta8Jsg&r=K_2Yg4I05GGnHlSOevlp3QeE5-JEqtmoUnmP0YVj9ZM&m=zSd-G2OVJD5hDKTrm7NWbQdUtoLoAEBZUmUJTFYyo4Q&s=EEcWRb99V7MLaDegiEwC4PRXv6BGGsjlXLh-q-wSniU&e=" target="_blank">
http://go.udayton.edu/learning</a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>