<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0pt;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0pt;
mso-margin-bottom-alt:auto;
margin-left:0pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle19
{mso-style-type:personal-compose;
font-family:"Times New Roman",serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>@Bryon, I’m sure you’ll get some differing opinions from this list.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We recommend that the document author look at the entire document and its intent before deciding. Alt-text isn’t as cut and dried as some like to think.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The body text that is before and/or after the screen capture or graphic can affect how much, if any, alt-text is needed on the graphic itself.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If the screen capture is of, let’s say, a software program and shows a menu with some options to select, you might not need much Alt-text if those steps are written in accessible body text before the screen capture. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>Example:</b><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Body Text:<o:p></o:p></p><p class=MsoNormal>Step 1, select the File menu, then Open.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Graphic:<o:p></o:p></p><p class=MsoNormal>Screen capture showing how to open a file with the File menu, and Open selected.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Alt-text:<o:p></o:p></p><p class=MsoNormal>Either minimal, such as “screen capture of how to open a file,” or artifact the graphic entirely because all the information that’s in the graphic is already in the accessible body text. The graphic doesn’t add any additional information for someone using a screen reader.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>Suggestion:<o:p></o:p></b></p><p class=MsoNormal>It sounds like your colleague is creating a document to explain how to use Taleo. I’d take the tactic of putting as much information as possible in live, accessible body text and use the screen captures to merely illustrate those actions for those who are sighted (who tend to look at pictures first, and read body text second).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>--Bevi Chagnon<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.0pt;font-family:"Calibri",sans-serif;color:#D9D9D9'>— — —<o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>Bevi Chagnon </span></b><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>| </span><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><a href="http://www.pubcom.com/"><span style='font-size:9.0pt;color:#0563C1'>www.<b>PubCom</b>.com</span></a></span><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></p><p class=MsoNormal style='margin-top:4.0pt'><i><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>Technologists, Consultants, Trainers, Designers, and Developers<o:p></o:p></span></i></p><p class=MsoNormal><i><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>for publishing & communication<o:p></o:p></span></i></p><p class=MsoNormal style='margin-top:4.0pt'><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>| Acrobat PDF | Print | EPUBS | Sec. 508 Accessibility |<o:p></o:p></span></p><p class=MsoNormal style='text-autospace:none'><span style='font-size:9.0pt;font-family:"Calibri",sans-serif;color:#D9D9D9'>— — —<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p><span style='font-family:"Calibri",sans-serif'>> On 12/14/2016 7:10:49 PM, Kluesner, Bryon (Bryon-Kluesner@utc.edu) wrote:</span> <br><span style='font-family:"Calibri",sans-serif'>> > Wise ones.</span> <br><span style='font-family:"Calibri",sans-serif'>> A Human Resources rep contacted me and asked what the steps were to add an alt tag on a photo in Power Point that would be screen reader accessible. She took a screen shot of something in Taleo (the U.T system's employment system to post jobs, and allow access to a search committee member to view applicant information). She wanted to know how to adequately describe the screenshot. Any suggestions?</span><o:p></o:p></p><p><span style='font-family:"Calibri",sans-serif'>> Thanks.</span> <br><span style='font-family:"Calibri",sans-serif'>> Bryon Kluesner, RhD</span> <br><span style='font-family:"Calibri",sans-serif'>> Adaptive Technology Coordinator</span> <br><span style='font-family:"Calibri",sans-serif'>> Disability Resource Center</span> <br><span style='font-family:"Calibri",sans-serif'>> Adjunct Professor</span> <br><span style='font-family:"Calibri",sans-serif'>> College of Health, Education </span><o:p></o:p></p></div></body></html>