<?xml version="1.0"?>
<News hasArchived="false" page="1" pageCount="3" pageSize="10" timestamp="Mon, 27 Jul 2026 16:56:07 -0400" url="https://my3.my.umbc.edu/groups/gsa/posts.xml?tag=faculty">
<NewsItem contentIssues="false" id="161203" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/161203">
<Title>10 Ways to Make Your Slide Decks Accessible</Title>
<Tagline>Same principles apply to PowerPoint, Google Slides, or Canva</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Slide decks get built fast. A lecture the night before, a workshop the morning of -- we’ve all done it. Accessibility is often the first thing to slip when you're racing a deadline. But a few intentional choices, made as you build rather than after the fact, can mean the difference between a deck that works for everyone in the room and one that quietly leaves some behind.</p>
    <p>Whether you're building in PowerPoint, Google Slides, or Canva, here are ten strategies to help your next presentation reach everyone who opens it.</p>
    <p><strong>1. Start with a Built-In Template</strong></p>
    <p>A blank canvas gives you no structural head start: no heading tags, no consistent color palette, nothing for a screen reader to key off of. Starting from a real layout means accessibility is baked in before you type a word.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Choose <em>File &gt; New from Template</em> rather than starting from a blank presentation.</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Use <em>File &gt; New &gt; From template gallery</em>, including UMBC's branded templates.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> Search "presentation" in Canva's template library and start from a pre-built design rather than a blank frame.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> if you're editing an existing deck that started as a blank canvas, it's worth rebuilding on a template rather than patching structure after the fact.</p>
    <p><strong>2. Keep Each Slide to One Idea</strong></p>
    <p>A crowded slide is hard to follow for every viewer, but especially for someone using magnification or a screen reader, working through it piece by piece. One idea per slide keeps the pace manageable.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Use the Outline view to check whether your slide titles actually summarize one clear point each.</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Break dense slides into two using <em>Duplicate slide</em>, rather than shrinking text to fit everything on one.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> Use Canva's multi-page presentation flow to spread a complex idea across two slides instead of one packed layout.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> if you find yourself shrinking text to make it fit, that's usually a sign the slide needs to be split, not shrunk.</p>
    <p><strong>3. Choose Fonts and Styles That Are Easy to Read</strong></p>
    <p>Decorative fonts and heavy styling might look sharp, but they slow down every reader, not just the ones using assistive technology. Simple, consistent typography benefits everyone in the room.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Stick to sans serif fonts like Arial, Helvetica, or Calibri, and avoid ALL CAPS or excessive underlining.</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Use the built-in theme fonts rather than importing custom or script-style fonts.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> Filter Canva's font library to sans serif options, and limit each slide to one or two font pairings.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> italics and underlining both signal "link" to many users. Save them for actual links, not emphasis.</p>
    <p><strong>4. Confirm Your Slides Read in the Right Order</strong></p>
    <p>Elements dragged and repositioned during editing don't always stay in a logical reading order, so what looks correct visually can come out scrambled for a screen reader.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Open the Reading Order pane (under Review &gt; Check Accessibility) to see and adjust the sequence.</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Use Tab key navigation to click through elements in the order they'll be read aloud.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> Use the Objects panel to check the stacking/layer order of elements, since Canva reads top-to-bottom by layer.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> this check only matters if you do it last — reordering elements during design is exactly when reading order breaks.</p>
    <p><strong>5. Write Alt Text That Explains Purpose</strong></p>
    <p>An image with no alt text is simply invisible to a screen reader, and alt text that just describes what something looks like ("a graph") skips the part that actually matters: what the audience is supposed to take away from it.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Right-click an image and select <em>Edit Alt Text</em>, or mark it decorative if it adds nothing instructional.</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Right-click an image, choose <em>Alt Text</em>, and write one to two sentences describing its purpose.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> Select an image, open <em>Accessibility</em> in the side panel, and add alt text there. Canva does not auto-generate this for you.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> decorative doesn't mean "skip the alt text because you don't feel like writing it" -- it means the image truly adds nothing a viewer needs to know.</p>
    <p><strong>6. Give Complex Visuals a Text Companion</strong></p>
    <p>Dense charts, infographics, or diagrams often carry more meaning than a sentence or two of alt text can capture. A nearby caption or a linked summary fills that gap.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Add a one- to two-sentence summary in the speaker notes for any complex chart or diagram.</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Include a caption text box beneath complex visuals summarizing the key takeaway.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> Pair infographic elements with a short adjacent text block rather than relying on the visual alone.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> if you can't summarize what a visual is teaching in a sentence, that's a sign the visual needs more support, not less.</p>
    <p><strong>7. Use Descriptive Hyperlink Text</strong></p>
    <p>"Click here" tells a screen reader nothing about where a link goes. They have to click through to find out. A descriptive link tells them upfront.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Replace generic link text with the destination's actual name (e.g., "View the syllabus" instead of "here").</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Use <em>Insert &gt; Link</em> and edit the display text to be descriptive before publishing.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> When adding a link to text or a button, rename the linked text itself rather than leaving a raw URL visible.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> a good test is reading just the link text out of context. If it doesn't make sense on its own, it needs a rewrite.</p>
    <p><strong>8. Check Your Color Contrast</strong></p>
    <p>Text that blends into its background is a barrier for anyone with low vision or color blindness, and it's an easy thing to miss when you're focused on branding colors, not readability.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Run the Accessibility Checker (<em>Review tab</em>) to flag any hard-to-read text contrast automatically.</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Google Slides has no built-in checker. Export as PowerPoint or PDF and run a checker there.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> Use Canva's built-in Accessibility view or an external tool like the WebAIM Contrast Checker before finalizing colors.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> contrast that looks fine on your laptop screen can fail in a bright classroom or lecture hall. Check it under real presentation conditions when you can.</p>
    <p><strong>9. Don't Let Color Alone Carry the Meaning</strong></p>
    <p>If red means "wrong" and green means "right," a colorblind viewer has no way to tell the two apart. Pairing color with text, icons, or patterns keeps the meaning intact for everyone.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Add a label or icon next to any color-coded element instead of relying on color alone.</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Use shape or icon differences (not just fill color) to distinguish categories in charts or diagrams.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> Choose Canva chart templates that include data labels, not just color-coded legends.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> a quick way to test this is to view your slide in grayscale. If the meaning disappears, so will it for some of your audience.</p>
    <p><strong>10. Caption and Describe Any Embedded Media</strong></p>
    <p>A video or audio clip embedded mid-presentation needs the same accessibility treatment as everything else in the deck: an uncaptioned clip is a gap, not a break from reading.</p>
    <ul>
    <li>
    <p><strong>PowerPoint:</strong> Use the built-in Subtitles &amp; Captions feature under the Insert tab when recording narration.</p>
    </li>
    <li>
    <p><strong>Google Slides:</strong> Link out to a captioned version hosted in YuJa or YouTube rather than embedding raw, uncaptioned video.</p>
    </li>
    <li>
    <p><strong>Canva:</strong> Enable auto-captions on any video element added through Canva's video tools, and review them for accuracy.</p>
    </li>
    </ul>
    <p><strong>Don't forget:</strong> auto-captions are a starting point, not a finish line. Always skim them for accuracy before sharing.</p>
    <p>None of these strategies requires starting over or mastering a new tool. Most take a few extra minutes woven into work you're already doing: Picking a template instead of a blank slide, writing one real sentence of alt text instead of skipping it, checking contrast before you hit export. Start with just one or two on your next deck. Once they become a habit, the rest tend to follow.</p>
    </div>
]]>
</Body>
<Summary>Slide decks get built fast. A lecture the night before, a workshop the morning of -- we’ve all done it. Accessibility is often the first thing to slip when you're racing a deadline. But a few...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/161203/guest@my.umbc.edu/ab31f41539b65f9f5063efd55095e65f/api/pixel</TrackingUrl>
<Tag>canva</Tag>
<Tag>digital-accessibility</Tag>
<Tag>faculty</Tag>
<Tag>google-slides</Tag>
<Tag>powerpoint</Tag>
<Tag>presentations</Tag>
<Tag>staff</Tag>
<Tag>students</Tag>
<Group token="doit">Division of Information Technology (DoIT)</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/doit</GroupUrl>
<AvatarUrl>https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/original.JPG?1727453227</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/large.png?1727453227</AvatarUrl>
<AvatarUrl size="medium">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/medium.png?1727453227</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/small.png?1727453227</AvatarUrl>
<AvatarUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxsmall.png?1727453227</AvatarUrl>
<Sponsor>Division of Information Technology (DoIT)</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/161/203/965afcc04172f517e579b1d4b0a1b9b3/xxlarge.jpg?1784579753</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/161/203/965afcc04172f517e579b1d4b0a1b9b3/xlarge.jpg?1784579753</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/203/965afcc04172f517e579b1d4b0a1b9b3/large.jpg?1784579753</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/203/965afcc04172f517e579b1d4b0a1b9b3/medium.jpg?1784579753</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/203/965afcc04172f517e579b1d4b0a1b9b3/small.jpg?1784579753</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/161/203/965afcc04172f517e579b1d4b0a1b9b3/xsmall.jpg?1784579753</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/161/203/965afcc04172f517e579b1d4b0a1b9b3/xxsmall.jpg?1784579753</ThumbnailUrl>
<ThumbnailAltText>A human figure with outstretched arms inside a circle of two curved arrows, suggesting movement. Below the figure are two words: digital accessibility.</ThumbnailAltText>
<PawCount>7</PawCount>
<CommentCount>1</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Tue, 21 Jul 2026 10:30:00 -0400</PostedAt>
<EditAt>Tue, 21 Jul 2026 10:35:13 -0400</EditAt>
</NewsItem>

