[{"id":798,"date":"2026-03-10T10:21:01","date_gmt":"2026-03-10T15:21:01","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=798"},"modified":"2026-03-10T16:24:49","modified_gmt":"2026-03-10T21:24:49","slug":"accessible-music-notation","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/accessible-music-notation\/","title":{"rendered":"Accessible Music Notation"},"content":{"rendered":"<p>Creating accessible music notation is vital for musicians with disabilities. Listed below are accessibility practices that help musicians with disabilities read, access, navigate, and comprehend sheet music.\u00a0These practices support compliance with WCAG 2.1 Level A and AA by providing text alternatives, supporting assistive technology compatibility, and ensuring proper use of color.<\/p>\n<h2>Digital Scores<\/h2>\n<p>Whenever possible, avoid sharing scanned images <em>as the sole format<\/em> for music scores. Instead, utilize digital scores (e.g., MusicXML, MIDI). Digital sheet music offers several features beneficial not only to musicians with disabilities, but to all users. Digital scores:<\/p>\n<ul>\n<li>can be searched, more easily annotated, and operated with assistive technology,<\/li>\n<li>provide better resolution, allowing high levels of magnification without loss of quality,<\/li>\n<li>allow the ability to increase color and brightness contrast to improve readability,<\/li>\n<li>in some applications, support audio playback,<\/li>\n<li>and are easier to remediate into alternative formats (such as Braille or large print).<\/li>\n<\/ul>\n<h2>Non-Digital Notation<\/h2>\n<p>If you need to include an image of sheet music (such as an excerpt or figure) on a website, slide deck, or other electronic document, include alt text to describe what is depicted. This allows individuals with visual disabilities to understand the purpose and content of the image (using a screen reader or other assistive technology).<\/p>\n<p>Review University of North Texas\u2019 <a href=\"https:\/\/digitalstrategy.unt.edu\/clear\/teaching-resources\/accessibility\/music-accessibility\/describing-musical-examples-text-and-alt-text.html\">Describing Musical Examples with Text and Alt Text<\/a> to understand the unique aspects of writing alt text for music. Below are a few examples:<\/p>\n<ul>\n<li>Write all musical symbols phonetically, rather than using special characters on the keyboard (e.g., \u201cC-Sharp\u201d instead of C#). This helps musicians who use <a href=\"https:\/\/afb.org\/blindness-and-low-vision\/using-technology\/assistive-technology-products\/screen-readers\">screen readers<\/a>.<\/li>\n<li>Screen readers may not distinguish upper- and lower-case, so write out &#8220;major&#8221; and &#8220;minor&#8221; when referencing chords, keys, and intervals (e.g., &#8220;C minor&#8221; instead of &#8220;Cm&#8221;).<\/li>\n<li>Write-out entire chord and interval names as if speaking them aloud (e.g., &#8220;C half-diminished seventh add two&#8221;, not &#8220;C\u00f87add2&#8221;).<\/li>\n<\/ul>\n<h2>Talking Scores<\/h2>\n<p>A \u201ctalking score&#8221; is an audio-based representation of sheet music used especially by musicians with visual disabilities. Talking scores can also be helpful for individuals with neurological disabilities who have difficulty processing print content.<\/p>\n<p>In talking scores, music notation is read aloud in sections with details such as instrument names, temp markings, key changes, repeated sections, and common rhythms. In between these sections, the notation is often played aloud for the listener.<\/p>\n<p>For examples of manually-created talking scores, check out\u00a0<a href=\"https:\/\/www.musicvi.com\/store\/piano-by-ear.html\">Bill Brown\u2019s Piano by Ear lessons<\/a>. For examples of talking scores generated using a conversion program, check out the <a href=\"https:\/\/www.talkingscores.org\/\">Talking Scores open source project<\/a>. This project converts MusicXML files into a combination of text description and audio playback files in an HTML format that can be navigated by assistive technologies.<\/p>\n<h2>More Best Practices<\/h2>\n<ul>\n<li><strong>Fonts.<\/strong> Always use sans-serif fonts (e.g., Arial). Avoid serif fonts (e.g., Times New Roman) and cursive text. The more readable the text is, the better.<\/li>\n<li><strong>Color and Contrast.\u00a0<\/strong>Ensure all text has sufficient contrast against the background (use\u00a0<a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\">WebAIM&#8217;s Color Contrast Checker<\/a>) and that color is not the only way to convey information.<\/li>\n<li><strong>Plain Language.<\/strong>\u00a0Write in a way that is\u00a0<span data-contrast=\"auto\">clear and easy to understand.<\/span><span data-ccp-props=\"{}\">\u00a0Organize content for easy scanning and understanding.\u00a0<\/span>Your writing should match\u00a0<a href=\"https:\/\/www.plainlanguage.gov\/guidelines\/\"><span data-contrast=\"none\">Federal Plain Language Guidelines<\/span><\/a><span data-contrast=\"auto\">.<\/span><\/li>\n<\/ul>\n<h2><span style=\"font-family: inherit;font-size: 1.777rem\">Accommodation Requests<\/span><\/h2>\n<p>Musicians with disabilities may require individualized accommodations. A range of advanced remediation tools and strategies are available to support diverse access needs. If requested, work directly with musicians on a one\u2011on\u2011one basis to identify and implement the most effective accommodations to meet their needs.<\/p>\n<h2><span style=\"font-family: inherit;font-size: 1.777rem\">Frequently Asked Questions<\/span><\/h2>\n<p><strong>Q:<\/strong> How do I make YouTube videos of musical recordings accessible?<br \/>\n<strong>A:<\/strong> Provide accurate, synchronized closed captions (CC) for all spoken dialogue, as well as musical cues (e.g., crescendos, &#8220;orchestra tuning&#8221;) and other contextual information (e.g., &#8220;applause&#8221;). Always manually review and edit auto-generated captions. Add a summary of the performance at the start and\/or in the video description (e.g., &#8220;this recording features Brahms Intermezzo Op. 117 No. 1, a slow, reflective piano work with a gentle lullaby theme&#8221;).<\/p>\n<p><strong>Q:<\/strong> How do I make an MP4 video that I upload accessible?<br \/>\n<strong>A:<\/strong> As above. Include closed captions for the hearing impaired, provide a full text transcript for screen readers, and ensure the player supports keyboard navigation. Use HTML5 video tags, offer audio descriptions for visual content, and avoid flashing, or strobing visuals. Include a text transcript that explains the audio, video narration, and key visual information.<\/p>\n<p><strong>Q:<\/strong> How can I upload a PDF of a musical score and make it accessible?<br \/>\n<strong>A:<\/strong> Produce scores in a digital format such as MusicXML. See our <a href=\"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/pdfs\/\">PDFs Accessibility Guide<\/a>\u00a0for more information.<\/p>\n<p><strong>Q:<\/strong> How can I upload an accessible PDF with a music font since I can\u2019t use \u201cPrint to PDF,\u201d but must use \u201cSave as PDF\u201d? None of the fonts transfer.<br \/>\n<strong>A:<\/strong> Creating an accessible PDF that includes specialized musical notation fonts requires embedding the fonts, tagging the structure, and ensuring the musical content is described.<\/p>\n<p><strong>Q:<\/strong> When we message students through Canvas and include links to external sites, do those sites need to be fully compliant with Title II?<br \/>\n<strong>A:<\/strong> By linking to a third party site, that site itself is not required to be fully compliant with Title II; however, if an accommodation is requested, the linked content must be made accessible.<\/p>\n<p><strong>Q:<\/strong> How does the university propose faculty remediate accessibility for personal, unpublished, or non-library musical scores where no alternative accessible format exists?<br \/>\n<strong>A:<\/strong> The best approach is to convert the inaccessible material into digital, machine-readable formats (such as MusicXML or MIDI) and subsequently into accessible formats like Braille music or Modified Stave Notation (MSN). Since no alternative exists, faculty must create these accessible versions, often with support from university disability services or through specialized software.<\/p>\n<p><strong>Q:<\/strong> If there is no institutionally supported technology that exists to render complex music notation accessible to blind or low-vision students, and audio to deaf or hard of hearing students, how does the university define \u201cmeaningful access\u201d under Title II?<br \/>\n<strong>A:<\/strong> U<span style=\"font-size: 1rem\">nder Title II of the Americans with Disabilities Act (ADA), if institutionally supported technology does not exist to render complex music notation or audio fully accessible, the university is required to define &#8220;meaningful access&#8221; through\u00a0<\/span><strong style=\"font-size: 1rem\">effective communication<\/strong><span style=\"font-size: 1rem\">,\u00a0<\/span><strong style=\"font-size: 1rem\">reasonable modifications<\/strong><span style=\"font-size: 1rem\">, and the provision of\u00a0<\/span><strong style=\"font-size: 1rem\">alternative, tailored auxiliary aids and services<\/strong><span style=\"font-size: 1rem\">.\u00a0<\/span><\/p>\n<h2>References<\/h2>\n<ul>\n<li>University of Michigan \u2013 <a href=\"https:\/\/accessibility.umich.edu\/how-to\/music-best-practices\"><em>Music Notation Best Practices<\/em><\/a><\/li>\n<li>University of North Texas \u2013 <a href=\"https:\/\/digitalstrategy.unt.edu\/clear\/teaching-resources\/accessibility\/music-accessibility\/describing-musical-examples-text-and-alt-text.html\"><em>Describing Musical Examples with Text and Alt Text<\/em><\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Creating accessible music notation is vital for musicians with disabilities. Listed below are accessibility practices that help musicians with disabilities read, access, navigate, and comprehend sheet music.\u00a0These practices support compliance with WCAG 2.1 Level A and AA by providing text alternatives, supporting assistive technology compatibility, and ensuring proper use of color. Digital Scores Whenever possible, [&hellip;]<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":685,"menu_order":5,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-798","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/798","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=798"}],"version-history":[{"count":5,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/798\/revisions"}],"predecessor-version":[{"id":828,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/798\/revisions\/828"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=798"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":752,"date":"2025-10-22T14:48:04","date_gmt":"2025-10-22T19:48:04","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=752"},"modified":"2026-03-10T10:07:20","modified_gmt":"2026-03-10T15:07:20","slug":"microsoft-word","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/microsoft-word\/","title":{"rendered":"Accessible Microsoft Word Documents"},"content":{"rendered":"<p>An accessible document is structured to be usable by everyone, including people with disabilities who use assistive technology like screen readers. Following these practices not only ensures compliance with standards like WCAG but also creates a more organized, navigable, and professional document for all readers.<\/p>\n<p><strong>Note:<\/strong> Although this guide is written for Microsoft Word documents, it also contains guidance on creating documents in Adobe InDesign, Google Docs, and Apple Pages.<\/p>\n<h2>Document Structure and Hierarchy<\/h2>\n<ul>\n<li><strong>Headings. <\/strong>Use Word&#8217;s built-in heading styles (<strong>Heading 1<\/strong>, <strong>Heading 2<\/strong>, <strong>Heading 3<\/strong>, etc.) to create a logical document outline. Never just make text bold and larger to signify a heading. <span style=\"font-size: 1rem\">Screen readers use the heading structure to navigate a document. A user can jump from heading to heading to understand the content&#8217;s layout and find specific sections, just as a visual user would scan the page. It&#8217;s also required for an automated Table of Contents.<\/span>\n<ul>\n<li><strong>How to Do It:<\/strong> Select your text and choose the appropriate heading level from the <strong>Styles<\/strong> gallery on the <strong>Home<\/strong> tab. Always follow a logical order (e.g., Heading 1 followed by Heading 2, not Heading 1 followed by Heading 3).<\/li>\n<li><strong>Cross-Platform Notes:<\/strong>\n<ul>\n<li><strong>Adobe InDesign:<\/strong> Fully supported and essential. This is achieved using <strong>Paragraph Styles<\/strong>, which are mapped to export tags (H1, H2, etc.) for accessible PDFs.<\/li>\n<li><strong>Google Docs:<\/strong> Fully supported. Use the &#8220;Title,&#8221; &#8220;Subtitle,&#8221; and &#8220;Heading 1-6&#8221; styles from the styles dropdown.<\/li>\n<li><strong>Apple Pages:<\/strong> Fully supported. Use the paragraph styles menu to apply heading styles.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><strong>Table of Contents (ToC). <\/strong>For any document longer than about 6 pages, an automated Table of Contents is crucial for navigation. <span style=\"font-size: 1rem\">A ToC provides a clear overview and clickable links that allow users to jump directly to a section without endless scrolling.<\/span>\n<ul>\n<li><strong>How to Do It:<\/strong> Go to the <strong>References<\/strong> tab &gt; <strong>Table of Contents<\/strong>. Choose a style. This only works if you have used Heading Styles correctly.<\/li>\n<li><strong>Cross-Platform Notes:<\/strong>\n<ul>\n<li><strong>Adobe InDesign:<\/strong> A powerful and highly customizable ToC feature is available that works with Paragraph Styles.<\/li>\n<li><strong>Google Docs:<\/strong> Insert &gt; Table of contents.<\/li>\n<li><strong>Apple Pages:<\/strong> Insert &gt; Table of Contents.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Text and Content Formatting<\/h2>\n<ul>\n<li><strong><strong>Styles. <\/strong><\/strong>Use Semantic Styles Instead of Direct Formatting. Use styles like <strong style=\"font-size: 1rem\">Strong<\/strong><span style=\"font-size: 1rem\"> for important text and <\/span><strong style=\"font-size: 1rem\">Emphasis<\/strong><span style=\"font-size: 1rem\"> for emphasized text, rather than simply applying bold or italic formatting. <\/span>While modern screen readers often announce &#8220;bold&#8221; or &#8220;italic,&#8221; using semantic styles is more robust. It tells the assistive technology <em>why<\/em> the text is different (e.g., it has strong importance), which is more meaningful than just announcing a visual change.\n<ul>\n<li><strong>How to Do It:<\/strong> Open the <strong>Styles Pane<\/strong> (select the small arrow in the corner of the Styles gallery). You can find and apply the Strong and Emphasis styles from this list.<\/li>\n<li><strong>Cross-Platform Notes:<\/strong>\n<ul>\n<li><strong>Adobe InDesign:<\/strong> Fully supported via <strong>Character Styles<\/strong>. You can create specific styles for &#8220;Strong&#8221; and &#8220;Emphasis.&#8221;<\/li>\n<li><strong>Google Docs:<\/strong> Does not have user-facing Strong or Emphasis styles. It relies on the <strong>Bold<\/strong> (Ctrl\/Cmd+B) and <em>Italic<\/em> (Ctrl\/Cmd+I) buttons. While these map to the correct HTML tags (&lt;strong&gt; and &lt;em&gt;) on export to web formats, the semantic distinction isn&#8217;t as clear in the editing interface.<\/li>\n<li><strong style=\"font-size: 1rem\">Apple Pages:<\/strong><span style=\"font-size: 1rem\"> Similar to Google Docs, relies on direct bold\/italic formatting rather than distinct character styles for semantic meaning.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><strong><strong>Lists. <\/strong><\/strong>Use True Bulleted and Numbered Lists. Always use the built-in list buttons to create lists. Do not manually type hyphens, asterisks, or numbers. Proper list formatting tells a screen reader, &#8220;List with X items,&#8221; allowing the user to understand the context and navigate the list efficiently. A manually typed list is just read as a series of unrelated lines of text.\n<ul>\n<li><strong>How to Do It:<\/strong> Use the <strong>Bulleted List<\/strong> or <strong>Numbered List<\/strong> buttons on the <strong>Home<\/strong> tab.<\/li>\n<li><strong>Cross-Platform Notes: <\/strong>This feature is fully and correctly supported across <strong>Adobe InDesign<\/strong>, <strong>Google Docs<\/strong>, and <strong>Apple Pages<\/strong>.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Page Breaks. <\/strong>Use Page Breaks, Not Empty Paragraphs. To start content on a new page, insert a page break. Do not hit the Enter key repeatedly. Each empty paragraph is announced as &#8220;blank&#8221; by a screen reader, creating a confusing and noisy experience. A page break is silent and correctly forces the layout change.\n<ul>\n<li><strong>How to Do It:<\/strong> Go to <strong>Insert &gt; Page Break<\/strong> or press Ctrl+Enter (Cmd+Enter on Mac).<\/li>\n<li><strong>Cross-Platform Notes: <\/strong>This feature is fully supported across <strong>Adobe InDesign<\/strong>, <strong>Google Docs<\/strong>, and <strong>Apple Pages<\/strong>.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Accessible Links<\/h2>\n<ul>\n<li><strong>Use Descriptive Link Text, Not Raw URLs. <\/strong>The most important rule is to make the link text itself describe its destination. Avoid using raw URLs or vague phrases like &#8220;click here.&#8221; <span style=\"font-size: 1rem\">Screen reader users often navigate by pulling up a list of all links in a document. A list of descriptive links like &#8220;2025 Annual Financial Report&#8221; or &#8220;Contact Us Page&#8221; is highly useful. A list of repetitive &#8220;click here&#8221; links or long, jumbled URLs is meaningless and frustrating.<\/span>\n<ul>\n<li><strong>How to Do It:<\/strong>\n<ol>\n<li>Type out the descriptive phrase (e.g., &#8220;Review our company policies&#8221;).<\/li>\n<li>Highlight the phrase.<\/li>\n<li>Right-click and select <strong>Link<\/strong> (or press Ctrl+K \/ Cmd+K).<\/li>\n<li>Paste the URL into the &#8220;Address&#8221; field.<\/li>\n<\/ol>\n<\/li>\n<li><strong>Example: <\/strong>\n<ul>\n<li><strong style=\"font-size: 1rem\">Bad:<\/strong><span style=\"font-size: 1rem\"> To learn more, click here: <\/span><a style=\"font-size: 1rem;font-weight: 400\" href=\"https:\/\/www.google.com\/search?q=https:\/\/www.example.com\/long\/unreadable\/url\/path\">https:\/\/www.example.com\/long\/unreadable\/url\/path<\/a><span style=\"font-size: 1rem\"> (<strong>Note:<\/strong> If your document will be printed for distribution, you must provide the full URL. In this case, you will need to files; 1 for printing and 1 for posting online.) <\/span><\/li>\n<li><strong style=\"font-size: 1rem\">Good:<\/strong><span style=\"font-size: 1rem\"> You can learn more by reading the <\/span><a style=\"font-size: 1rem;font-weight: 400\" href=\"https:\/\/www.example.com\">20<\/a><strong><a style=\"font-size: 1rem;font-weight: 400\" href=\"https:\/\/www.example.com\">25 Accessibility Guidelines<\/a><\/strong><span style=\"font-size: 1rem\">.<\/span><\/li>\n<\/ul>\n<\/li>\n<li><strong>Cross-Platform Notes:<\/strong>\n<ul>\n<li><strong style=\"font-size: 1rem\">Adobe InDesign:<\/strong><span style=\"font-size: 1rem\"> Fully supported. Creating descriptive hyperlinks is a standard and essential feature for creating accessible PDFs and EPUBs.<\/span><\/li>\n<li><strong style=\"font-size: 1rem\">Google Docs:<\/strong><span style=\"font-size: 1rem\"> Fully supported. The Ctrl+K \/ Cmd+K shortcut works the same way.<\/span><\/li>\n<li><strong style=\"font-size: 1rem\">Apple Pages:<\/strong><span style=\"font-size: 1rem\"> Fully supported. Highlight text and use Cmd+K or Insert &gt; Link.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><strong>Opening Links in a New Window.\u00a0<\/strong>As a general rule, avoid forcing links to open in a new browser window or tab. This can be disorienting for users and takes control away from them. However, if it&#8217;s absolutely necessary (e.g., for a help page on a multi-step form), you must warn the user. <span style=\"font-size: 1rem\">Unexpectedly opening a new window can confuse users, especially those with cognitive disabilities or low vision. It can also break the &#8220;Back&#8221; button functionality, which is a primary navigation tool.<\/span>\n<ul>\n<li><strong>How to Do It:<\/strong> Since Word documents don&#8217;t have a &#8220;target=_blank&#8221; function like web pages, this primarily applies when exporting to PDF. The best practice is to indicate the behavior directly in the link text itself.<\/li>\n<li><strong>Example: <\/strong>You can find additional information in the <a href=\"https:\/\/www.example.com\" target=\"_blank\" rel=\"noopener\">Resource Guide (opens in a new window)<\/a>.<\/li>\n<li><strong>Cross-Platform Notes:<\/strong>\n<ul>\n<li><strong>Adobe InDesign:<\/strong> InDesign gives you precise control when exporting to PDF. In the Hyperlinks panel, you can choose options, but it&#8217;s still best practice to include a textual warning.<\/li>\n<li><strong style=\"font-size: 1rem\">Google Docs &amp; Apple Pages:<\/strong><span style=\"font-size: 1rem\"> These applications do not offer a native feature to force a link to open in a new window when exported to PDF. Therefore, the best practice of letting the user decide is followed by default.<\/span><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Visuals and Non-Text Content<\/h2>\n<ul>\n<li><strong>Alternative Text (Alt Text) for Images. <\/strong>Every image that conveys information must have alt text. Alt text provides a textual description of an image for screen reader users, who would otherwise have no access to the information.\n<ul>\n<li><strong>How to Do It:<\/strong> Right-click the image &gt; <strong>Edit Alt Text<\/strong>. Write a concise description of the image&#8217;s content and function. If an image is purely decorative, check the <strong>&#8220;Mark as decorative&#8221;<\/strong> box.<\/li>\n<li><strong>Cross-Platform Notes:<\/strong>\n<ul>\n<li><strong>Adobe InDesign:<\/strong> Via Object &gt; Object Export Options. This is a critical step for creating accessible PDFs and EPUBs from InDesign.<\/li>\n<li><strong>Google Docs:<\/strong> Right-click the image &gt; <strong>Alt text<\/strong>.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><strong>Captions for Images and Tables. <\/strong>Use the built-in caption feature to add visible descriptions for images, figures, and tables. Captions provide context for all users and create a semantic link between an object and its description.\n<ul>\n<li><strong>How to Do It:<\/strong> Right-click the object &gt; <strong>Insert Caption<\/strong>.<\/li>\n<li><strong>Cross-Platform Notes:<\/strong>\n<ul>\n<li><strong>Adobe InDesign: <\/strong>This is standard practice, often done by anchoring a text frame to the object or using features like &#8220;Live Captions.&#8221;<\/li>\n<li><strong>Google Docs:<\/strong> Does not have a native, linked captioning feature. The standard workaround is to type text in a separate paragraph below the object, but this text is not structurally linked to it.<\/li>\n<li><strong>Apple Pages:<\/strong> Lacks a dedicated captioning feature. Like Google Docs, the workaround is an unlinked text box or line of text.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><strong>Data Tables.<\/strong> Use tables for displaying tabular data, not for visual layout. <span style=\"font-size: 1rem\">Screen readers can navigate tables cell by cell and announce the corresponding column and row headers, so the user understands the data&#8217;s context. This is impossible if headers aren&#8217;t defined.<\/span>\n<ul>\n<li><strong>How to Do It:<\/strong>\n<ol>\n<li>Insert a table.<\/li>\n<li>Place your cursor in the top row.<\/li>\n<li>In the <strong>Table Design<\/strong> tab, check the <strong>&#8220;Header Row&#8221;<\/strong> box.<\/li>\n<li>Right-click the table &gt; <strong>Table Properties<\/strong> &gt; <strong>Row<\/strong> tab and ensure <strong>&#8220;Repeat as header row at the top of each page&#8221;<\/strong> is checked.<\/li>\n<li>Keep tables simple; avoid merged or split cells.<\/li>\n<\/ol>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li style=\"list-style-type: none\">\n<ul>\n<li><strong>Cross-Platform Notes:<\/strong>\n<ul>\n<li><strong>Adobe InDesign:<\/strong> Tables can be fully accessible with defined header rows in Table Options.<\/li>\n<li><strong>Google Docs:<\/strong> You can specify header rows in Format &gt; Table &gt; Table properties.<\/li>\n<li><strong>Apple Pages:<\/strong> In Format &gt; Table, you can specify a number of Header Rows and Columns.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><strong>Color and Contrast. <\/strong>Ensure text has sufficient contrast against its background and that color is not the only way to convey information.\n<ul>\n<li><strong>The Standard (WCAG):<\/strong> A contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.<\/li>\n<li><strong>How to Check:<\/strong> Use a tool like <a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\">WebAIM&#8217;s Color Contrast Checker<\/a>.<\/li>\n<li><strong>Cross-Platform Notes: <\/strong>This is a universal design principle, not a software feature. It must be adhered to in <strong>all<\/strong> platforms.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Finalizing and Exporting<\/h2>\n<ul>\n<li><strong><strong>Check for Accessibility. <\/strong><\/strong>Use Word&#8217;s built-in checker to catch common issues before distributing your document.\n<ul>\n<li><strong>How to Do It:<\/strong> Go to <strong>File &gt; Info &gt; Check for Issues &gt; Check Accessibility<\/strong>.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Convert to an Accessible PDF. <\/strong>When exporting to PDF, ensure the accessibility tags are preserved.\u00a0A tagged PDF contains the underlying structure (headings, lists, alt text) that you created in Word, making the PDF itself accessible. An untagged PDF is just a flat image of a document.<strong><br \/>\n<\/strong><\/p>\n<ul>\n<li><strong>How to Do It:<\/strong> Go to <strong>File &gt; Save a Copy<\/strong> (or Export) and select <strong>PDF<\/strong>. In the <strong>Options<\/strong> dialog, ensure the box for <strong>&#8220;Document structure tags for accessibility&#8221;<\/strong> is checked.<\/li>\n<li><strong>Cross-Platform Notes:<\/strong>\n<ul>\n<li><strong>Adobe InDesign:<\/strong> This is the gold standard for accessible PDF export, offering the most control over tagging and structure.<\/li>\n<li><strong>Google Docs:<\/strong> File &gt; Download &gt; PDF Document creates a tagged PDF, but the quality of the tagging is less reliable and offers no user control. It often requires remediation in Adobe Acrobat Pro for full compliance.<\/li>\n<li><strong>Apple Pages:<\/strong> File &gt; Export To &gt; PDF has similar limitations to Google Docs. It produces a tagged PDF, but the professional workflow for high-level accessibility is to remediate the file in Acrobat Pro.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>An accessible document is structured to be usable by everyone, including people with disabilities who use assistive technology like screen readers. Following these practices not only ensures compliance with standards like WCAG but also creates a more organized, navigable, and professional document for all readers. Note: Although this guide is written for Microsoft Word documents, [&hellip;]<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":685,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-752","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/752","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=752"}],"version-history":[{"count":4,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/752\/revisions"}],"predecessor-version":[{"id":822,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/752\/revisions\/822"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=752"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":742,"date":"2025-09-25T14:20:20","date_gmt":"2025-09-25T19:20:20","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=742"},"modified":"2026-02-09T12:52:58","modified_gmt":"2026-02-09T18:52:58","slug":"powerpoint","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/powerpoint\/","title":{"rendered":"Accessible Microsoft PowerPoint Presentations"},"content":{"rendered":"<p>Creating an accessible PowerPoint presentation ensures that your content is usable by the widest possible audience, including people with disabilities who may use assistive technologies like screen readers. Following these best practices not only helps with compliance standards like the Web Content Accessibility Guidelines (WCAG) but also results in a clearer, more professional presentation for everyone.<\/p>\n<h2>Structure and Layout: The Foundation<\/h2>\n<ul>\n<li><strong>Master Pages and Built-in Layouts.\u00a0<\/strong>Always start with PowerPoint&#8217;s built-in slide master layouts found under <strong>Home <\/strong>&gt;<strong> New Slide<\/strong> or <strong>Home <\/strong>&gt;<strong> Layout<\/strong>. Do this instead of creating a new blank slide and adding your own text boxes. Pre-defined layouts (e.g., &#8220;Title Slide,&#8221; &#8220;Title and Content&#8221;) contain placeholders that are correctly structured in the background. Screen readers rely on this structure to understand the hierarchy of information (titles, subtitles, lists) and to read the content in the correct order. Manually placed text boxes can lead to a chaotic and confusing reading order.\n<ul>\n<li><strong>How to Do It:<\/strong> Use the <strong>Slide Master<\/strong> (<strong>View <\/strong>&gt;<strong> Slide Master<\/strong>) to create your own branded, accessible templates. By modifying the master layouts, you ensure that anyone creating a presentation from your template will start with an accessible foundation.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Titles<\/strong>. Every slide <b>must <\/b>have a unique title. Titles act as a heading and is the primary way screen reader users navigate the presentation. Screen readers can pull up a list of all slide titles, allowing a user to quickly jump to the content they need, much like scanning a table of contents.\n<ul>\n<li><strong>How to Do It:<\/strong> Use the &#8220;Title&#8221; placeholder on your chosen slide layout. If you don&#8217;t want the title to be visible on the slide for design reasons, you can move it off-screen or use the <strong>Selection Pane<\/strong> (<strong>Home <\/strong>&gt;<strong> Arrange <\/strong>&gt; <strong>Selection Pane<\/strong>) to hide it visually by clicking the eye icon. The screen reader will still announce it.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Reading Order<\/strong> determines the sequence in which a screen reader announces the content on a slide.\u00a0Out of order content can change the meaning of your message or make it hard to understand.\n<ul>\n<li><strong>How to Do It:<\/strong> Go to <strong>Home <\/strong>&gt; <strong>Arrange <\/strong>&gt;<strong> Selection Pane<\/strong>. The pane lists all objects on the slide. The reading order is from the <strong>bottom up<\/strong>. Drag and drop items in the list to reorder them into a logical sequence (e.g., Title, then Subtitle, then Image, then Bulleted List).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Content and Readability<\/h2>\n<ul>\n<li><strong>Text Size:<\/strong> Use a font size of 24pt or higher for all text. Titles should be larger, such as 32pt or more.\u00a0Use <strong>bold<\/strong> for emphasis. Never underline text unless it is a link.<\/li>\n<li><strong>Fonts:<\/strong> Use simple, sans-serif fonts like <strong>Aptos<\/strong><strong>, Arial, Helvetica, or Verdana<\/strong>. Serif fonts such as Times New Roman should be avoided. Never use cursive, highly decorative or stylized fonts.<\/li>\n<li><strong>Notes.<\/strong> Keep slides simple and uncluttered. Focus on one main idea per slide. Use the <strong>Notes Section<\/strong> to provide a full transcript or more detailed information. Overly complex slides can be overwhelming visually and cognitively. The notes section provides an accessible alternative for screen reader users to get the full context. It&#8217;s also a great resource for your audience to review after the presentation.\n<ul>\n<li><strong>How to Do It:<\/strong> Below each slide, type your speaking notes or a detailed description of the slide&#8217;s content into the &#8220;Click to add notes&#8221; pane.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<ul>\n<li><strong>Lists. <\/strong>Always use the built-in tools for creating bulleted and numbered lists.\n<ul>\n<li><strong>Why it Matters:<\/strong> When you use the list tools, PowerPoint creates a proper semantic list. A screen reader will announce &#8220;List with 5 items,&#8221; and then read each item. If you manually type a hyphen or number, the screen reader just sees it as text and doesn&#8217;t understand the relationship between the items.<\/li>\n<li><strong>How to Do It:<\/strong> Use the <strong>Bulleted List<\/strong> or <strong>Numbered List<\/strong> buttons in the <strong>Home<\/strong> tab.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Color and Contrast<\/h2>\n<ul>\n<li><strong>Color Contrast.<\/strong> Ensure there is enough contrast between text color and background color. People with low vision or color blindness may not be able to read text if the contrast is too low. The minimum color contrast is<strong> 4.5:1<\/strong> for normal text and <strong>3:1<\/strong> for large text (18pt bold or 24pt regular or higher).\n<ul>\n<li><strong>How to Check:<\/strong> Use a free tool like <a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\"><strong>WebAIM&#8217;s Contrast Checker<\/strong><\/a> to identify the contrast between two colors (use the eyedropper tool inside the &#8220;Color Picker&#8221; to select the color on your screen). PowerPoint&#8217;s Accessibility Checker will also flag some contrast issues.<\/li>\n<\/ul>\n<\/li>\n<li><span style=\"font-size: 1rem\"><strong>Never rely on color alone<\/strong> as the only means of conveying information because u<\/span>sers with color blindness won&#8217;t be able to distinguish the information.\n<ul>\n<li><strong>Example:<\/strong> In a chart, use different patterns, textures, or labels in addition to colors to differentiate data series. Instead of saying &#8220;As shown in the red bar,&#8221; say &#8220;As shown in the first bar, representing Q1 sales.&#8221;<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Images and Non-Text Content<\/h2>\n<ul>\n<li><strong>Alternative Text (Alt Text)<\/strong> is a concise, textual description of an image that is read aloud by screen readers. <span style=\"font-size: 1rem\">Without alt text, a screen reader user has no way of knowing what information the image conveys. They will only hear &#8220;image.&#8221;<\/span>\n<ul>\n<li><strong>How to Do It: <\/strong>Right-click the image and select <strong>Edit Alt Text&#8230;\u00a0<\/strong>Be descriptive and concise. Describe the <strong>content and function<\/strong> of the image. What point are you making with it?\u00a0Start with the most important information.\u00a0There is no need to say &#8220;Image of&#8230;&#8221; or &#8220;Picture of&#8230;&#8221; as the screen reader already announces it as an image.\n<ul>\n<li><strong>Bad Alt Text:<\/strong> chart<\/li>\n<li><strong>Good Alt Text:<\/strong> Bar chart showing a steady increase in quarterly sales from $10M in Q1 to $25M in Q4.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Decorative Images:<\/strong> If an image is purely decorative and adds no informational value (e.g., a stylistic swoosh), check the <strong>&#8220;Mark as decorative&#8221;<\/strong> box. Screen readers skip over decorative images.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Tables. <\/strong>Keep tables simple. Avoid complex tables with merged or split cells.\n<ul>\n<li><strong>Specify Header Row:<\/strong> In the <strong>Table Design<\/strong> tab, ensure the <strong>&#8220;Header Row&#8221;<\/strong> checkbox is ticked. If your first column also contains headers, check <strong>&#8220;First Column&#8221;<\/strong> as well. This allows a screen reader to associate each data cell with its corresponding row and column headers.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Hyperlinks.<\/strong> Use descriptive hyperlink text describing where that link goes. Screen reader users often navigate by pulling up a list of all links on a page. &#8220;Click here&#8221; provides no context, but &#8220;Read the 2024 Annual Report&#8221; is clear.\n<ul>\n<li><strong>Bad Hyperlink:<\/strong> To learn more, <a href=\"https:\/\/www.example.com\/report\">click here<\/a>.<\/li>\n<li><strong>Good Hyperlink:<\/strong> You can review the full details in the <a href=\"https:\/\/www.google.com\/url?sa=E&amp;source=gmail&amp;q=https:\/\/www.example.com\/report\">2025 Annual Report<\/a>.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Checking Your Work and Sharing<\/h2>\n<ul>\n<li><strong>Accessibility Checker.<\/strong> PowerPoint has a powerful built-in tool to help you find and fix issues. Select<span style=\"font-size: 1rem\">\u00a0<\/span><strong style=\"font-size: 1rem\">Review<\/strong> &gt;<strong style=\"font-size: 1rem\"> Check Accessibility<\/strong><span style=\"font-size: 1rem\">. The checker will open a pane that lists errors, warnings, and tips, along with instructions on how to fix each one. Run this checker before finalizing your presentation.<\/span><\/li>\n<li><strong>Sharing Your File.<\/strong> When sharing your presentation, consider providing it in multiple formats.\n<ul>\n<li><strong>PowerPoint (.pptx):<\/strong> The native format is often the most accessible, as it preserves all the underlying accessibility features.<\/li>\n<li><strong>PDF:<\/strong> When saving as a PDF (<strong>File<\/strong> &gt;<strong> Save a Copy <\/strong>&gt;<strong> PDF<\/strong>), go into <strong>Options<\/strong> and ensure the box for <strong>&#8220;Document structure tags for accessibility&#8221;<\/strong> is checked. This exports the accessible structure you created into the PDF file.\u00a0<strong>NEVER print to PDF<\/strong>\u00a0(File &gt; Print &gt; Adobe PDF) as this strips the document of accessibility and structure.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Creating an accessible PowerPoint presentation ensures that your content is usable by the widest possible audience, including people with disabilities who may use assistive technologies like screen readers. Following these best practices not only helps with compliance standards like the Web Content Accessibility Guidelines (WCAG) but also results in a clearer, more professional presentation for [&hellip;]<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":685,"menu_order":3,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-742","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/742","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=742"}],"version-history":[{"count":1,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/742\/revisions"}],"predecessor-version":[{"id":809,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/742\/revisions\/809"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=742"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":537,"date":"2025-08-27T09:04:03","date_gmt":"2025-08-27T14:04:03","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=537"},"modified":"2025-08-27T09:17:56","modified_gmt":"2025-08-27T14:17:56","slug":"accessibility-testing-tools","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/resources\/accessibility-testing-tools\/","title":{"rendered":"Accessibility Testing Tools"},"content":{"rendered":"<p>This page contains a compiled list of tools and resources that support the creation and assessment of universally designed materials. All browser extensions are tied to Google Chrome. Comparable extensions or tools may also be available in other web browsers.<\/p>\n<p>Departmental technical assistance may be required to install these tools.<\/p>\n<h2><strong>Recommended <\/strong><strong>Testing Tools<\/strong><\/h2>\n<p>The following <strong>Google Chrome extensions<\/strong> and <strong>webpage tools<\/strong> are recommended for anyone getting started with accessibility testing. They are all free and require minimum technical knowledge to use.<\/p>\n<p>When testing a webpage, we recommend you run WAVE Evaluation Tool and Lighthouse first. Then use the other tools in this section to address any remaining accessibility issues.<\/p>\n<h3>Recommended Google Chrome Extensions and Tools<\/h3>\n<ul>\n<li><a href=\"https:\/\/chromewebstore.google.com\/detail\/wave-evaluation-tool\/jbbplnpkjmmeebjpijfedlgcdilocofh\">WAVE Evaluation Tool<\/a> \u2013 Identifies many WCAG errors and offers suggestions.<\/li>\n<li><a href=\"https:\/\/chromewebstore.google.com\/detail\/lighthouse\/blipmdconlkpinefehnmjammfjpmpbjk\">Lighthouse<\/a> \u2013 Open-source, automated tool for improving the performance, quality, and correctness of webpages.<\/li>\n<li><a href=\"https:\/\/chromewebstore.google.com\/detail\/window-resizer\/kkelicaakdanhinjdeammmilcgefonfh\">Window Resizer<\/a> \u2013 Alters the viewport size and orientation (e.g., \u201cmobile\u201d or \u201ctablet\u201d views, low-resolution displays).<\/li>\n<li><a href=\"https:\/\/chromewebstore.google.com\/detail\/image-alt-text-viewer\/nhmihbneenlkbjjpbimhegikadfleccd\">Image Alt Text Viewer<\/a> \u2013 Shows alternative text (alt text) for each image on the page.<\/li>\n<li><a href=\"https:\/\/chromewebstore.google.com\/detail\/h-tag\/fjigfcghoooegmndmejpoeoodplfmoca?hl=en\">H-tag<\/a> \u2013 Shows all headings (H1, H2, etc.) on the webpage.<\/li>\n<li><a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\">WebAIM Contrast Checker<\/a> \u2013 Analyzes the color contrast ratio between two colors.<\/li>\n<\/ul>\n<h2><strong>Optional <\/strong><strong>Testing Tools<\/strong><\/h2>\n<h3>Optional Google Chrome Extensions and Tools<\/h3>\n<ul>\n<li><a href=\"https:\/\/chrome.google.com\/webstore\/detail\/arc-toolkit\/chdkkkccnlfncngelccgbgfmjebmkmce\" target=\"_blank\" rel=\"noopener\">ARC Toolkit<\/a>\u00a0\u2013 Set of accessibility tools from TPGi which aids developers in identifying accessibility problems.<\/li>\n<li><a href=\"https:\/\/chromewebstore.google.com\/detail\/axe-devtools-web-accessib\/lhdoppojpmngadmnindnejefpokejbdd?utm_source=deque.com&amp;utm_medium=referral&amp;utm_campaign=axe_hero\">axe DevTools<\/a> \u2013 Developer-centric toolset of unit testing and integration testing capabilities.<\/li>\n<li><a href=\"https:\/\/chromewebstore.google.com\/detail\/grayscale-the-web-save-si\/mblmpdpfppogibmoobibfannckeeleag\">Grayscale the Web<\/a> \u2013 Allows you to turn on grayscale (only shades of gray) for pages.<\/li>\n<li><a href=\"https:\/\/chromewebstore.google.com\/detail\/siteimprove-accessibility\/djcglbmbegflehmbfleechkjhmedcopn\">Siteimprove Accessibility Checker<\/a> \u2013 Checks the accessibility of any webpage, including WCAG and ARIA. (This tool is separate from the Siteimprove website.)<\/li>\n<li><a href=\"https:\/\/www.ssa.gov\/accessibility\/andi\/help\/install.html\">ANDI (Accessible Name &amp; Description Inspector)<\/a> \u2013 Provides automated detection of accessibility issues and reveals what a screen reader should say for interactive elements (the accessible name computation).<\/li>\n<\/ul>\n<h3>Siteimprove<\/h3>\n<p>Siteimprove is a Software as a Service (SaaS) Texas A&amp;M System members use to improve the quality assurance, accessibility, and SEO (Search Engine Optimization) of our web content (including PDFs). Approximately every five days, Siteimprove &#8220;crawls&#8221; each website and compiles the data into graphs, charts, and other useful reports, located on the <a href=\"http:\/\/siteimprove.com\">Siteimprove web platform<\/a>. Examples of issues include broken links, misspellings, insufficient color contrast, and images with missing alt text. To access Siteimprove, contact your member&#8217;s web team.<\/p>\n<h3>Screen Readers<\/h3>\n<p>Screen readers are assistive technology (AT) that convert content on a webpage (text, images, videos, etc.) into audio speech or braille. They are used primarily by individuals with vision impairments and learning disabilities.<\/p>\n<ul>\n<li><a href=\"https:\/\/www.nvaccess.org\/download\/\">NVDA Screen Reader<\/a> (free application)<\/li>\n<li><a href=\"https:\/\/www.freedomscientific.com\/products\/software\/jaws\/\">JAWS\u00ae (Job Access With Speech)<\/a> (paid application)<\/li>\n<li><a href=\"https:\/\/support.apple.com\/guide\/voiceover\/welcome\/mac\">Apple MacOS and iOS VoiceOver<\/a> (built-in to Mac devices)<\/li>\n<li><a href=\"https:\/\/support.microsoft.com\/en-us\/windows\/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1\">Windows Narrator<\/a> (built-in to Windows devices)<\/li>\n<\/ul>\n<h3>Screen Magnifiers<\/h3>\n<ul>\n<li><a href=\"https:\/\/www.freedomscientific.com\/products\/software\/zoomtext\/\">ZoomText<\/a> (screen magnifier, Windows only)<\/li>\n<\/ul>\n<h3>Grayscale and Color Mode Testing<\/h3>\n<ul>\n<li>Android: <a href=\"https:\/\/support.google.com\/accessibility\/android\/answer\/6151850?hl=en\">Change Text &amp; Display Settings<\/a><\/li>\n<li>iPhone or iPad: <a href=\"https:\/\/support.apple.com\/en-us\/HT207025\">Use Display and Text Size Preferences<\/a><\/li>\n<li>Mac: <a href=\"https:\/\/support.apple.com\/guide\/mac-help\/use-color-filters-mchl11ddd4b3\/mac\">Mac Display Colors<\/a><\/li>\n<li>Windows:\u00a0<a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4344736\/windows-10-use-color-filters\">Window Color Filters<\/a><\/li>\n<\/ul>\n<h3>Built-in Accessibility Checkers<\/h3>\n<ul>\n<li>Adobe Acrobat: <a href=\"https:\/\/helpx.adobe.com\/acrobat\/using\/create-verify-pdf-accessibility.html\"><span data-contrast=\"none\">Adobe PDF Document Accessibility Checker<\/span><\/a><\/li>\n<li>Microsoft applications: <span data-contrast=\"none\"><a href=\"https:\/\/support.microsoft.com\/en-us\/office\/improve-accessibility-with-the-accessibility-checker-a16f6de0-2f39-4a2b-8bd8-5ad801426c7f?ui=en-us&amp;rs=en-us&amp;ad=us\">Microsoft Accessibility Checker<\/a><\/span><\/li>\n<\/ul>\n<h2>External Resources<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.w3.org\/WAI\/test-evaluate\/tools\/list\/\">W3C: Web Accessibility Evaluation Tool list<\/a><\/li>\n<li><a href=\"https:\/\/webaim.org\/resources\/htmlcheatsheet\/\">WebAIM: HTML Semantics and Accessibility Cheat Sheet<\/a><\/li>\n<li><a href=\"https:\/\/webaim.org\/resources\/evalquickref\/\">WebAIM: Quick Reference &#8211; Testing Web Content for Accessibility<\/a><\/li>\n<li><a href=\"https:\/\/webaim.org\/standards\/wcag\/checklist\">WebAIM: WebAIM&#8217;s WCAG 2 Checklist<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>This page contains a compiled list of tools and resources that support the creation and assessment of universally designed materials. All browser extensions are tied to Google Chrome. Comparable extensions or tools may also be available in other web browsers. Departmental technical assistance may be required to install these tools. Recommended Testing Tools The following [&hellip;]<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":23,"menu_order":13,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-537","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/537","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=537"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/537\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/23"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=537"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":716,"date":"2025-07-15T15:36:04","date_gmt":"2025-07-15T20:36:04","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=716"},"modified":"2026-02-09T12:52:19","modified_gmt":"2026-02-09T18:52:19","slug":"docusign","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/docusign\/","title":{"rendered":"Accessible DocuSign Documents"},"content":{"rendered":"<p>Reviewing a DocuSign document for accessibility issues is a bit different from reviewing a regular PDF, because:<\/p>\n<ul>\n<li>Once a document is signed and finalized in DocuSign, it becomes locked and uneditable.<\/li>\n<li>Accessibility tags cannot be added or fixed after signing.<\/li>\n<li>DocuSign\u2019s platform does not perform accessibility remediation, nor does it create accessible tags automatically.<\/li>\n<\/ul>\n<h2><strong>Accessibility Review Process for DocuSign Documents<\/strong><\/h2>\n<p>Here\u2019s the process to check a document intended for DocuSign before it is signed and locked.<\/p>\n<p><strong>Step-by-Step Accessibility Review Before Using DocuSign<\/strong><\/p>\n<ol>\n<li>Start with a Source Document (e.g., Word).\n<ul>\n<li>Run the <a href=\"https:\/\/support.microsoft.com\/en-us\/office\/improve-accessibility-with-the-accessibility-checker-a16f6de0-2f39-4a2b-8bd8-5ad801426c7f\">Microsoft Word Accessibility Checker<\/a>.<\/li>\n<li>Fix:\n<ul>\n<li>Missing alt text<\/li>\n<li>Poor heading structure<\/li>\n<li>Table headers not defined<\/li>\n<li>Improper reading order<\/li>\n<\/ul>\n<\/li>\n<li>Save as:\n<ul>\n<li>Word (.docx) for backup<\/li>\n<li>PDF for accessibility review<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li><strong>Check the PDF in Adobe Acrobat<\/strong>\n<ul>\n<li>Open the saved PDF in Adobe Acrobat Pro.<\/li>\n<li>Run the Full Accessibility Check (Tools &gt; Accessibility &gt; Full Check).<\/li>\n<li>Fix issues such as:\n<ul>\n<li>Missing document title<\/li>\n<li>Untagged content<\/li>\n<li>Improper reading order<\/li>\n<li>Missing alt text or language specification<\/li>\n<\/ul>\n<\/li>\n<li>Use the Tags panel to ensure all elements (headings, lists, tables) are tagged correctly.<\/li>\n<li>Save the fully remediated PDF.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Optional: Insert Signature Placeholder<\/strong>\n<ul>\n<li>If needed, insert a blank signature line or placeholder image (e.g., \u201cSignature Here\u201d) before signing.<\/li>\n<li>Add alt text to any visual placeholder indicating it&#8217;s for a signature.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Sign the Document<\/strong>\n<ul>\n<li>Once the PDF is fully accessible, sign it using DocuSign.<\/li>\n<li><strong>Note:<\/strong> After signing, you cannot add or change accessibility tags.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<h3><strong>Important Accessibility Notes About DocuSign PDFs<\/strong><\/h3>\n<ul>\n<li>DocuSign\u2019s finalized PDFs do not always preserve tag structures or reading order.<\/li>\n<li>Signatures often appear as images without alt text or untagged content, triggering errors in Adobe&#8217;s accessibility checker.<\/li>\n<li><strong>Best practice:<\/strong> insert the signed timestamp as an image into the original Word document and re-export it to PDF, rather than relying on DocuSign\u2019s locked version.<\/li>\n<\/ul>\n<h3><strong>How to Document the Review<\/strong><\/h3>\n<p>If required for compliance tracking, k<span style=\"font-size: 1rem\">eep a record of:<\/span><\/p>\n<ul>\n<li>Accessibility check results (screenshots or reports)<\/li>\n<li>Final review prior to signature<\/li>\n<li>Confirmation that no accessibility issues existed before signing<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Reviewing a DocuSign document for accessibility issues is a bit different from reviewing a regular PDF, because: Once a document is signed and finalized in DocuSign, it becomes locked and uneditable. Accessibility tags cannot be added or fixed after signing. DocuSign\u2019s platform does not perform accessibility remediation, nor does it create accessible tags automatically. Accessibility [&hellip;]<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":685,"menu_order":4,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-716","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/716","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=716"}],"version-history":[{"count":1,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/716\/revisions"}],"predecessor-version":[{"id":807,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/716\/revisions\/807"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=716"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":700,"date":"2025-07-01T11:15:24","date_gmt":"2025-07-01T16:15:24","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=700"},"modified":"2026-02-09T12:51:58","modified_gmt":"2026-02-09T18:51:58","slug":"emails","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/emails\/","title":{"rendered":"Accessible Emails"},"content":{"rendered":"<p><a href=\"https:\/\/apps.system.tamus.edu\/resources\/download\/Accessibility\/Videos\/Accessible_Emails.html\">Watch our video on creating accessible emails!<\/a>\u00a0<a href=\"https:\/\/it.tamus.edu\/accessibility\/wp-content\/uploads\/sites\/31\/2025\/04\/Accessible_Emails_Transcript.docx\">(or download the transcript)<\/a>.\u00a0This video goes over how to improve the accessibility and usability of emails in Microsoft Outlook.<\/p>\n<h2>Accessible Email Checklist<\/h2>\n<ul>\n<li><strong>Color contrast.\u00a0<\/strong>The color of text and other meaningful information needs to be distinct from the background color. Y<span data-contrast=\"none\">ellow text on a white background, for example, is extremely difficult to read. The higher the color contrast, the better. <\/span><span data-contrast=\"none\">Use <a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\">WebAIM&#8217;s Color Contrast Checker<\/a><\/span><span data-contrast=\"none\"> to check the contrast between two colors.<\/span><\/li>\n<li><strong>Alternative Text (or Alt Text) <\/strong>is needed for all non-decorative multimedia, including images, <span data-contrast=\"none\">social media posts, graphs, charts, flyers, banners, and infographics<\/span><span data-contrast=\"none\">. Screen readers (a type of assistive technology) helps <\/span><span data-contrast=\"none\">individuals with limited or no vision understand what the multimedia is by reading the alt text out loud. Your email platform should provide<\/span><span data-contrast=\"none\"> a simple way to provide alt text for multimedia.<\/span><span data-ccp-props=\"{&quot;134233279&quot;:true,&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}\">\u00a0<\/span><a href=\"https:\/\/www.section508.gov\/create\/alternative-text\/\"><span class=\"TextRun SCXW160510362 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun CommentStart CommentHighlightPipeRest CommentHighlightRest SCXW160510362 BCX0\">Learn how to write <\/span><\/span><span class=\"TextRun Underlined SCXW160510362 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"none\"><span class=\"NormalTextRun CommentHighlightRest SCXW160510362 BCX0\" data-ccp-charstyle=\"Hyperlink\">effective <\/span><span class=\"NormalTextRun CommentHighlightRest SCXW160510362 BCX0\" data-ccp-charstyle=\"Hyperlink\">alt<\/span> <span class=\"NormalTextRun CommentHighlightRest SCXW160510362 BCX0\" data-ccp-charstyle=\"Hyperlink\">text<\/span><\/span><\/a><span class=\"TextRun SCXW160510362 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun CommentHighlightPipeRest SCXW160510362 BCX0\">.<\/span><\/span><\/li>\n<li><span class=\"TextRun SCXW145738438 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW145738438 BCX0\"><strong>Links. <\/strong>Links should describe their destination and\/or purpose. Do not repeat information<\/span><span class=\"NormalTextRun SCXW145738438 BCX0\"> in text or link. For example, do not insert links like &#8220;read more&#8221; or &#8220;<\/span><span class=\"NormalTextRun SCXW145738438 BCX0\">click here.&#8221; Never underline text <em>unless\u00a0<\/em>it is a link.<\/span><\/span><\/li>\n<li><strong>Plain Language.<\/strong> Write in a way that is <span data-contrast=\"auto\">clear and easy to understand.<\/span><span data-ccp-props=\"{}\"> Organize content for easy scanning and understanding. <\/span>Your writing should match <a href=\"https:\/\/www.plainlanguage.gov\/guidelines\/\"><span data-contrast=\"none\">Federal Plain Language Guidelines<\/span><\/a><span data-contrast=\"auto\">.<\/span><\/li>\n<li><strong>Lists. <\/strong>Use ordered lists (e.g., numbered lists) when items need to be in a specific order (such as step-by-step instructions). Use unordered lists (like bullets) when the sequence matters less (for example, lists of people). Lists organize your content, both visually and practically. It also helps assistive technology navigate your email.<\/li>\n<li><strong>Images. <\/strong><a class=\"ProsemirrorEditor-link\" style=\"font-size: 1rem\" href=\"https:\/\/support.microsoft.com\/en-us\/office\/add-alternative-text-to-a-shape-picture-chart-smartart-graphic-or-other-object-44989b2a-903c-4d9a-b742-6a75b451c669\">Add alternative text<\/a><span style=\"font-size: 1rem\"> (alt text) <\/span>that concisely describes the purpose or meaning of each image, unless the image is purely decorative. If the image contains informational text, it should be included within the alt text. If the image is purely decorative, enter \u2018decorative image\u2019 in the description field. A &#8220;Mark as Decorative&#8221; checkbox may be available in some Outlook versions. Do not use the &#8220;Generate alt text for me&#8221; button. Position the picture in line whenever possible to ensure the alt text is read at the appropriate time within the document. For complex images and informational graphics, provide a full text description in the body of the email or in an easy-to-access secondary location (such as a linked webpage). For images that also serve as links, a description of the link purpose or destination should be included in the alt text in addition to the description of the image. In addition to applying the appropriate above recommendations, a word document attached with the email will ensure the email is accessible for everyone.<\/li>\n<\/ul>\n<h2>Additional Resources<\/h2>\n<p>Microsoft Outlook: <a href=\"https:\/\/support.microsoft.com\/en-us\/office\/make-your-outlook-email-accessible-to-people-with-disabilities-71ce71f4-7b15-4b7a-a2e3-cf91721bbacb?ui=en-us&amp;rs=en-us&amp;ad=us\">Make your Outlook email accessible to people with disabilities<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Watch our video on creating accessible emails!\u00a0(or download the transcript).\u00a0This video goes over how to improve the accessibility and usability of emails in Microsoft Outlook. Accessible Email Checklist Color contrast.\u00a0The color of text and other meaningful information needs to be distinct from the background color. Yellow text on a white background, for example, is extremely [&hellip;]<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":685,"menu_order":5,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-700","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/700","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=700"}],"version-history":[{"count":1,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/700\/revisions"}],"predecessor-version":[{"id":806,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/700\/revisions\/806"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=700"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":697,"date":"2025-07-01T11:14:00","date_gmt":"2025-07-01T16:14:00","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=697"},"modified":"2026-02-09T12:50:59","modified_gmt":"2026-02-09T18:50:59","slug":"pdfs","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/pdfs\/","title":{"rendered":"Accessible PDFs"},"content":{"rendered":"<p><a href=\"https:\/\/apps.system.tamus.edu\/resources\/download\/WorkdayServices\/Videos\/Accessible_PDFs.html\">Watch our video on creating accessible PDFs!<\/a>\u00a0<a href=\"https:\/\/it.tamus.edu\/accessibility\/wp-content\/uploads\/sites\/31\/2025\/04\/Accessible_PDFs_Transcript.docx\">(or download the transcript)<\/a>. This video goes over how to improve the accessibility and usability of emails in Microsoft Outlook.<\/p>\n<h2>Before you Make a PDF<\/h2>\n<ul>\n<li><span data-contrast=\"auto\"><span class=\"TextRun SCXW151215318 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW151215318 BCX0\">Webpages are preferred over PDFs because webpages are generally easier to make accessible. Always choose a webpage if you have the choice. Convert your existing PDFs into webpages when possible.<\/span><\/span><\/span><\/li>\n<li><span data-contrast=\"auto\">Do not post PDFs on websites or social media.<\/span><\/li>\n<li><span class=\"TextRun SCXW61252263 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW61252263 BCX0\">Digital Flyers\u00a0are\u00a0<em>not<\/em>\u00a0allowed<\/span><\/span><span class=\"TextRun SCXW61252263 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW61252263 BCX0\">\u00a0on any A&amp;M System website<\/span><span class=\"NormalTextRun SCXW61252263 BCX0\">s<\/span><span class=\"NormalTextRun SCXW61252263 BCX0\">.\u00a0<\/span><\/span><span data-contrast=\"auto\">They will be removed without notice.<\/span><span data-ccp-props=\"{}\">\u00a0<\/span><span data-contrast=\"auto\">Content owners are responsible for fixing any resulting issues (e.g., broken links).<\/span><span data-ccp-props=\"{}\">\u00a0<span class=\"TextRun SCXW235067197 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW235067197 BCX0\">Physical,<\/span><span class=\"NormalTextRun SCXW235067197 BCX0\">\u00a0printed materials are allowed.<\/span><\/span><span class=\"EOP SCXW235067197 BCX0\" data-ccp-props=\"{}\">\u00a0<span class=\"TextRun SCXW241019130 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW241019130 BCX0\">A<\/span><span class=\"NormalTextRun SCXW241019130 BCX0\">\u00a0plain text version must be posted online to\u00a0<\/span><span class=\"NormalTextRun SCXW241019130 BCX0\">meet<\/span><span class=\"NormalTextRun SCXW241019130 BCX0\">\u00a0accessibility requirements.<\/span><\/span><\/span><\/span><\/li>\n<\/ul>\n<h2>Accessible PDF Checklist<\/h2>\n<ul>\n<li><strong>Color contrast.\u00a0<\/strong>The color of text and other meaningful information needs to be distinct from the background color. Y<span data-contrast=\"none\">ellow text on a white background, for example, is extremely difficult to read. The higher the color contrast, the better. <\/span><span data-contrast=\"none\">Use <a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\">WebAIM&#8217;s Color Contrast Checker<\/a><\/span><span data-contrast=\"none\"> to check the contrast between two colors.<\/span><\/li>\n<li><strong>Alternative Text (or Alt Text) <\/strong>is needed for all non-decorative multimedia, including images, <span data-contrast=\"none\">social media posts, graphs, charts, flyers, banners, and infographics<\/span><span data-contrast=\"none\">. Screen readers (a type of assistive technology) helps <\/span><span data-contrast=\"none\">individuals with limited or no vision understand what the multimedia is by reading the alt text out loud. Adobe Acrobat provides a<\/span><span data-contrast=\"none\">\u00a0<a href=\"https:\/\/elearning.adobe.com\/2024\/02\/how-to-add-alt-text-in-adobe-acrobat-a-step-by-step-guide\/\">simple way to provide alt text<\/a> for multimedia.<\/span><span data-ccp-props=\"{&quot;134233279&quot;:true,&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}\">\u00a0<\/span><a href=\"https:\/\/www.section508.gov\/create\/alternative-text\/\"><span class=\"TextRun SCXW160510362 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun CommentStart CommentHighlightPipeRest CommentHighlightRest SCXW160510362 BCX0\">Learn how to write <\/span><\/span><span class=\"TextRun Underlined SCXW160510362 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"none\"><span class=\"NormalTextRun CommentHighlightRest SCXW160510362 BCX0\" data-ccp-charstyle=\"Hyperlink\">effective <\/span><span class=\"NormalTextRun CommentHighlightRest SCXW160510362 BCX0\" data-ccp-charstyle=\"Hyperlink\">alt<\/span> <span class=\"NormalTextRun CommentHighlightRest SCXW160510362 BCX0\" data-ccp-charstyle=\"Hyperlink\">text<\/span><\/span><\/a><span class=\"TextRun SCXW160510362 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun CommentHighlightPipeRest SCXW160510362 BCX0\">.<\/span><\/span><\/li>\n<li><span class=\"TextRun SCXW145738438 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW145738438 BCX0\"><strong>Links. <\/strong>Links should describe their destination and\/or purpose. Do not repeat information<\/span><span class=\"NormalTextRun SCXW145738438 BCX0\"> in text or link. For example, do not insert links like &#8220;read more&#8221; or &#8220;<\/span><span class=\"NormalTextRun SCXW145738438 BCX0\">click here.&#8221; Never underline text <em>unless\u00a0<\/em>it is a link.<\/span><\/span><\/li>\n<li><strong>Plain Language.<\/strong> Write in a way that is <span data-contrast=\"auto\">clear and easy to understand.<\/span><span data-ccp-props=\"{}\"> Organize content for easy scanning and understanding. <\/span>Your writing should match <a href=\"https:\/\/www.plainlanguage.gov\/guidelines\/\"><span data-contrast=\"none\">Federal Plain Language Guidelines<\/span><\/a><span data-contrast=\"auto\">.<\/span><\/li>\n<li><strong>Lists. <\/strong>Use ordered lists (e.g., numbered lists) when items need to be in a specific order (such as step-by-step instructions). Use unordered lists (like bullets) when the sequence matters less (for example, lists of people). Lists organize your content, both visually and practically. It also helps assistive technology navigate your PDF.<\/li>\n<li><strong>Headings.<\/strong> Each PDF should have a proper heading structure. This means ensuring headings structured logically (H2 comes after H1, H3 comes after H2, etc.). Headings should not be used for decorative purposes only.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Watch our video on creating accessible PDFs!\u00a0(or download the transcript). This video goes over how to improve the accessibility and usability of emails in Microsoft Outlook. Before you Make a PDF Webpages are preferred over PDFs because webpages are generally easier to make accessible. Always choose a webpage if you have the choice. Convert your [&hellip;]<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":685,"menu_order":6,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-697","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/697","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=697"}],"version-history":[{"count":1,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/697\/revisions"}],"predecessor-version":[{"id":804,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/697\/revisions\/804"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=697"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":695,"date":"2025-07-01T11:06:51","date_gmt":"2025-07-01T16:06:51","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=695"},"modified":"2026-02-09T12:53:15","modified_gmt":"2026-02-09T18:53:15","slug":"social-media","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/social-media\/","title":{"rendered":"Accessible Social Media"},"content":{"rendered":"<h2>Accessible Social Media Checklist<\/h2>\n<ul>\n<li><span data-contrast=\"auto\"><strong>Hashtags<\/strong>. Use \u201cCamel Case\u201d for hashtags (e.g., #WeLoveTexas). However, l<\/span><span data-contrast=\"auto\">imit your use of hashtags because screen readers will read each one out loud.<\/span><\/li>\n<li><span data-contrast=\"auto\"><strong>Emojis and Special Characters.<\/strong> Use emojis sparingly. Screen readers read out their full descriptions.\u00a0<\/span><span data-ccp-props=\"{}\"><em>Never\u00a0<\/em>use emoticons such as :-} because screen readers will read each character individually. It is best to avoid using special characters that don\u2019t appear on your keyboard. <\/span><\/li>\n<li><strong>Closed Captions.<\/strong> All videos need synchronized closed captions<span data-contrast=\"none\"> (sometimes abbreviated as \u201cCC\u201d). Closed captions transcribe all spoken words as well as as well as relevant non-verbal sounds (laughter and applause, for example). Provide the speaker&#8217;s name when there are multiple voices. Closed captions should <em>always<\/em> be provided to the user.<\/span>\n<ul>\n<li><span data-contrast=\"auto\"><strong>Note: <\/strong>Closed captions can be turned on and off, as opposed to open captions, which are permanently embedded (i.e., &#8220;burned&#8221;) into the video and cannot be turned off. Use closed captions instead; you can usually upload them via an .srt file or use auto-captioning tools (such as Stories on Instagram).<\/span><span data-contrast=\"auto\">\u00a0Subtitles are captions presented in a language other than the one that is primarily spoken in the video.<\/span><\/li>\n<\/ul>\n<\/li>\n<li><strong>Color contrast.\u00a0<\/strong>The color of text and other meaningful information needs to be distinct from the background color. Y<span data-contrast=\"none\">ellow text on a white background, for example, is extremely difficult to read. The higher the color contrast, the better. <\/span><span data-contrast=\"none\">Use <a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\">WebAIM&#8217;s Color Contrast Checker<\/a><\/span><span data-contrast=\"none\"> to check the contrast between two colors.<\/span><\/li>\n<li><strong>Alternative Text (or Alt Text) <\/strong>is needed for all non-decorative multimedia, including images, <span data-contrast=\"none\">social media posts, graphs, charts, flyers, banners, and infographics<\/span><span data-contrast=\"none\">. Screen readers (a type of assistive technology) helps <\/span><span data-contrast=\"none\">individuals with limited or no vision understand what the multimedia is by reading the alt text out loud. Y<\/span><span data-contrast=\"none\">our social media platform should provide a simple way to provide alt text for multimedia.<\/span><span data-ccp-props=\"{&quot;134233279&quot;:true,&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:240}\"> If not, describe the image in the post&#8217;s description. <\/span><a href=\"https:\/\/www.section508.gov\/create\/alternative-text\/\"><span class=\"TextRun SCXW160510362 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun CommentStart CommentHighlightPipeRest CommentHighlightRest SCXW160510362 BCX0\">Learn how to write <\/span><\/span><span class=\"TextRun Underlined SCXW160510362 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"none\"><span class=\"NormalTextRun CommentHighlightRest SCXW160510362 BCX0\" data-ccp-charstyle=\"Hyperlink\">effective <\/span><span class=\"NormalTextRun CommentHighlightRest SCXW160510362 BCX0\" data-ccp-charstyle=\"Hyperlink\">alt<\/span> <span class=\"NormalTextRun CommentHighlightRest SCXW160510362 BCX0\" data-ccp-charstyle=\"Hyperlink\">text<\/span><\/span><\/a><span class=\"TextRun SCXW160510362 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun CommentHighlightPipeRest SCXW160510362 BCX0\">.<\/span><\/span><\/li>\n<li><strong>AI.<\/strong> Always review any automatically- or AI-generated text for accuracy, including closed captions. Avoid duplicating post text in the alt text.<\/li>\n<li><span class=\"TextRun SCXW145738438 BCX0\" lang=\"EN-US\" xml:lang=\"EN-US\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW145738438 BCX0\"><strong>Links. <\/strong>Links should describe their destination and\/or purpose. Do not repeat information<\/span><span class=\"NormalTextRun SCXW145738438 BCX0\"> in text or link. For example, do not insert links like &#8220;read more&#8221; or &#8220;<\/span><span class=\"NormalTextRun SCXW145738438 BCX0\">click here.&#8221; Never underline text <em>unless\u00a0<\/em>it is a link.<\/span><\/span><\/li>\n<li><strong>Plain Language.<\/strong> Write in a way that is <span data-contrast=\"auto\">clear and easy to understand.<\/span><span data-ccp-props=\"{}\"> Organize content for easy scanning and understanding. <\/span>Your writing should match <a href=\"https:\/\/www.plainlanguage.gov\/guidelines\/\"><span data-contrast=\"none\">Federal Plain Language Guidelines<\/span><\/a><span data-contrast=\"auto\">.<\/span><\/li>\n<li><strong>Lists. <\/strong>Use ordered lists (e.g., numbered lists) when items need to be in a specific order (such as step-by-step instructions). Use unordered lists (like bullets) when the sequence matters less (for example, lists of people). Lists organize your content, both visually and practically. It also helps assistive technology navigate your post.<\/li>\n<\/ul>\n<h2>Additional Resources<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.facebook.com\/accessibility\/posts\/3026154860761552\">Make Your Facebook and Instagram Posts More Accessible<\/a>.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Accessible Social Media Checklist Hashtags. Use \u201cCamel Case\u201d for hashtags (e.g., #WeLoveTexas). However, limit your use of hashtags because screen readers will read each one out loud. Emojis and Special Characters. Use emojis sparingly. Screen readers read out their full descriptions.\u00a0Never\u00a0use emoticons such as :-} because screen readers will read each character individually. It is [&hellip;]<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":685,"menu_order":7,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-695","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/695","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=695"}],"version-history":[{"count":1,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/695\/revisions"}],"predecessor-version":[{"id":812,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/695\/revisions\/812"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=695"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":693,"date":"2025-07-01T11:05:53","date_gmt":"2025-07-01T16:05:53","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=693"},"modified":"2026-02-09T12:53:09","modified_gmt":"2026-02-09T18:53:09","slug":"videos","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/videos\/","title":{"rendered":"Accessible Videos"},"content":{"rendered":"<h2>Accessible Video Checklist<\/h2>\n<ul>\n<li><strong>Closed Captions.<\/strong> All videos need synchronized closed captions<span data-contrast=\"none\"> (sometimes abbreviated as \u201cCC\u201d). Closed captions transcribe all spoken words as well as well as relevant non-verbal sounds (laughter and applause, for example). Provide the speaker&#8217;s name when there are multiple voices. Closed captions should <em>always<\/em> be provided to the user.<\/span>\n<ul>\n<li><span data-contrast=\"auto\"><strong>Note: <\/strong>Closed captions can be turned on and off, as opposed to open captions, which are permanently embedded (i.e., &#8220;burned&#8221;) into the video and cannot be turned off. Use closed captions instead; you can usually upload them via an .srt file.<\/span><span data-contrast=\"auto\">\u00a0Subtitles are captions presented in a language other than the one that is primarily spoken in the video.<\/span><\/li>\n<\/ul>\n<\/li>\n<li><strong>Transcripts<\/strong>. In addition to closed captions, all videos also need a transcript (a written text version of everything spoken in the video). Visual information that is important to understanding, but not spoken-aloud, should also be described in the transcript.<\/li>\n<li><strong>Audio Descriptions.<\/strong> If your video has important visual information that is <em>not<\/em> spoken-aloud, it needs a separate audio description track. Audio description audibly narrates what is happening on the screen to users with limited or no vision. <a href=\"https:\/\/www.section508.gov\/create\/synchronized-media\/#audio-description\">Learn more about audio descriptions<\/a>.<\/li>\n<li><span class=\"TextRun SCXW10145747 BCX0\" lang=\"EN\" xml:lang=\"EN\" data-contrast=\"auto\"><span class=\"NormalTextRun SCXW10145747 BCX0\"><strong>Flashing content.<\/strong> Limit flashing, blinking, flickering, or rapidly changing shots to no more than three per second.<\/span><\/span><span class=\"EOP SCXW10145747 BCX0\" data-ccp-props=\"{&quot;335557856&quot;:16777215}\"> Or better yet, avoid flashing content altogether. Keep transitions smooth and avoid excessive flashing, flickering or rapidly changing shots.<\/span><\/li>\n<li><strong>Color contrast.\u00a0<\/strong>The color of text and other meaningful information needs to be distinct from the background color. Y<span data-contrast=\"none\">ellow text on a white background, for example, is extremely difficult to read. The higher the color contrast, the better. <\/span><span data-contrast=\"none\">Use <a href=\"https:\/\/webaim.org\/resources\/contrastchecker\/\">WebAIM&#8217;s Color Contrast Checker<\/a><\/span><span data-contrast=\"none\"> to check the contrast between two colors. Also, always ensure the<\/span><span data-contrast=\"none\"> lower third of the screen is dark enough so closed captions (white text) have enough contrast.<\/span><\/li>\n<li><strong>Plain Language.<\/strong> Write and speak in a way that is clear and easy to understand.<span data-ccp-props=\"{}\">\u00a0Organize content for easy scanning and understanding. <\/span>Your writing should match <a href=\"https:\/\/www.plainlanguage.gov\/guidelines\/\"><span data-contrast=\"none\">Federal Plain Language Guidelines<\/span><\/a><span data-contrast=\"auto\">.<\/span><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Accessible Video Checklist Closed Captions. All videos need synchronized closed captions (sometimes abbreviated as \u201cCC\u201d). Closed captions transcribe all spoken words as well as well as relevant non-verbal sounds (laughter and applause, for example). Provide the speaker&#8217;s name when there are multiple voices. Closed captions should always be provided to the user. Note: Closed captions [&hellip;]<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":685,"menu_order":8,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-693","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/693","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=693"}],"version-history":[{"count":1,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/693\/revisions"}],"predecessor-version":[{"id":810,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/693\/revisions\/810"}],"up":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=693"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":685,"date":"2025-07-01T11:02:08","date_gmt":"2025-07-01T16:02:08","guid":{"rendered":"https:\/\/it.tamus.edu\/accessibility\/?page_id=685"},"modified":"2025-10-22T14:51:22","modified_gmt":"2025-10-22T19:51:22","slug":"accessibility-guides","status":"publish","type":"page","link":"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/","title":{"rendered":"Accessibility Guides"},"content":{"rendered":"<p>Our Accessibility Guides provide you best practices, checklists, and resources for creating different types of accessible digital content. Select a topic below to get started.<\/p>\n<ul>\n<li><a href=\"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/docusign\/\">DocuSign<\/a><\/li>\n<li><a href=\"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/emails\/\"><span data-contrast=\"none\">Emails<\/span><\/a><\/li>\n<li><a href=\"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/powerpoint\/\">Microsoft PowerPoint<\/a><\/li>\n<li><a href=\"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/microsoft-word\/\">Microsoft Word<\/a><\/li>\n<li><a href=\"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/pdfs\/\"><span data-contrast=\"none\">PDFs<\/span><\/a><\/li>\n<li><a href=\"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/social-media\/\"><span data-contrast=\"none\">Social Media<\/span><\/a><\/li>\n<li><a href=\"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/videos\/\"><span data-contrast=\"none\">Videos <\/span><\/a><\/li>\n<li><a href=\"https:\/\/it.tamus.edu\/accessibility\/accessibility-guides\/webpages\/\"><span data-contrast=\"none\">Webpages<\/span><\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Our Accessibility Guides provide you best practices, checklists, and resources for creating different types of accessible digital content. Select a topic below to get started. DocuSign Emails Microsoft PowerPoint Microsoft Word PDFs Social Media Videos Webpages<\/p>\n","protected":false},"author":37849,"featured_media":0,"parent":0,"menu_order":10,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-685","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/users\/37849"}],"replies":[{"embeddable":true,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/comments?post=685"}],"version-history":[{"count":0,"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/pages\/685\/revisions"}],"wp:attachment":[{"href":"https:\/\/it.tamus.edu\/accessibility\/wp-json\/wp\/v2\/media?parent=685"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}]