<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;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:"Lucida Bright";
        panose-1:2 4 6 2 5 5 5 2 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0pt;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
h1
        {mso-style-priority:9;
        mso-style-link:"Heading 1 Char";
        margin-top:0pt;
        margin-right:0pt;
        margin-bottom:7.5pt;
        margin-left:0pt;
        font-size:14.0pt;
        font-family:"Cambria",serif;
        font-weight:bold;}
h2
        {mso-style-priority:9;
        mso-style-link:"Heading 2 Char";
        mso-margin-top-alt:auto;
        margin-right:0pt;
        margin-bottom:7.5pt;
        margin-left:0pt;
        font-size:13.0pt;
        font-family:"Cambria",serif;
        font-weight:bold;}
h3
        {mso-style-priority:9;
        mso-style-link:"Heading 3 Char";
        mso-margin-top-alt:auto;
        margin-right:0pt;
        margin-bottom:7.5pt;
        margin-left:0pt;
        font-size:12.0pt;
        font-family:"Cambria",serif;
        font-weight:bold;}
h4
        {mso-style-priority:9;
        mso-style-link:"Heading 4 Char";
        mso-margin-top-alt:auto;
        margin-right:0pt;
        margin-bottom:7.5pt;
        margin-left:0pt;
        font-size:12.0pt;
        font-family:"Cambria",serif;
        font-weight:bold;
        font-style:italic;}
h5
        {mso-style-priority:9;
        mso-style-link:"Heading 5 Char";
        margin-top:0pt;
        margin-right:0pt;
        margin-bottom:6.0pt;
        margin-left:21.6pt;
        page-break-after:avoid;
        font-size:12.0pt;
        font-family:"Cambria",serif;
        font-weight:normal;}
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.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0pt;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma",sans-serif;}
p.MsoQuote, li.MsoQuote, div.MsoQuote
        {mso-style-priority:29;
        mso-style-link:"Quote Char";
        margin-top:0pt;
        margin-right:36.0pt;
        margin-bottom:6.0pt;
        margin-left:36.0pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;
        color:black;}
span.Heading1Char
        {mso-style-name:"Heading 1 Char";
        mso-style-priority:9;
        mso-style-link:"Heading 1";
        font-family:"Cambria",serif;
        font-weight:bold;}
span.Heading2Char
        {mso-style-name:"Heading 2 Char";
        mso-style-priority:9;
        mso-style-link:"Heading 2";
        font-family:"Cambria",serif;
        font-weight:bold;}
span.Heading3Char
        {mso-style-name:"Heading 3 Char";
        mso-style-priority:9;
        mso-style-link:"Heading 3";
        font-family:"Cambria",serif;
        font-weight:bold;}
span.Heading4Char
        {mso-style-name:"Heading 4 Char";
        mso-style-priority:9;
        mso-style-link:"Heading 4";
        font-family:"Cambria",serif;
        font-weight:bold;
        font-style:italic;}
span.Heading5Char
        {mso-style-name:"Heading 5 Char";
        mso-style-priority:9;
        mso-style-link:"Heading 5";
        font-family:"Cambria",serif;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-style-priority:99;
        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.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma",sans-serif;}
span.QuoteChar
        {mso-style-name:"Quote Char";
        mso-style-priority:29;
        mso-style-link:Quote;
        color:black;}
span.EmailStyle28
        {mso-style-type:personal;
        font-family:"Cambria",serif;
        color:#1F3864;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
span.EmailStyle29
        {mso-style-type:personal;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
span.EmailStyle30
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.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=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>That’ll work!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Unfortunately, there are many instances in WCAG and PDF/UA that lack adequate tags for the type of material we create.<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><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Those who create the standards are mostly programmers (mostly, not all) who don’t usually think about how to handle title pages, titles with subtitles, kicker headings, deck heads, department headings, and other common parts of our documents. We end up cramming square WCAG/PDF-UA tags into round document holes.<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><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>I counsel my clients to do what makes sense to you for that particular document. As long as there is an H1 tag that designates the title, it’s somewhere close to the start of the reading order, and it is followed by a logical heading hierarchy for other titles, the user should be able to figure things out. <o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></a></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>And don’t forget to KISS: keep it simple, sweetie. Don’t obsess too much about this and don’t make it overly complicated for you or your audience. Sometimes a <P> tag does the job just fine.<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>--Bevi Chagnon <o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><p class=MsoNormal style='text-autospace:none'><span style='mso-bookmark:_MailEndCompose'><span style='font-size:9.0pt;font-family:"Calibri",sans-serif;color:#D9D9D9'>— — —<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><b><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>Bevi Chagnon </span></b></span><span style='mso-bookmark:_MailEndCompose'><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>| </span></span><span style='mso-bookmark:_MailEndCompose'></span><a href="http://www.pubcom.com/"><span style='mso-bookmark:_MailEndCompose'><span style='font-size:9.0pt;font-family:"Calibri",sans-serif;color:#0563C1'>www.<b>PubCom</b>.com</span></span><span style='mso-bookmark:_MailEndCompose'></span></a><span style='mso-bookmark:_MailEndCompose'><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'> <o:p></o:p></span></span></p><p class=MsoNormal style='margin-top:4.0pt'><span style='mso-bookmark:_MailEndCompose'><i><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>Technologists, Consultants, Trainers, Designers, and Developers<o:p></o:p></span></i></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><i><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>for publishing & communication<o:p></o:p></span></i></span></p><p class=MsoNormal style='margin-top:4.0pt'><span style='mso-bookmark:_MailEndCompose'><span style='font-size:9.0pt;font-family:"Calibri",sans-serif'>| Acrobat PDF | Print | EPUBS | Sec. 508 Accessibility |<o:p></o:p></span></span></p><p class=MsoNormal style='text-autospace:none'><span style='mso-bookmark:_MailEndCompose'><span style='font-size:9.0pt;font-family:"Calibri",sans-serif;color:#D9D9D9'>— — —<o:p></o:p></span></span></p><p class=MsoNormal><span style='mso-bookmark:_MailEndCompose'><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'><o:p> </o:p></span></span></p><span style='mso-bookmark:_MailEndCompose'></span><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0pt 0pt 0pt'><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>Bourne, Sarah (MASSIT)<br><b>Sent:</b> Monday, February 13, 2017 4:23 PM<br><b>To:</b> Access Technology Higher Education Network <athen-list@u.washington.edu><br><b>Subject:</b> Re: [Athen] proper heading structure in PDF<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'>Personally (and what I recommend to others) is to use H1 for the title of a document, and only use the TITLE style if there’s a separate title page. I then repeat the title as an H1 after the title page.  I haven’t seen a spec for how to use Word’s TITLE, so I just made something up that seemed to make sense.<o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Calibri",sans-serif'>sb<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Lucida Bright";color:#1F497D'>Sarah E. Bourne<br>Director of IT Accessibility, MassIT <br>Commonwealth of Massachusetts<br>1 Ashburton Pl. rm 811 Boston MA 02108<br>617-626-4502 <br><a href="mailto:sarah.bourne@mass.gov"><span style='color:#1F497D'>sarah.bourne@mass.gov</span></a> <br><a href="http://www.mass.gov/MassIT"><span style='color:#1F497D'>http://www.mass.gov/MassIT</span></a><o:p></o:p></span></p></div></div></body></html>