<NewsItem contentIssues="false" id="161092" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/161092">
<Title>5 Steps to More Accessible Google Docs</Title>
<Tagline>Start building inclusive Google Docs for all readers today</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Imagine a student opening a Google Docs syllabus with a screen reader. They expect to easily skip from section to section. Instead, they hit a wall of text. Why? Because simply making text bold and underlined doesn't turn it into a real header and assistive technology can't read it as one.</p>
    <p>Because Google Docs live entirely in a web browser, building an inclusive document requires a slightly different approach than working in traditional desktop word processors. Google Workspace’s native tools make it easy to build in accessibility from the start, rather than fixing it after the fact.</p>
    <p>Here are five steps to create inclusive Google Docs, from the first keystroke to the final share.</p>
    <h4><strong>Step 1: Mapping the Foundation with Paragraph Styles</strong></h4>
    <p>When building a document, it is tempting to use the font size, bold, and underline buttons to manually create visual section headers. However, screen readers cannot use visual styling to understand the hierarchy of a page. Instead, they rely on an invisible, structural blueprint.</p>
    <p>To build this structure properly, swap manual formatting for the <strong>Styles</strong> menu:</p>
    <ol>
    <li>Highlight your section title and click the <strong>Styles</strong> dropdown in the top toolbar (it usually defaults to "Normal text").</li>
    <li>Assign <strong>Title</strong> for your main topic, <strong>Heading 1</strong> for major sections, and <strong>Heading 2</strong> for subsections.</li>
    </ol>
    <p><strong>The Google Advantage:</strong> Using native headings automatically populates the left-hand document outline panel (View → Show outline). Because this outline serves as a live, interactive map, it doesn't just help assistive tech users jump between sections—it allows <em>everyone</em> collaborating on the document to navigate massive files with a single click.</p>
    <h4><strong>Step 2: Writing and Linking via "Smart Chips"</strong></h4>
    <p>Pasting raw, lengthy URLs into a shared document creates a clunky visual layout and an incredibly frustrating experience for screen reader users, who have to listen to every single character read aloud. On the flip side, vague text like "click here" lacks critical context when scanned in isolation.</p>
    <ul>
    <li>
    <strong>Instead of:</strong> “For the library database, click here.”</li>
    <li>
    <strong>Write:</strong> “Search the Library Database directly.”</li>
    </ul>
    <p><strong>The Google Advantage:</strong> Google Docs offers a cloud-native fix for messy links. When you paste a URL into a document, immediately press the “Tab" key when prompted. Google will automatically convert the raw web address into a clean <strong>Smart Chip</strong> or a descriptive preview title pulled directly from the destination page's metadata.</p>
    <h4><strong>Step 3: Handling Visuals and Decorative Content</strong></h4>
    <p>Images, charts, and diagrams require text alternatives (Alt Text) so screen readers can describe the images in the Documents. </p>
    <p>To add this in Google Docs:</p>
    <ol>
    <li>Right-click the image and select <strong>Alt text</strong> (or use the shortcut Ctrl + Alt + Y / Cmd + Option + Y).</li>
    <li>Type your summary strictly in the <strong>Description</strong> box, focusing on <em>why</em> the image matters to the document. You can leave the "Title" box blank.</li>
    </ol>
    <p><strong>The Google Disadvantage:</strong> Unlike desktop processors, Google Docs does not feature a native "Mark as decorative" checkbox for purely aesthetic graphics (like accent lines or background shapes). To work around this limitation without confusing assistive technologies, either omit purely decorative images entirely, or explicitly type "Decorative image" in the description box so a screen reader user knows they aren't missing out on critical content.</p>
    <h4><strong>Step 4: Creating Lists</strong></h4>
    <p>A hand-type dash or asterisk might look like a list on screen, but screen readers have no way of knowing it’s meant to be one. Instead, they announce each line as a separate, disconnected sentences, leaving the listener with no sense of how many items exist or where they are in a sequence.</p>
    <ul>
    <li>
    <strong>Use numbered lists when sequence matters</strong>, such as steps in an assignment or the order of operations in a grading rubric.</li>
    <li>
    <strong>Use bulleted lists when items carry equal weight</strong>, like a set of recommended readings or optional resources.</li>
    </ul>
    <p><strong>The Google Advantage:</strong> Applying a native list format (Format → Bullets &amp; numbering) tells assistive technology exactly how many items are in the list and which one is currently being read, while also letting collaborators reorder or indent items automatically, without retyping symbols by hand.</p>
    <h4><strong>Step 5: Maintaining Simple Typography</strong></h4>
    <p>Decorative or script fonts, along with fully justified paragraphs, can be difficult for low-vision or dyslexic readers to track, since justification stretches spacing unevenly and creates awkward gaps between words. Standard, legible fonts paired with left-aligned text keep spacing consistent and predictable for every reader.</p>
    <ul>
    <li>
    <strong>Keep body text at 11pt or larger</strong>, since smaller sizes force low-vision readers to rely entirely on browser zoom.</li>
    <li>
    <strong>Reserve underlining for hyperlinks only</strong> since underlined body text can be mistaken for a broken or dead link.</li>
    </ul>
    <p><strong>The Google Advantage:</strong> Selecting "More fonts" from the font dropdown lets you preview and filter Google's full font library before applying it document-wide, making it easy to swap in an accessible typeface consistently across the whole file.</p>
    <p><strong>Remember:</strong> The biggest difference between Google Docs and desktop alternatives is the ecosystem: Google Docs does not feature a native, built-in "Check Accessibility" button in the toolbar. Therefore, you must review your work for accessibility before selecting the “Share” button.</p>
    </div>
]]>
</Body>
<Summary>Imagine a student opening a Google Docs syllabus with a screen reader. They expect to easily skip from section to section. Instead, they hit a wall of text. Why? Because simply making text bold...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/161092/guest@my.umbc.edu/4c31df49fbf183e8810b871843cebdf0/api/pixel</TrackingUrl>
<Tag>digital-accessibility</Tag>
<Tag>faculty</Tag>
<Tag>google-docs</Tag>
<Tag>staff</Tag>
<Tag>students</Tag>
<Group token="doit">Division of Information Technology (DoIT)</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/doit</GroupUrl>
<AvatarUrl>https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/original.JPG?1727453227</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/large.png?1727453227</AvatarUrl>
<AvatarUrl size="medium">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/medium.png?1727453227</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/small.png?1727453227</AvatarUrl>
<AvatarUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxsmall.png?1727453227</AvatarUrl>
<Sponsor>Division of Information Technology (DoIT)</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/161/092/b5b9709a1e61d34494762386677031d0/xxlarge.jpg?1784034898</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/161/092/b5b9709a1e61d34494762386677031d0/xlarge.jpg?1784034898</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/092/b5b9709a1e61d34494762386677031d0/large.jpg?1784034898</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/092/b5b9709a1e61d34494762386677031d0/medium.jpg?1784034898</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/161/092/b5b9709a1e61d34494762386677031d0/small.jpg?1784034898</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/161/092/b5b9709a1e61d34494762386677031d0/xsmall.jpg?1784034898</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/161/092/b5b9709a1e61d34494762386677031d0/xxsmall.jpg?1784034898</ThumbnailUrl>
<ThumbnailAltText>A human figure with outstretched arms inside a circle of two curved arrows, suggesting movement. Below the figure are two words: digital accessibility.</ThumbnailAltText>
<PawCount>4</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Tue, 14 Jul 2026 10:50:48 -0400</PostedAt>
</NewsItem>

<NewsItem contentIssues="false" id="160956" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/160956">
<Title>5 Tips for Accessible Word Documents</Title>
<Tagline>Small changes, big impact for everyone.</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Microsoft Word is one of the most common tools used for creating flyers, handouts, syllabi, readings, and assignments. It’s also one of the most common sources of accessibility problems in Blackboard courses or websites. The good news: <a href="https://support.microsoft.com/en-US/accessibility/word/make-your-word-documents-accessible-to-people-with-disabilities" rel="nofollow external" class="bo">Word has built-in tools</a> that can make it easy to create documents that work for every faculty, staff, and student; including those who rely on screen readers or other assistive technologies. These 5 tips will help you build accessibility into your Word documents from the start, no special expertise required.</p>
    <h3><strong>1. Use Heading Styles</strong></h3>
    <p>One of the most impactful things you can do for document accessibility is also one of the simplest: use Word’s built-in heading styles instead of manually increasing font size or bolding text to create section titles. Heading styles already give your document structure that screen readers can navigate, such as a table of contents for assistive technology. Think of headings as signposts. Screen reader users can jump from heading to heading the same way sighted readers scan a page.</p>
    <ul>
    <li>Find heading styles in the Home tab under “Styles.”</li>
    <li>Apply Heading 1 for your main title, Heading 2 for major sections, and Heading 3 for subsections.</li>
    <li>Avoid skipping levels, don’t jump from Heading 1 directly to Heading 3.</li>
    </ul>
    <h3><strong>2. Write Descriptive Link Text</strong></h3>
    <p>When you insert a hyperlink into a Word document, the link text is what gets read aloud to screen reader users. Vague phrases like “click here,” “read more,” or a raw URL give no information about where the link leads. Descriptive link text also helps users who are scanning a document quickly. (Refer to <a href="https://my3.my.umbc.edu/groups/doit/posts/160632" rel="nofollow external" class="bo">5 Tips for Creating Clear and Accessible Links</a> for more information.)</p>
    <ul>
    <li>Instead of: “For the course schedule, click here.”</li>
    <li>Write: “Download the course schedule (PDF).”</li>
    </ul>
    <h3><strong>3. Add Alt Text to Images</strong></h3>
    <p>Any image in your Word document that conveys meaning (e.g., a diagram, a chart, a photograph), does need an alternative text; so students using screen readers can access the information it contains. If you’re unsure how to describe a complex image, <a href="https://umbc.atlassian.net/wiki/x/FoAgNQ" rel="nofollow external" class="bo">a generative AI tool</a> can generate a starting point. Be sure to review and revise before saving it.</p>
    <ul>
    <li>Right-click on an image and select “Edit Alt Text.”</li>
    <li>Write a concise description focused on the image’s purpose, not just its appearance.</li>
    <li>For purely decorative images, check the “Mark as decorative” box in the alt text panel.</li>
    </ul>
    <h3><strong>4. Make Tables Accessible</strong></h3>
    <p>Tables are a common accessibility problem in Word documents, especially when they’re used for layout rather than data. A table designed to organize visual information can become a challenge for a screen reader user to follow if it’s not structured correctly.</p>
    <ul>
    <li>Use tables for data, not for page layout.</li>
    <li>Add a table title or brief description above the table so students know what it contains.</li>
    <li>Mark your header row: right-click the top row → Table Properties → Row → check “Repeat as header row at the top of each page.”</li>
    <li>Avoid merged or split cells. Keep tables simple. </li>
    </ul>
    <h3><strong>5. Run the Accessibility Checker</strong></h3>
    <p>Word has a built-in Accessibility Checker that scans your document and flags any potential problems to fix before you save and share it with students. It can quickly identify any issues you might have missed.</p>
    <ul>
    <li>Go to Review → Check Accessibility.</li>
    <li>The checker will flag errors (must fix), warnings (should fix), and tips (consider fixing).</li>
    <li>Click on each flagged item for a plain-language explanation and apply the suggested fix.</li>
    </ul>
    <p>Running the Accessibility Checker in Microsoft Word before uploading a file to Sites or Blackboard is one of the simplest habits you can build into your document workflow. It’s also one of the fastest ways to improve your Accessibility score.</p>
    
    <p>For more information, view UMBC’s Digital Accessibility’s site on <a href="https://accessibility.umbc.edu/digital-accessibility/accessible-documents-presentations/" rel="nofollow external" class="bo">Accessible Documents &amp; Presentations</a> on how to make your word documents accessible.</p>
    <h3><strong>Coming Soon: Beyond PDFs</strong></h3>
    <p>Why Use PDFs at All? While this article focuses on making your Word documents accessible, we often get asked why PDFs are so common if they are harder to remediate. In an upcoming article, we’ll dive into the question of the PDF Dilemma and share why sharing your original Word file is often the preferred choice for accessibility. Keep an eye out for that deep dive soon!</p>
    </div>
]]>
</Body>
<Summary>Microsoft Word is one of the most common tools used for creating flyers, handouts, syllabi, readings, and assignments. It’s also one of the most common sources of accessibility problems in...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/160956/guest@my.umbc.edu/33fbb614796ac04ca55e7bf7bf0083cc/api/pixel</TrackingUrl>
<Tag>crutchfield</Tag>
<Tag>digital-accessibility</Tag>
<Tag>faculty</Tag>
<Tag>staff</Tag>
<Tag>students</Tag>
<Tag>word-documents</Tag>
<Group token="doit">Division of Information Technology (DoIT)</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/doit</GroupUrl>
<AvatarUrl>https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/original.JPG?1727453227</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/large.png?1727453227</AvatarUrl>
<AvatarUrl size="medium">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/medium.png?1727453227</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/small.png?1727453227</AvatarUrl>
<AvatarUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxsmall.png?1727453227</AvatarUrl>
<Sponsor>Division of Information Technology (DoIT)</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/956/cc844df109e755a4eb30b38b01bd7774/xxlarge.jpg?1783344713</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/160/956/cc844df109e755a4eb30b38b01bd7774/xlarge.jpg?1783344713</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/956/cc844df109e755a4eb30b38b01bd7774/large.jpg?1783344713</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/956/cc844df109e755a4eb30b38b01bd7774/medium.jpg?1783344713</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/956/cc844df109e755a4eb30b38b01bd7774/small.jpg?1783344713</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/956/cc844df109e755a4eb30b38b01bd7774/xsmall.jpg?1783344713</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/956/cc844df109e755a4eb30b38b01bd7774/xxsmall.jpg?1783344713</ThumbnailUrl>
<ThumbnailAltText>A human figure with outstretched arms inside a circle of two curved arrows, suggesting movement. Below the figure are two words: digital accessibility.</ThumbnailAltText>
<PawCount>6</PawCount>
<CommentCount>1</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Tue, 07 Jul 2026 12:15:00 -0400</PostedAt>
</NewsItem>

<NewsItem contentIssues="false" id="160866" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/160866">
<Title>3 Tips for Making Your Synchronous Meetings Accessible</Title>
<Tagline>Accessible meetings benefit every participant involved.</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Let’s enhance meeting productivity for all attendees! Whether you are hosting a departmental meeting, conducting a 1:1 check-in, or moderating a large-scale event,  the organization and execution of that meeting impacts everyone’s ability to engage meaningfully. Attendees with hearing or vision impairments, audio processing differences, or utilizing assistive technology will benefit if you can reduce barriers that impact their ability to participate. </p>
    <p>Here are 3 tips to ensure your synchronous meetings are accessible. Applicable to both in-person meetings and virtual sessions, these tips focus on UMBC’s primary platforms: <a href="https://umbc.atlassian.net/wiki/spaces/faq/pages/522944514/Google+Meet?search_id=7f12fea9-4d6f-4349-9765-95ce15bfedc4&amp;additional_analytics=queryHash---e6f7f04f5a43e53f4df979478918ca1c962f1b93b9b5cce6690290d1748780ff" rel="nofollow external" class="bo">Google Meet</a>, <a href="https://umbc.atlassian.net/wiki/spaces/faq/pages/30766726/Getting+Started+with+Microsoft+Teams?search_id=7f12fea9-4d6f-4349-9765-95ce15bfedc4&amp;additional_analytics=queryHash---4f8c0cbb86f180150642480744dcd76e0caa2b4a9ae315c5b6b7cb918d1f8b24" rel="nofollow external" class="bo">Microsoft Teams</a>, and <a href="https://umbc.atlassian.net/wiki/x/jjzVAQ" rel="nofollow external" class="bo">Webex</a>.</p>
    <h3><strong>1. Coordinate and Share Materials</strong></h3>
    <p><em>All information should be easy to perceive and navigate throughout the entire meeting.</em></p>
    <ul>
    <li>
    <p><strong>Pre-Meeting: </strong>Provide agendas and supporting files at least 24 hours beforehand to accommodate screen reader users and those who desire or require ample time to prepare.  Use your calendar description to include or share text-based agendas and favor structured documents over PDFs.</p>
    </li>
    <li>
    <p><strong>During the Meeting: </strong>Ensure text is at least 18 pt (sans serif) for clarity across devices. Narrate visual elements -- like describing specific data points on a chart -- rather than just reading text. Encourage participants to share their screens during collaborative work, if appropriate, for improved compatibility with assistive software.</p>
    </li>
    <li>
    <p><strong>Post-Meeting: </strong>Provide notes in structured formats rather than long-form, dense and possibly inaccessible emails. Review and fix errors in automated transcripts or captions before distributing recordings. Clearly define and label all deadlines and action items.</p>
    </li>
    </ul>
    <h3><strong>2. Use Real-Time Captioning</strong></h3>
    <p><em>Providing a visual representation of speech is a fundamental accommodation.</em></p>
    <p>Providing real-time captions allows a diverse range of participants to engage in the meeting meaningfully. While live text displays are essential for individuals who are deaf or hard of hearing, they also offer vital support for non-native speakers, those in high-noise environments, and attendees who utilize visual reinforcement to process information more effectively.</p>
    <ul>
    <li>
    <p><strong>Google Meet: </strong>Toggle the <a href="https://support.google.com/meet/answer/15077804?hl=en&amp;co=GENIE.Platform%3DDesktop" rel="nofollow external" class="bo"><em>Captions</em></a> feature in settings for immediate text display.</p>
    </li>
    <li>
    <p><strong>Microsoft Teams: </strong>Enable live captions via <a href="https://support.microsoft.com/en-us/teams/meetings/use-live-captions-in-microsoft-teams-meetings" rel="nofollow external" class="bo"><em>Language and speech</em></a> in the ellipsis menu.</p>
    </li>
    <li>
    <p><strong>Webex: </strong>Use the <a href="https://help.webex.com/en-us/article/lzi8h2/Show-or-hide-closed-captions-during-a-Webex-meeting-or-webinar" rel="nofollow external" class="bo"><em>Accessibility</em> or <em>Closed captions</em></a> options. </p>
    </li>
    </ul>
    <h3><strong>3. Enhance Audio Quality</strong></h3>
    <p><em>Using clear audio helps generate reliable transcripts.</em></p>
    <ul>
    <li>
    <p><strong>Prioritize Quality: </strong>Use a headset or external microphone instead of built-in speakers for better speech recognition and transcription accuracy. Follow microphone etiquette by muting yourself when not speaking to reduce noise that will hinder captioning.</p>
    </li>
    <li>
    <p><strong>Control Speaking Order: </strong>Speak clearly and at a moderate pace, ensuring only one person speaks at a time. Overlapping speech confuses transcription engines and makes it difficult for participants using hearing aids to follow.</p>
    </li>
    <li>
    <p><strong>Optimize Your Space: </strong>In <a href="https://umbc.atlassian.net/wiki/x/_l3VAQ" rel="nofollow external" class="bo">hyflex</a> environments, utilize the installed room microphones and speakers rather than your laptop’s built-in audio. These integrated systems are designed to pick up voices from across the room, ensuring that remote participants can clearly hear in-person contributions<strong>.</strong> Remember to face the audience to provide essential visual cues for lip-readers.</p>
    </li>
    </ul>
    <p>Accessible meetings take a little more time and intention to plan, yet you can create and facilitate a more equitable meeting where everyone can engage and contribute their full potential.</p>
    </div>
]]>
</Body>
<Summary>Let’s enhance meeting productivity for all attendees! Whether you are hosting a departmental meeting, conducting a 1:1 check-in, or moderating a large-scale event,  the organization and execution...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/160866/guest@my.umbc.edu/c7b51b018b50ed8ba85f345e7902e2f7/api/pixel</TrackingUrl>
<Tag>captions</Tag>
<Tag>crutchfield</Tag>
<Tag>digital-accessibility</Tag>
<Tag>faculty</Tag>
<Tag>google-meet</Tag>
<Tag>meetings</Tag>
<Tag>ms-teams</Tag>
<Tag>staff</Tag>
<Tag>students</Tag>
<Tag>webex</Tag>
<Group token="doit">Division of Information Technology (DoIT)</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/doit</GroupUrl>
<AvatarUrl>https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/original.JPG?1727453227</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/large.png?1727453227</AvatarUrl>
<AvatarUrl size="medium">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/medium.png?1727453227</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/small.png?1727453227</AvatarUrl>
<AvatarUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxsmall.png?1727453227</AvatarUrl>
<Sponsor>Division of Information Technology (DoIT)</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/866/30a56f1094aab5fbd1b80bba59d7919f/xxlarge.jpg?1782748309</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/866/30a56f1094aab5fbd1b80bba59d7919f/xlarge.jpg?1782748309</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/866/30a56f1094aab5fbd1b80bba59d7919f/large.jpg?1782748309</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/866/30a56f1094aab5fbd1b80bba59d7919f/medium.jpg?1782748309</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/866/30a56f1094aab5fbd1b80bba59d7919f/small.jpg?1782748309</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/866/30a56f1094aab5fbd1b80bba59d7919f/xsmall.jpg?1782748309</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/160/866/30a56f1094aab5fbd1b80bba59d7919f/xxsmall.jpg?1782748309</ThumbnailUrl>
<ThumbnailAltText>A human figure with outstretched arms inside a circle of two curved arrows, suggesting movement. Below the figure are two words: digital accessibility.</ThumbnailAltText>
<PawCount>8</PawCount>
<CommentCount>1</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Tue, 30 Jun 2026 12:00:00 -0400</PostedAt>
<EditAt>Thu, 02 Jul 2026 15:31:12 -0400</EditAt>
</NewsItem>

<NewsItem contentIssues="false" id="160812" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/160812">
<Title>5 Tips for Posting Accessible Images &amp; Stories to Social Media</Title>
<Tagline>Build social media habits that include everyone.</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Social media is one of the most powerful tools departments use to share news, celebrate achievements, and build community. It’s also one of the most consistently inaccessible corners of institutional communication. The good news is that most major platforms now have built-in accessibility features, and the habits that make social media accessible also tend to make it more engaging for everyone.</p>
    <p>Note: The availability of some accessibility features depends on whether you are using the mobile application or a desktop/browser.</p>
    <h3><strong>1. Write Alt Text for Every Image You Post</strong></h3>
    <p>Alt text on social media works the same way it does everywhere else: it describes an image to someone who cannot see it. Write a descriptive sentence about what the image shows and why you’re posting it. </p>
    <p>Most major platforms now support alt text -- you just have to use it. </p>
    <ul>
    <li>
    <p><a href="https://www.facebook.com/help/214124458607871/" rel="nofollow external" class="bo">On Facebook</a>: When composing a post with an image, click the three dots (…) on the photo and select “Edit alt text.” </p>
    </li>
    <li>
    <p><a href="https://help.instagram.com/503708446705527/?helpref=uf_share" rel="nofollow external" class="bo">On Instagram</a>: Before posting, tap “Advanced settings” at the bottom of the caption screen and select “Write alt text.”</p>
    </li>
    <li>
    <p><a href="https://www.linkedin.com/help/linkedin/answer/a519856" rel="nofollow external" class="bo">On LinkedIn</a>: After uploading an image, look for the “Alt text” option before publishing.</p>
    </li>
    <li>
    <p><a href="https://help.x.com/en/using-x/add-image-descriptions" rel="nofollow external" class="bo">On X</a>: Tap the image after uploading and select “Add description” before posting.</p>
    </li>
    </ul>
    <p>Note: If a platform doesn't support native alt text (like TikTok), write a brief visual description directly at the bottom of your post caption.</p>
    <h3><strong>2. Caption Your Videos</strong></h3>
    <p>Video content without captions excludes users who are deaf or hard of hearing, and also anyone watching without sound, which is a significant portion of social media users. Most platforms generate auto-captions.</p>
    <ul>
    <li>
    <p>On <a href="https://help.instagram.com/3544819209117630/?helpref=uf_share" rel="nofollow external" class="bo">Instagram</a> and <a href="https://www.facebook.com/help/509746615868430/?helpref=uf_share" rel="nofollow external" class="bo">Facebook</a>: Auto-captions are generated for Reels and videos. </p>
    </li>
    <li>
    <p>On <a href="https://www.linkedin.com/help/linkedin/answer/a1327025" rel="nofollow external" class="bo">LinkedIn</a>: You can generate captions, but uploading a caption file (SRT format) when posting a video will be the most accurate.</p>
    </li>
    <li>
    <p>On <a href="https://support.google.com/youtube/answer/2734796?hl=en" rel="nofollow external" class="bo">YouTube</a>: Auto-captions are available, and can be corrected via YouTube Studio.</p>
    </li>
    </ul>
    <p>Consider burning captions directly into the short-form videos (e.g., TikTok-style content) before posting, so they appear for all platforms. Regardless of how you add captions to your social media videos, they should be accurate for your audience.</p>
    <h3><strong>3. Provide Essential Text Outside of Images</strong></h3>
    <p>Graphic design tools make it easy to create visually striking images with text overlaid for event announcements, quotes, and infographic-style posts. But text embedded in an image cannot be read by a screen reader, cannot be resized by users with low vision, and is not searchable.</p>
    <ul>
    <li>
    <p>If your graphic includes essential information (event name, date, location, deadline), repeat that information in the post caption or body text so users with screen readers will have access to the same information.</p>
    </li>
    <li>
    <p>Use high-contrast text on image graphics. Light text on a light background or dark text on a dark background is hard to read for everyone, not just screen reader users. If you <a href="https://webaim.org/resources/contrastchecker/" rel="nofollow external" class="bo">use a color contrast checker</a>, aim for a ratio of at least 4:5:1.</p>
    </li>
    </ul>
    <h3><strong>4. Use CamelCase for Hashtags</strong></h3>
    <p>Screen readers rely on capital letters to distinguish individual words. Without capital letters, hashtags are read aloud by screen readers as a single string of text: #digitalaccess becomes “digitalaccess” becomes one undifferentiated word. CamelCase (capitalizing the first letter of each word in a hashtag) allows screen readers to identify and announce each word separately.</p>
    <ul>
    <li>
    <p>Write #DigitalAccessibility instead of #digitalaccessibility.</p>
    </li>
    <li>
    <p>Screen readers translate “umbc” to “uhm-buck” when they read out loud. If you want accuracy, use hyphens between the letters: “U-M-B-C”</p>
    </li>
    </ul>
    <p>This is a small habit that makes hashtags more readable for everyone -- including sighted users scanning a post.</p>
    <h3><strong>5. Write and Format for an Inclusive Audience</strong></h3>
    <p>Consider all of your audience when preparing and publishing your social media posts. </p>
    <ul>
    <li>
    <p>Keep emojis to the end of your posts rather than bullet points or in the middle of your sentence. Screen readers will read aloud the exact text description, which will break up the flow of your post.</p>
    </li>
    <li>Avoid using external font generators to create styled text on platforms like Instagram and X. Words written in these fonts cannot be read by screen readers, and many are difficult to read by visual users as well.</li>
    <li>
    <p>Write with clear and simple language, and avoid unnecessary jargon and idioms to support users with cognitive or language-processing disabilities.</p>
    </li>
    <li>
    <p>When adding links to posts and bios, include context and clear labels so your readers know where the link leads. For example, “Learn more about our summer accessibility training series” or “Request support” instead of a short URL.</p>
    </li>
    </ul>
    <p>Social media accessibility is an ongoing practice, not a one-time fix. Building these habits into your regular posting workflow means every post you share is reaching your full audience.</p>
    <p>---</p>
    <p><em>Tips and strategies adapted from <a href="https://www.youtube.com/watch?v=Dd00U8elzm0" rel="nofollow external" class="bo">“Accessible Social Media” training</a> (2026), prepared by the <strong>Maryland Assistive Technology Program</strong>, and <a href="https://social.umbc.edu/resources-and-guidelines/social-media-accessibility-guidelines/" rel="nofollow external" class="bo">"Social Media Accessibility Guidelines"</a> (n.d.), prepared by UMBC's <strong>University Communications &amp; Marketing</strong> team.</em></p>
    </div>
]]>
</Body>
<Summary>Social media is one of the most powerful tools departments use to share news, celebrate achievements, and build community. It’s also one of the most consistently inaccessible corners of...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/160812/guest@my.umbc.edu/d57e5696714e1ea3a479aca768f6286f/api/pixel</TrackingUrl>
<Tag>digital-accessibility</Tag>
<Tag>faculty</Tag>
<Tag>social-media</Tag>
<Tag>staff</Tag>
<Tag>students</Tag>
<Group token="doit">Division of Information Technology (DoIT)</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/doit</GroupUrl>
<AvatarUrl>https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/original.JPG?1727453227</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/large.png?1727453227</AvatarUrl>
<AvatarUrl size="medium">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/medium.png?1727453227</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/small.png?1727453227</AvatarUrl>
<AvatarUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxsmall.png?1727453227</AvatarUrl>
<Sponsor>Division of Information Technology (DoIT)</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/812/6c9ec8685957656b5f1311c71f545fa2/xxlarge.jpg?1782231451</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/812/6c9ec8685957656b5f1311c71f545fa2/xlarge.jpg?1782231451</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/812/6c9ec8685957656b5f1311c71f545fa2/large.jpg?1782231451</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/160/812/6c9ec8685957656b5f1311c71f545fa2/medium.jpg?1782231451</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/812/6c9ec8685957656b5f1311c71f545fa2/small.jpg?1782231451</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/812/6c9ec8685957656b5f1311c71f545fa2/xsmall.jpg?1782231451</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/812/6c9ec8685957656b5f1311c71f545fa2/xxsmall.jpg?1782231451</ThumbnailUrl>
<ThumbnailAltText>A human figure with outstretched arms inside a circle of two curved arrows, suggesting movement. Below the figure are two words: digital accessibility.</ThumbnailAltText>
<PawCount>7</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Tue, 23 Jun 2026 15:27:36 -0400</PostedAt>
</NewsItem>

<NewsItem contentIssues="false" id="160654" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/160654">
<Title>7 Accessible Practices for Creating and Sending Email</Title>
<Tagline>Accessibility starts before you hit send.</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Email is one of the most universal communication tools we have at UMBC, and one of the most commonly overlooked places where accessibility breaks down. Whether you’re sending a department update, a meeting invitation, or a campus-wide announcement, the way you format your email affects whether every recipient can actually read and understand it. For users who use screen readers, have low vision, or rely on assistive technology, a poorly formatted email isn’t just inconvenient -- it’s a barrier. The good news: accessible emails are also clearer, better organized, and easier for everyone to read.</p>
    <p>These tips apply to Gmail, UMBC’s primary email platform, but the principles carry across any email client.</p>
    <h3><strong>1. Write a Descriptive, Meaningful Subject Line</strong></h3>
    <p>Your subject line is the first thing a screen reader announces. Vague subject lines like “FYI,” “Update,” or “Important” don’t tell the recipient what to expect or how urgently to act.</p>
    <ul>
    <li>
    <p>Be specific: “Staff Meeting Agenda – Thursday, July 10” is more useful than “Agenda.”</p>
    </li>
    <li>
    <p>Skip the emoji in subject lines. Screen readers read the emoji name aloud (e.g., “check mark button” and this can bury your actual message.</p>
    </li>
    <li>
    <p>Avoid all caps. Screen readers may spell out letters individually, and all caps are harder to read visually. </p>
    </li>
    <li>
    <p>Front-load the most important information: “Action Required: Submit Your Training Confirmation by Friday.”</p>
    </li>
    </ul>
    <h3><strong>2. Keep Your Structure Simple and Scannable</strong></h3>
    <p>Long blocks of unbroken text are hard for everyone to read, and especially difficult for screen reader users who need to navigate content linearly. Use structure to make your emails easier to process.</p>
    <ul>
    <li>
    <p>Use short paragraphs. One idea per paragraph is a good rule of thumb.</p>
    </li>
    <li>
    <p>Use real lists (Gmail’s bulleted or numbered list buttons in the formatting toolbar) rather than typing dashes or asterisks manually.</p>
    </li>
    <li>
    <p>If your email covers multiple topics, use Gmail’s bold text to create visual section breaks, but use it sparingly so emphasis stays meaningful.</p>
    </li>
    <li>
    <p>Avoid using tables for layout in email. Table rendering is inconsistent across email clients, and tables can be confusing for screen reader users.</p>
    </li>
    </ul>
    <h3><strong>3. Make Your Links Descriptive</strong></h3>
    <p>Links in emails are frequently formatted as raw URLs or vague phrases. Both create problems for screen reader users, who often navigate emails by jumping between links.</p>
    <ul>
    <li>
    <p>Instead of “Click Here” or “Please register using this link: [long link]” you should write: “Register for the July accessibility workshop.” Then embed the link to the descriptive phrase. </p>
    <ul>
    <li>
    <p>In Gmail: Highlight the text you want to link, press Ctrl+K (or Cmd+K on Mac), and paste the URL. The visible text, not the URL, becomes the link.</p>
    </li>
    </ul>
    </li>
    <li>
    <p>Avoid linking entire sentences. Link only the meaningful phrase.</p>
    </li>
    </ul>
    <h3><strong>4. Use Color and Formatting Thoughtfully</strong></h3>
    <p>Color can add visual emphasis, but it should never be the only way you communicate information. Recipients with color blindness or low vision may not perceive color differences the way you intend.</p>
    <ul>
    <li>
    <p>Don’t rely on color alone to indicate importance. Pair color with bold, italics, or explicit language (“Note:” or “Reminder:”).</p>
    </li>
    <li>
    <p>Ensure text color has sufficient contrast against the background. Gmail’s default black text on white background is already contrast-compliant. Avoid overriding it with light gray or other low-contrast colors.</p>
    </li>
    <li>
    <p>Use bold and italics for emphasis sparingly. Excessive formatting is as hard to read as none.</p>
    </li>
    </ul>
    <h3><strong>5. Add Alt Text to Images in Gmail</strong></h3>
    <p>If you include images in your email -- for example, logos, banners, charts, or photos -- they need alternative text so recipients using screen readers understand what the image conveys.</p>
    <ul>
    <li>
    <p>In Gmail: Insert an image, then click it and select “Edit alt text.”</p>
    </li>
    <li>
    <p>Write a brief description of what the image communicates, not just what it looks like.</p>
    </li>
    <li>
    <p>If the image is purely decorative (a banner or divider), consider whether it’s necessary to use it at all. Decorative images in email can slow load times and add clutter.</p>
    </li>
    <li>
    <p>Never embed essential information, especially text like event information, only in an image. If the image doesn’t load or can’t be read, that information disappears.</p>
    </li>
    </ul>
    <h3><strong>6. Send Attachments That Are Actually Accessible</strong></h3>
    <p>An email can be well-formatted, while the file attached to it is not. Before attaching a document, take a moment to confirm it will work for every recipient.</p>
    <ul>
    <li>
    <p>Run the Accessibility Checker in Word or PowerPoint (Review &gt; Check Accessibility) before attaching. It flags missing alt text, poor color contrast, and other common issues.</p>
    </li>
    <li>
    <p>For PDFs, export from the source file rather than scanning a paper document. Scanned PDFs are images of text, not readable text, and are inaccessible to screen readers by default.</p>
    </li>
    <li>
    <p>Check that your document has a logical structure: real headings, readable lists, and meaningful link text. The same principles that apply to your email apply to what you attach to it.</p>
    </li>
    </ul>
    <p>When in doubt, put the information in the email body instead. The most accessible attachment is one that doesn’t need to exist.</p>
    <h3><strong>7. Test Before You Send</strong></h3>
    <p>Before sending a high-stakes email to a large group, take 60 seconds to review it with accessibility in mind:</p>
    <ul>
    <li>
    <p>Read your subject line out loud. Is it clear without any surrounding context?</p>
    </li>
    <li>
    <p>Read your link text out loud. Does each link tell you where it goes?</p>
    </li>
    <li>
    <p>Try removing all color from your email mentally. Does it still make sense?</p>
    </li>
    <li>
    <p>If you’ve included an image, check that it has alt text.</p>
    </li>
    </ul>
    <p>Accessible email takes only a little more time to write, and makes a significant difference for the colleagues and community members who receive it.</p>
    </div>
]]>
</Body>
<Summary>Email is one of the most universal communication tools we have at UMBC, and one of the most commonly overlooked places where accessibility breaks down. Whether you’re sending a department update,...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/160654/guest@my.umbc.edu/1367a6bff94a9d6ac4d5d5bb96cede25/api/pixel</TrackingUrl>
<Tag>accessible-email</Tag>
<Tag>blackboard</Tag>
<Tag>digital-accessibility</Tag>
<Tag>faculty</Tag>
<Tag>staff</Tag>
<Tag>students</Tag>
<Group token="doit">Division of Information Technology (DoIT)</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/doit</GroupUrl>
<AvatarUrl>https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/original.JPG?1727453227</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/large.png?1727453227</AvatarUrl>
<AvatarUrl size="medium">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/medium.png?1727453227</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/small.png?1727453227</AvatarUrl>
<AvatarUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxsmall.png?1727453227</AvatarUrl>
<Sponsor>Division of Information Technology (DoIT)</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/654/d6ada947e2dc009b9121d8199ac0832e/xxlarge.jpg?1781180154</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/654/d6ada947e2dc009b9121d8199ac0832e/xlarge.jpg?1781180154</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/160/654/d6ada947e2dc009b9121d8199ac0832e/large.jpg?1781180154</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/654/d6ada947e2dc009b9121d8199ac0832e/medium.jpg?1781180154</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/654/d6ada947e2dc009b9121d8199ac0832e/small.jpg?1781180154</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/654/d6ada947e2dc009b9121d8199ac0832e/xsmall.jpg?1781180154</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/654/d6ada947e2dc009b9121d8199ac0832e/xxsmall.jpg?1781180154</ThumbnailUrl>
<ThumbnailAltText>A human figure with outstretched arms inside a circle of two curved arrows, suggesting movement. Below the figure are two words: digital accessibility.</ThumbnailAltText>
<PawCount>9</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Tue, 16 Jun 2026 12:30:00 -0400</PostedAt>
</NewsItem>

<NewsItem contentIssues="false" id="160632" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/160632">
<Title>5 Tips for Creating Clear and Accessible Links</Title>
<Tagline>&#8220;Click here&#8221; doesn&#8217;t tell anyone where they&#8217;re going.</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Links are everywhere -- in syllabi, announcements, email, assignments, websites, and Blackboard pages. They’re one of the most useful tools for connecting students to resources and one of the most commonly overlooked accessibility issues. For anyone using screen readers, a link is read aloud exactly as it appears: “click here” or “hxxps // web(dot)com/long-string-of-characters” -- this communicates nothing.</p>
    <p>Accessible link text is a small fix with a big payoff for everyone. Let’s explore five tips to improve how providing accessible links can make a huge difference to everyone.</p>
    <h3><strong>1. Make Every Link Self-Describing</strong></h3>
    <p>Accessible link text should make sense out of context. Screen reader users often navigate a page by jumping from link to link, without reading the surrounding text. That means each link needs to stand on its own.</p>
    <ul>
    <li>
    <p>Instead of: “To access the library database, click here.”<br><strong>Write:</strong> “Access the UMBC Library database.”</p>
    </li>
    </ul>
    <p><em>Why this matters:</em> “click here” provides no context. Telling someone what happens when the link is clicked and where the link will take them helps them know where they're going.</p>
    <ul>
    <li>
    <p>Instead of: “The reading for this week is available here.”<br><strong>Write:</strong> “Download this week’s reading: Smith (2022) on urban planning (PDF).”</p>
    </li>
    </ul>
    <p><em>Why this matters:</em> Providing clear information about the reading, including the author, year, and file format, helps students know exactly what they are accessing when they click the link.</p>
    <p>Here’s a useful test for you to try: Read only the text of your links with no surrounding context. Do you know where it leads? If not, then you need to make sure you provide clear descriptions.</p>
    <h3><strong>2. Avoid These Common Accessibility Pitfalls</strong></h3>
    <p>A few link habits are so common that they can feel natural, but each one creates a barrier for anyone using assistive technology.</p>
    <ul>
    <li>
    <p>As we just explored, it’s critical to avoid using “Click here” -- not all users navigate with a mouse, and it tells users nothing about the destination.</p>
    </li>
    <li>
    <p>Create unique link text for different destinations -- it’s important not to use the same words for different links (e.g., two different readings both labeled “Weekly reading”).</p>
    </li>
    <li>
    <p>Avoid full web page addresses as link text. A full web page address read aloud character-by-character is inaccessible and confusing. Imagine what it sounds like to hear 150+ letters, numbers, and/or symbols read, one by one, because your link has that many characters.</p>
    </li>
    </ul>
    <h3><strong>3. Indicate When a Link Opens a File or New Window</strong></h3>
    <p>Screen reader and keyboard users benefit from knowing what will happen when they click a link, especially if it downloads a file or opens a new tab. Include a brief note in the link text itself.</p>
    <ul>
    <li>
    <p>“Download the rubric (Word doc)”</p>
    </li>
    <li>
    <p>“View the course policy (PDF)”</p>
    </li>
    <li>
    <p>“Watch the intro video on YouTube (opens in new tab)”</p>
    </li>
    </ul>
    <p>This helps everyone plan their workflow, not just those using screen readers.</p>
    <h3><strong>4. Keep Link Text Concise But Complete</strong></h3>
    <p>Longer isn’t always better. Link text should be long enough to be descriptive, but short enough to be efficient.</p>
    <ul>
    <li>
    <p>Aim for 4-10 words for most links.</p>
    </li>
    <li>
    <p>Skip filler phrases like “please visit” or “feel free to.”</p>
    </li>
    <li>
    <p>Don’t link entire paragraphs. Link a meaningful phrase within the sentence instead.</p>
    </li>
    </ul>
    <p>It’s also important to avoid using “Read more” or “Learn more” -- more about what? If you must use these phrases, tell us what we’re reading or learning more about.</p>
    <h3><strong>5. Check Your Links in Silktide or Ally</strong></h3>
    <p>Silktide and Ally will evaluate link accessibility. In your Blackboard course or organization, Ally will check Ultra Documents and uploaded files. Silktide will flag very obvious issues (links that just say "click here," for instance), but it won't flag anything else, so you still need to manually evaluate all of your page links.</p>
    <p>If your report flags link issues, here’s how to address them:</p>
    <ul>
    <li>
    <p>In Sites or Blackboard Ultra, edit the content item and update the link text directly in the rich text editor.</p>
    </li>
    <li>
    <p>In uploaded Word or PDF files, fix the link text in the original file and re-upload.</p>
    </li>
    <li>
    <p>In your syllabus, use Word’s Accessibility Checker (Review → Check Accessibility) to flag link text issues before uploading.</p>
    </li>
    </ul>
    <p>Link accessibility is one of the fastest fixes in your email, website, document, or course -- and it makes a noticeable difference for everyone who depends on clear navigation to find what they need.</p>
    </div>
]]>
</Body>
<Summary>Links are everywhere -- in syllabi, announcements, email, assignments, websites, and Blackboard pages. They’re one of the most useful tools for connecting students to resources and one of the most...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/160632/guest@my.umbc.edu/93145fd76ce31040d60a4c3ad3920227/api/pixel</TrackingUrl>
<Tag>accessible-links</Tag>
<Tag>blackboard</Tag>
<Tag>digital-accessibility</Tag>
<Tag>faculty</Tag>
<Tag>staff</Tag>
<Tag>students</Tag>
<Group token="doit">Division of Information Technology (DoIT)</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/doit</GroupUrl>
<AvatarUrl>https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/original.JPG?1727453227</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/large.png?1727453227</AvatarUrl>
<AvatarUrl size="medium">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/medium.png?1727453227</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/small.png?1727453227</AvatarUrl>
<AvatarUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxsmall.png?1727453227</AvatarUrl>
<Sponsor>Division of Information Technology (DoIT)</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/632/7d035e878c1cf467fee92229a8f2f856/xxlarge.jpg?1781024319</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/632/7d035e878c1cf467fee92229a8f2f856/xlarge.jpg?1781024319</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/632/7d035e878c1cf467fee92229a8f2f856/large.jpg?1781024319</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/632/7d035e878c1cf467fee92229a8f2f856/medium.jpg?1781024319</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/160/632/7d035e878c1cf467fee92229a8f2f856/small.jpg?1781024319</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/632/7d035e878c1cf467fee92229a8f2f856/xsmall.jpg?1781024319</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/632/7d035e878c1cf467fee92229a8f2f856/xxsmall.jpg?1781024319</ThumbnailUrl>
<ThumbnailAltText>A human figure with outstretched arms inside a circle of two curved arrows, suggesting movement. Below the figure are two words: digital accessibility.</ThumbnailAltText>
<PawCount>18</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Tue, 09 Jun 2026 13:20:49 -0400</PostedAt>
<EditAt>Tue, 09 Jun 2026 13:23:19 -0400</EditAt>
</NewsItem>

<NewsItem contentIssues="true" id="143301" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/143301">
<Title>Introducing the AOK OneSearch Workshop Series</Title>
<Tagline>Discover the Power of AOK OneSearch!</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>We’re excited to announce a series of workshops to introduce AOK OneSearch, the Library’s new search platform! Whether you're a student, faculty, or staff member, this series will help you unlock the full potential of AOK OneSearch for your research and coursework. </p>
    <p><strong>What You’ll Learn:</strong></p>
    <ul>
    <li>How to search for books, articles, videos, and more</li>
    <li>Tips for refining your search results</li>
    <li>How to personalize your account for a better search experience</li>
    <li>How to request materials from other libraries</li>
    </ul>
    <div><br></div>
    <h6>Choose from one of these sessions and click the link for full details and to register:</h6>
    <div><br></div>
    <h5>AOK OneSearch Workshop for Faculty and Staff (<a href="https://my3.my.umbc.edu/groups/library/events/131335" rel="nofollow external" class="bo"><u>Link</u></a>)</h5>
    <div>
    <strong>Date</strong>: Wednesday, September 4</div>
    <div>
    <strong>Time</strong>: 12 – 1 PM</div>
    <div>
    <strong>Location</strong>: Hybrid (Webex and in-person in Library room 259)</div>
    <div>
    <strong>Note: </strong>This workshop is geared towards faculty and staff, but others are welcome to join.</div>
    <div><br></div>
    <h5>AOK OneSearch Workshop for Students (<a href="https://my3.my.umbc.edu/groups/library/events/131384" rel="nofollow external" class="bo"><u>Link</u></a>)</h5>
    <div>
    <div>
    <strong>Date</strong>: Tuesday, September 17</div>
    <div>
    <strong>Time</strong>: 12 – 1 PM</div>
    <div>
    <strong>Location</strong>: Virtual on Webex</div>
    </div>
    <div><br></div>
    <h5>AOK OneSearch Workshop for Graduate Students (<a href="https://my3.my.umbc.edu/groups/library/events/131587" rel="nofollow external" class="bo"><u>Link</u></a>)</h5>
    <div>
    <div>
    <strong>Date</strong>: Monday, September 30</div>
    <div>
    <strong>Time</strong>: 12 – 1 PM</div>
    <div>
    <strong>Location</strong>: Hybrid (Webex and in-person in Library room 259)</div>
    </div>
    <div>
    <strong>Note</strong>: This workshop is geared towards graduate students, but others are welcome to join.</div>
    <div><br></div>
    <h5>AOK OneSearch Workshop for Students (<a href="https://my3.my.umbc.edu/groups/library/events/131507" rel="nofollow external" class="bo"><u>Link</u></a>)</h5>
    <div>
    <div>
    <strong>Date</strong>: Thursday, October 17</div>
    <div>
    <strong>Time</strong>: 12 – 1 PM</div>
    <div>
    <strong>Location</strong>: Virtual on Webex</div>
    </div>
    <div><br></div>
    <h5>AOK OneSearch Workshop for Students (<a href="https://my3.my.umbc.edu/groups/library/events/131642" rel="nofollow external" class="bo"><u>Link</u></a>)</h5>
    <div>
    <div>
    <strong>Date</strong>: Wednesday, October 30</div>
    <div>
    <strong>Time</strong>: 12 – 1 PM</div>
    <div>
    <strong>Location</strong>: Virtual on Webex</div>
    </div>
    <div><br></div>
    <h5>AOK OneSearch Workshop for All (<a href="https://my3.my.umbc.edu/groups/library/events/131588" rel="nofollow external" class="bo"><u>Link</u></a>)</h5>
    <div>
    <div>
    <div>
    <strong>Date</strong>: Tuesday, November 12</div>
    <div>
    <strong>Time</strong>: 12 – 1 PM</div>
    <div>
    <strong>Location</strong>: Hybrid (Webex and in-person in Library room 259)</div>
    </div>
    <div><br></div>
    </div>
    </div>
]]>
</Body>
<Summary>We’re excited to announce a series of workshops to introduce AOK OneSearch, the Library’s new search platform! Whether you're a student, faculty, or staff member, this series will help you unlock...</Summary>
<AttachmentKind>Flyer</AttachmentKind>
<AttachmentUrl>https://assets4-my.umbc.edu/system/shared/attachments/2f84a35a0c605dacb8b4b15476f2af61/6a67c5e8/news/000/143/301/0f1da65fdcf697ce21f424de22c79ab9/OneSearch workshop flyer.pdf?1724350593</AttachmentUrl>
<Attachments>
<Attachment kind="Flyer" url="https://my3.my.umbc.edu/groups/gsa/posts/143301/attachments/52891"></Attachment>
</Attachments>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/143301/guest@my.umbc.edu/9906b01edebee71b4feb1062a5220307/api/pixel</TrackingUrl>
<Tag>faculty</Tag>
<Tag>graduate</Tag>
<Tag>library</Tag>
<Tag>staff</Tag>
<Tag>students</Tag>
<Tag>undergraduate</Tag>
<Tag>workshop</Tag>
<Group token="library">Albin O. Kuhn Library &amp;amp; Gallery</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/library</GroupUrl>
<AvatarUrl>https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xsmall.png?1279120404</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/original.png?1279120404</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xxlarge.png?1279120404</AvatarUrl>
<AvatarUrl size="xlarge">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xlarge.png?1279120404</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/large.png?1279120404</AvatarUrl>
<AvatarUrl size="medium">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/medium.png?1279120404</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/small.png?1279120404</AvatarUrl>
<AvatarUrl size="xsmall">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xsmall.png?1279120404</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xxsmall.png?1279120404</AvatarUrl>
<Sponsor>Albin O. Kuhn Library &amp; Gallery</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/143/301/c4ef48590a6747ca4d5fcb604cb3d61d/xxlarge.jpg?1724350612</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/143/301/c4ef48590a6747ca4d5fcb604cb3d61d/xlarge.jpg?1724350612</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/143/301/c4ef48590a6747ca4d5fcb604cb3d61d/large.jpg?1724350612</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/143/301/c4ef48590a6747ca4d5fcb604cb3d61d/medium.jpg?1724350612</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/143/301/c4ef48590a6747ca4d5fcb604cb3d61d/small.jpg?1724350612</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/143/301/c4ef48590a6747ca4d5fcb604cb3d61d/xsmall.jpg?1724350612</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/143/301/c4ef48590a6747ca4d5fcb604cb3d61d/xxsmall.jpg?1724350612</ThumbnailUrl>
<PawCount>2</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Thu, 22 Aug 2024 14:40:06 -0400</PostedAt>
</NewsItem>

<NewsItem contentIssues="false" id="126807" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/126807">
<Title>HeinOnline database trial</Title>
<Tagline>Give us feedback on this trial resource!</Tagline>
<Body>
<![CDATA[
    <div class="html-content">The AOK Library &amp; Gallery is evaluating <a href="https://lib.guides.umbc.edu/az.php?q=heinonline" rel="nofollow external" class="bo">HeinOnline</a> as a possible replacement for <a href="https://advance-lexis-com.proxy-bc.researchport.umd.edu/bisacademicresearchhome?crid=d9900fec-3718-4868-9905-e2cf06708edd&amp;pdmfid=1516831&amp;pdisurlapi=true" rel="nofollow external" class="bo">NexisUni</a>, and we'd love to hear your thoughts on this trial database!<div><br></div>
    <div>
    <a href="https://lib.guides.umbc.edu/az.php?q=heinonline" rel="nofollow external" class="bo">HeinOnline</a> is a premier online research platform that provides more than 201 million pages of multidisciplinary periodicals, essential government documents, international resources, case law, and much more.</div>
    <div><br></div>
    <div>
    <div>We have created a helpful introduction video, which can be viewed <a href="https://umbc.webex.com/umbc/ldr.php?RCID=40a518a42f6de467b93fe2f0a9ade243" rel="nofollow external" class="bo">here</a>. After viewing and testing HeinOnline, we kindly ask that you share your thoughts with us via this <a href="https://docs.google.com/forms/d/e/1FAIpQLSfU21ausvncUuGRFh3dP78-wKPscecDEFryTMksl7oFkFpsbg/viewform" rel="nofollow external" class="bo">Google Form</a>.</div>
    <div><br></div>
    <div>In addition, HeinOnline will be holding a virtual demo of the site on <strong>Thursday, January 12, 2023, at 12pm. </strong>You are encouraged to attend if you have follow-up questions or would like to learn more about the resource. Click <a href="https://teams.microsoft.com/l/meetup-join/19%3ameeting_MTEyNzhhNjktNWZkMy00MTFiLTliMzYtYzI1YWMxZjAxYzQy%40thread.v2/0?context=%7b%22Tid%22%3a%22a3bb4cc4-0646-496f-90a6-7ac4a0a302df%22%2c%22Oid%22%3a%220467c79d-e0a0-4fa2-8a3b-bbc67182b5b5%22%7d" rel="nofollow external" class="bo">here</a> to join. </div>
    </div>
    <div><br></div>
    <div>Please reach out to Jasmine Shumaker at <a href="mailto:jshumake@umbc.edu">jshumake@umbc.edu</a> or Joe Lee at <a href="mailto:jlee75@umbc.edu">jlee75@umbc.edu</a> if you have any questions or comments.</div>
    </div>
]]>
</Body>
<Summary>The AOK Library &amp; Gallery is evaluating HeinOnline as a possible replacement for NexisUni, and we'd love to hear your thoughts on this trial database!    HeinOnline is a premier online...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/126807/guest@my.umbc.edu/bdfc298594cf1e7d8a5366480ff1b9c0/api/pixel</TrackingUrl>
<Tag>database</Tag>
<Tag>faculty</Tag>
<Tag>students</Tag>
<Tag>trial</Tag>
<Group token="library">Albin O. Kuhn Library &amp;amp; Gallery</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/library</GroupUrl>
<AvatarUrl>https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xsmall.png?1279120404</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/original.png?1279120404</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xxlarge.png?1279120404</AvatarUrl>
<AvatarUrl size="xlarge">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xlarge.png?1279120404</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/large.png?1279120404</AvatarUrl>
<AvatarUrl size="medium">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/medium.png?1279120404</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/small.png?1279120404</AvatarUrl>
<AvatarUrl size="xsmall">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xsmall.png?1279120404</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xxsmall.png?1279120404</AvatarUrl>
<Sponsor>Albin O. Kuhn Library &amp; Gallery</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/126/807/6c24da05f5625c1af9bb55648178e8f5/xxlarge.jpg?1660234551</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/126/807/6c24da05f5625c1af9bb55648178e8f5/xlarge.jpg?1660234551</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/126/807/6c24da05f5625c1af9bb55648178e8f5/large.jpg?1660234551</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/126/807/6c24da05f5625c1af9bb55648178e8f5/medium.jpg?1660234551</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/126/807/6c24da05f5625c1af9bb55648178e8f5/small.jpg?1660234551</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/126/807/6c24da05f5625c1af9bb55648178e8f5/xsmall.jpg?1660234551</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/126/807/6c24da05f5625c1af9bb55648178e8f5/xxsmall.jpg?1660234551</ThumbnailUrl>
<ThumbnailAltText>UMBC library and pond</ThumbnailAltText>
<PawCount>5</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>false</CommentsAllowed>
<PostedAt>Thu, 11 Aug 2022 12:15:14 -0400</PostedAt>
<EditAt>Wed, 03 Dec 2025 16:34:11 -0500</EditAt>
</NewsItem>

<NewsItem contentIssues="true" id="101312" important="false" status="posted" url="https://my3.my.umbc.edu/groups/gsa/posts/101312">
<Title>An Award-Winning Staff!</Title>
<Tagline>Two big award winners at the AOK Library &amp; Gallery!</Tagline>
<Body>
<![CDATA[
    <div class="html-content">The Albin O. Kuhn Library &amp; Gallery proudly announces campus awards for two of our talented staff this semester!<div><br></div>
    <div>
    <strong>Lindsey Loeper</strong>, Librarian III and Reference &amp; Instruction Archivist in our Special Collections division, received the UMBC Provost's Library Faculty Award. This award, founded in 2019, is given every two years to a member of the library faculty who exemplifies excellence in librarianship, research and publication, and service to the UMBC community and information professions. Ms. Loeper is a UMBC graduate (BA, American Studies, 2004) and joined Special Collections in 2007. Her nomination singled out Ms. Loeper's "effective leadership skills, extensive service contributions, and impressive record of scholarship and creativity," as well as her "outstanding and innovative work in teaching, and collaborative and collegial working manner."</div>
    <div><br></div>
    <div><img src="https://my3.my.umbc.edu/system/shared/attachments/news/000/101/312/45cdb55866bcdb7caac8f7e643856747/Loeper%20photo.jpg" style="max-width: 100%; height: auto;"></div>
    <div><br></div>
    <div>
    <strong>Kathy Chetelat</strong>, Library Services Supervisor for Interlibrary Loan, received the 2020-2021 Karen L. Wensch Endowment Award for Outstanding Exempt Staff. Among other criteria, the award recognizes a staff member who displays "extraordinary dedication to the fulfillment of the campus goals and mission." Ms. Chetelat joined the Library &amp; Gallery in 2006, and has been a supervisor in Interlibrary Loan since 2018. Her nomination called attention to skill as a customer-serviced focused manager who is regularly praised by Interlibrary Loan users as "unfailingly professional, friendly, helpful, and thorough." She was honored at the Presidential Faculty &amp; Staff Awards ceremony on April 7, 2021.</div>
    <div><img src="https://my3.my.umbc.edu/system/shared/attachments/news/000/101/312/ad10bfd27bfb2f0d81310a8a732e7bb6/Kathy-Chetelat.jpg" style="max-width: 100%; height: auto;"></div>
    <div><br></div>
    <div>Please join us in thanking and congratulating these two stellar members of the AOK Library &amp; Gallery team and UMBC campus community!</div>
    </div>
]]>
</Body>
<Summary>The Albin O. Kuhn Library &amp; Gallery proudly announces campus awards for two of our talented staff this semester!    Lindsey Loeper, Librarian III and Reference &amp; Instruction Archivist in...</Summary>
<Website>https://library.umbc.edu/</Website>
<AttachmentKind>Image</AttachmentKind>
<AttachmentUrl>https://assets1-my.umbc.edu/system/shared/attachments/78a71522a1fec4402024f0c1dada102d/6a67c5e8/news/000/101/312/45cdb55866bcdb7caac8f7e643856747/Loeper photo.jpg?1619619970</AttachmentUrl>
<Attachments>
<Attachment kind="Image" url="https://my3.my.umbc.edu/groups/gsa/posts/101312/attachments/39636"></Attachment>
<Attachment kind="Image" url="https://my3.my.umbc.edu/groups/gsa/posts/101312/attachments/39638"></Attachment>
<Attachment kind="Document" url="https://my3.my.umbc.edu/groups/gsa/posts/101312/attachments/39640"></Attachment>
</Attachments>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/101312/guest@my.umbc.edu/c9e415dc70695907f8f0f90199d808fb/api/pixel</TrackingUrl>
<Tag>awards</Tag>
<Tag>congratulations</Tag>
<Tag>faculty</Tag>
<Tag>library</Tag>
<Tag>staff</Tag>
<Tag>superstars</Tag>
<Group token="library">Albin O. Kuhn Library &amp;amp; Gallery</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/library</GroupUrl>
<AvatarUrl>https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xsmall.png?1279120404</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/original.png?1279120404</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xxlarge.png?1279120404</AvatarUrl>
<AvatarUrl size="xlarge">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xlarge.png?1279120404</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/large.png?1279120404</AvatarUrl>
<AvatarUrl size="medium">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/medium.png?1279120404</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/small.png?1279120404</AvatarUrl>
<AvatarUrl size="xsmall">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xsmall.png?1279120404</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/016/854d6fae5ee42911677c739ee1734486/xxsmall.png?1279120404</AvatarUrl>
<Sponsor>Albin O. Kuhn Library &amp; Gallery</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/101/312/073baedbb0d3fb04a184cef1b06c5f4f/xxlarge.jpg?1619619905</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/101/312/073baedbb0d3fb04a184cef1b06c5f4f/xlarge.jpg?1619619905</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/101/312/073baedbb0d3fb04a184cef1b06c5f4f/large.jpg?1619619905</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/101/312/073baedbb0d3fb04a184cef1b06c5f4f/medium.jpg?1619619905</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/101/312/073baedbb0d3fb04a184cef1b06c5f4f/small.jpg?1619619905</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/101/312/073baedbb0d3fb04a184cef1b06c5f4f/xsmall.jpg?1619619905</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/101/312/073baedbb0d3fb04a184cef1b06c5f4f/xxsmall.jpg?1619619905</ThumbnailUrl>
<PawCount>7</PawCount>
<CommentCount>1</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Wed, 28 Apr 2021 14:41:04 -0400</PostedAt>
</NewsItem>

</News>
