<?xml version="1.0"?>
<News hasArchived="false" page="1" pageCount="2" pageSize="10" timestamp="Thu, 05 Nov 2026 23:09:59 -0500" url="https://my3.my.umbc.edu/groups/veterans/posts.xml?tag=digital-accessibility">
<NewsItem contentIssues="false" id="164845" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/164845">
<Title>USM Accessibility in Action - November 2026 Issue</Title>
<Tagline>Repost from the USM Kirwan Center for Academic Innovation</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <h3><strong>November 2026 Issue</strong></h3>
    <p>Brought to you by the USM Kirwan Center for Academic Innovation and the USM Digital Accessibility Work Group</p>
    <p>Supporting neurodivergent students requires more than good intentions. It requires understanding neurodiversity itself and designing with both predictability and flexibility in mind. This month, we're bringing you an expert workshop with Dr. Sarah Silverman, practical strategies for your courses and communications, and a look at how faculty across Maryland are solving accessibility's toughest challenges together.</p>
    <p><strong> </strong></p>
    <h4><strong>Beyond Accommodations: Understanding and Supporting Neurodivergent Students</strong></h4>
    <p>Understanding neurodivergent learners starts with understanding neurodiversity itself, not just as a buzzword, but as a concept with deep roots in disability advocacy, a complex relationship to traditional accommodations systems, and profound implications for how we teach. This month, we’re honored to welcome Dr. Sarah Silverman, author of the newly released <a href="https://us.list-manage.com/XiGXxhgbwX3?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo"><em>Classroom Mindscapes: An Introduction to Neurodiversity for Educators</em></a>, for a two-part workshop series that will transform how you think about and support the growing number of neurodivergent students on our campuses.</p>
    <p>Dr. Silverman is a neurodivergent scholar, independent faculty developer, and Disability Studies instructor who brings a firsthand perspective to her work. She focuses on accessible and feminist pedagogy, Universal Design for Learning, and the intersection between disability and ed tech. In addition to her recent book, she also writes <a href="https://us.list-manage.com/oDDdX2mUcAd?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo"><em>Beyond the Scope</em></a>, a Substack newsletter, and shares her materials and presentations on her <a href="https://us.list-manage.com/8ssbkxkySP2?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">blog</a>.</p>
    <p>The two-part workshop responds to a critical reality: campuses are experiencing greater numbers of neurodivergent students and these students are not always supported by the traditional disability accommodations system. Dr. Silverman introduces an approach called “teaching in the neurodiversity paradigm,” which views teaching as the navigation and negotiation of multiple and often contrasting needs. She targets specific “pressure points,” including group assignments, class participation, labs, and practical activities. Part one of the workshop details the history, theory, and first-person perspectives from neurodivergent students, staff, and faculty. Part two offers space to apply your knowledge using complex case studies and scenarios to continue to refine our inclusive practices.</p>
    <p>While live registration has reached capacity, you can <a href="https://us.list-manage.com/P8U9hAP8ec5?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">sign up to receive the recording and workshop materials</a> later this month.</p>
    <p><strong> </strong></p>
    <h4><strong>November Challenge: Design for Predictability &amp; Flexibility</strong></h4>
    <p>Neurodivergent learners, including students with ADHD, autism, dyslexia, and other cognitive differences, often need what seems like a paradox: predictability and flexibility. Predictable course structures reduce anxiety and support executive function, while flexibility accommodates different processing speeds and learning approaches. The good news? Many accessibility practices you're already implementing serve both needs at once. And these principles extend beyond the classroom; they make emails, meeting materials, and professional communications more effective for everyone.</p>
    <h5><strong>Predictability Helps With:</strong></h5>
    <ul>
    <li>Executive function challenges (planning, organizing, prioritizing)</li>
    <li>Anxiety reduction through clear expectations</li>
    <li>Cognitive load management</li>
    </ul>
    
    <h5><strong>Flexibility Supports:</strong></h5>
    <ul>
    <li>Different processing speeds and styles</li>
    <li>Varied ways of engaging with content</li>
    <li>Individual accommodation needs</li>
    </ul>
    
    <h5><strong>This Month's Challenge: Implement Strategies That Deliver Both</strong></h5>
    <h6><strong><em>Captions &amp; Transcripts</em></strong></h6>
    <ul>
    <li>In courses: Students know they can access spoken content in text form and review at their own pace</li>
    <li>Beyond the classroom: Meeting recordings, training videos, and announcements become accessible to all staff</li>
    <li>Quick win: Turn on auto-captions in Zoom recordings, then edit for accuracy (especially discipline-specific terminology)</li>
    </ul>
    <h6><strong><em>Clear, Descriptive Headings</em></strong></h6>
    <ul>
    <li>In courses: Consistent heading structure helps students navigate syllabi, modules, and readings</li>
    <li>Beyond the classroom: Long emails, reports, and meeting agendas become scannable and easier to process</li>
    <li>Quick win: Use Word or Google Docs' heading styles (Heading 1, Heading 2) rather than just making text bold or large. In emails, use clear subject lines and bold key section headers.</li>
    </ul>
    <h6><strong><em>Alt Text for Images</em></strong></h6>
    <ul>
    <li>In courses: Every meaningful image has a text description for students using screen readers or with visual processing differences</li>
    <li>Beyond the classroom: Infographics, charts, and screenshots in emails and presentations become accessible to all colleagues</li>
    <li>Quick win: Start with images that convey essential information (diagrams, charts, screenshots with text)</li>
    </ul>
    <h6><strong><em>Chunk Long Content</em></strong></h6>
    <p>Many neurodivergent people struggle with lengthy, unstructured texts—whether it's a 40-page reading or a dense email. Breaking content into manageable pieces supports both sustained attention and comprehension.</p>
    <p>In courses:</p>
    <ul>
    <li>Break PDFs into sections with descriptive titles ("Introduction: Key Concepts" rather than "Pages 1-5")</li>
    <li>Use headings to create logical stopping points and help students track progress</li>
    <li>Provide reading guides with questions or summaries for each section</li>
    <li>Offer multiple formats when possible (article + podcast summary, textbook chapter + video overview)</li>
    <li>Be explicit about reading purpose: "This section introduces three theories you'll apply in Thursday's discussion"</li>
    </ul>
    
    <p>Beyond the classroom:</p>
    <ul>
    <li>Structure long emails with headings like "Background," "Action Needed," and "Deadline"</li>
    <li>Create clear meeting agendas with time allocations and expected outcomes for each item</li>
    <li>Provide meeting summaries with decisions made, action items, and next steps</li>
    <li>Break complex processes into numbered steps with clear headers</li>
    <li>Use bullet points to make information scannable</li>
    </ul>
    
    <h5><strong>Did You Know?</strong></h5>
    <p>Many neurodivergent students don't disclose their needs or seek formal accommodations. The same is true for neurodivergent staff and colleagues. Proactive design means you're already supporting people you may not even know need it. When you build predictability and flexibility into your materials from the start, whether it's a syllabus, an email, or a meeting agenda, you create an environment where everyone can succeed.</p>
    
    <h5><strong>Take the Challenge:</strong></h5>
    <p>This month, choose one strategy from this list and implement it in your work. Already doing all of these? Share your approach with a colleague or try extending these principles to a new area—like assignment instructions, discussion board structure, committee communications, or professional development materials.</p>
    <p><strong> </strong></p>
    <h4><strong>Spotlight: Faculty Collaboration Tackles Discipline-Specific Accessibility Challenges</strong></h4>
    <p>Led by <strong>Sarah Bass</strong> (University of Maryland Baltimore County, STEM), Luis Engelke (Towson University, Music &amp; Arts), Jessica Grimmer (University of Maryland, College Park, Music &amp; Arts), and Cyndi Wiley (University of Maryland Global Campus, STEM), with 60+ faculty and staff from across Maryland institutions, the Digital Accessibility Communities of Practice are tackling the discipline-specific challenges that general accessibility guidance doesn't address.</p>
    <p>In STEM, project teams are developing workflows to convert handwritten math and tablet notes into accessible formats using tools like MathPix and LaTeX, creating pathways that provide predictability (standardized processes faculty can follow) while maintaining flexibility (multiple tool options for different contexts and comfort levels).</p>
    <p>In Music &amp; Arts, faculty are wrestling with how to write alt text for abstract art that's interpretive rather than purely descriptive, honoring artistic intent while making visual content accessible. This work requires flexibility in approach (recognizing that context matters) while establishing predictable frameworks that faculty can adapt across disciplines from sculpture to stage design.</p>
    <p>Both communities are building resources designed to be shared across Maryland campuses in early spring 2027, transforming individual faculty struggles into collective solutions. Project teams are developing "How Do I..." guides, tool recommendation briefs, student-facing resources, and advocacy materials that will benefit faculty and students statewide.</p>
    <p>Want to follow their progress? Updates will be shared in future newsletters, and all resources will be published on the USM Digital Accessibility Hub as they're completed.</p>
    <p><strong> </strong></p>
    <h4><strong>Save the Date: Spring Cleaning for Accessible Courses</strong></h4>
    <p>Is your spring course ready for a fresh start? Join us in January for our Spring Cleaning workshop series—hands-on sessions to help you review syllabi, update course documents, check multimedia accessibility, and apply lessons from our Communities of Practice and Digital Accessibility Fellows.</p>
    <p><strong>We’re planning afternoon and evening sessions on Tuesday, January 12, and Wednesday, January 13.</strong></p>
    <p>We want to hear from you: What topics would you like us to cover? What challenges are you facing? <a href="https://us.list-manage.com/14ThlHpRtwY?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Submit your session ideas and requests</a>.</p>
    <p>More details coming soon!</p>
    <p><strong> </strong></p>
    <h4><strong>Get Involved</strong></h4>
    <p>Whether you’re ready to lead, want to share an accessibility success story, or are looking for practical guidance, we want to hear from you.</p>
    <p><a href="https://us.list-manage.com/Y2SyEoG4pJ4?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Share or Nominate an Accessibility Win</a></p>
    <p>Visit the <a href="https://us.list-manage.com/egzmblTp8l9?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">USM Digital Accessibility Hub</a></p>
    </div>
]]>
</Body>
<Summary>November 2026 Issue   Brought to you by the USM Kirwan Center for Academic Innovation and the USM Digital Accessibility Work Group   Supporting neurodivergent students requires more than good...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/164845/guest@my.umbc.edu/f02f895f48747c5afb3f8d4129bf2839/api/pixel</TrackingUrl>
<Tag>accessibility</Tag>
<Tag>digital-accessibility</Tag>
<Tag>usm</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/164/845/abb8e6ab6f87fd0b6bfbbb814ec0ce63/xxlarge.jpg?1793718961</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/164/845/abb8e6ab6f87fd0b6bfbbb814ec0ce63/xlarge.jpg?1793718961</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/164/845/abb8e6ab6f87fd0b6bfbbb814ec0ce63/large.jpg?1793718961</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/164/845/abb8e6ab6f87fd0b6bfbbb814ec0ce63/medium.jpg?1793718961</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/164/845/abb8e6ab6f87fd0b6bfbbb814ec0ce63/small.jpg?1793718961</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/164/845/abb8e6ab6f87fd0b6bfbbb814ec0ce63/xsmall.jpg?1793718961</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/164/845/abb8e6ab6f87fd0b6bfbbb814ec0ce63/xxsmall.jpg?1793718961</ThumbnailUrl>
<ThumbnailAltText>"USM Accessibility in Action. Accessible by Design. Inclusive for All." text on top of a red, gray, gold, and black wave design.</ThumbnailAltText>
<PawCount>0</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Wed, 04 Nov 2026 13:30:00 -0500</PostedAt>
</NewsItem>

<NewsItem contentIssues="false" id="163735" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/163735">
<Title>USM Accessibility in Action October 2026 Issue</Title>
<Tagline>Repost from the USM Kirwan Center for Academic Innovation</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Welcome to October! As we continue toward the midpoint of the fall semester, it's a good time to check in on how our courses and communications are working for students and colleagues. This month, we're focusing on the structural elements that make digital content navigable and usable, particularly for people using assistive technologies. We're also excited to officially launch the USM Digital Accessibility Communities of Practice, creating dedicated spaces for faculty to collaborate, share strategies, and tackle discipline-specific accessibility challenges together. Inside this issue, you'll find insights from WebAIM’s latest <a href="https://us.list-manage.com/LA4Z77r4BjC?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">screen reader user survey</a>, practical guidance on tables and lists, an opportunity to learn more about our new communities of practice, and a celebration of faculty leading accessibility work across our system. </p>
    
    <h3><strong>USM Digital Accessibility Communities of Practice Launch</strong></h3>
    <p>On Friday, October 2, nearly 50 faculty from across the University System of Maryland and partner institutions will gather in person at Coppin State University to officially launch the Digital Accessibility Communities of Practice in STEM and Music &amp; Arts.</p>
    <p>These discipline-specific communities bring together faculty leaders who recognize that accessibility isn't one-size-fits-all. From chemical equations and data visualizations to musical notation and performance-based assessments, STEM and Music &amp; Arts present unique accessibility challenges that require specialized knowledge and creative solutions.</p>
    <p>Throughout the 2026-2027 academic year, CoP members will:</p>
    <ul>
    <li>Identify accessibility barriers specific to their disciplines</li>
    <li>Share what's working and learn from peers across institutions</li>
    <li>Develop practical solutions, workflows, and tools faculty can use immediately</li>
    <li>Create resources for colleagues across Maryland and beyond</li>
    </ul>
    <p><strong>Help Shape the Work</strong></p>
    <p>To ensure these Communities of Practice address the real challenges faculty face, we've launched discipline-specific surveys to gather input from STEM and Music &amp; Arts faculty across Maryland:</p>
    <ul>
    <li><a href="https://us.list-manage.com/vIJaTyt33va?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">STEM Faculty Digital Accessibility Survey</a></li>
    <li><a href="https://us.list-manage.com/15VJYucBWVi?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Music &amp; Arts Faculty Digital Accessibility Survey</a></li>
    </ul>
    <p>Your responses, whether you teach biology or sculpture, mathematics or theater, will directly inform the resources, guidance, and solutions these communities develop. The surveys take approximately 15 minutes to complete and are IRB-approved through the University of Maryland, College Park. </p>
    
    <h3><strong>Why Structure Matters: The Power of Lists, Tables, and Meaningful Markup</strong></h3>
    <p>When we design syllabi, lecture slides, or department documents, visual layout is often top of mind. We use bold text, indents, bullet points, and tables to make information clean and easy to scan.</p>
    <p>But what happens when someone doesn't experience your document visually?</p>
    <p>According to WebAIM’s <a href="https://us.list-manage.com/Y7yzznZ5PSC?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Screen Reader User Survey #11</a> (2026), 83.9% of screen reader users report that well-structured, accessible content makes a far greater difference to their digital access than assistive technology upgrades alone. When documents lack underlying semantic structure, assistive technologies can't help learners navigate efficiently.</p>
    <p>This is why true structure matters. This month, we offer suggestions on how to add structure across Word, PowerPoint, and everyday documents:</p>
    <h4><strong>1. Lists: More Than Visual Indents</strong></h4>
    <p><strong>Why it matters:</strong> When you type a dash (-) or asterisk (*) and hit enter, a sighted reader recognizes a list. But a screen reader sees raw, disconnected text. When you use built-in list formatting, assistive technologies announce: <em>"List with 5 items,"</em> allowing users to know the scope of the list, jump through items one by one, or skip past it entirely if it's not what they need.</p>
    <p><strong>Best Practices in Practice:</strong></p>
    <ul>
    <li>
    <p><strong>Use Ribbon Formatting:</strong> In Word, Google Docs, PowerPoint, or your LMS text editor, always click the <strong>Bulleted List</strong> or <strong>Numbered List</strong> tool rather than typing symbols manually.</p>
    </li>
    <li>
    <p><strong>Choose the Right Type:</strong> Use numbered lists when step sequence or priority matters; use bulleted lists when order does not matter.</p>
    </li>
    </ul>
    <h4><strong>2. Tables: For Data, Never for Layout</strong></h4>
    <p><strong>Why it matters: </strong>Tables are designed to show relationships between data (like course grading scales or assignment due dates). Sighted readers quickly match a cell to its row and column headers with their eyes. A screen reader user relies on software to announce the header before reading each data cell (e.g., <em>"Week 3, Topic: Cell Division"</em>).</p>
    <p>Without designated headers, or in tables with merged and split cells, assistive technology can lose track of where data belongs, which can create confusion and disorientation for the user.</p>
    <p><strong>Best Practices in Practice:</strong></p>
    <ul>
    <li>
    <strong>Data, Not Layout:</strong> Never use a table just to place text side-by-side or format a page layout. Use columns or tabs instead.</li>
    <li><strong>Designate a Header Row</strong></li>
    <li>
    <strong>Keep Structure Simple:</strong> Avoid nested tables, merged cells, or empty header rows. If a table becomes too complex, split it into two simpler tables.</li>
    </ul>
    <h4><strong>3. The PDF Factor</strong></h4>
    <p>The WebAIM survey also revealed that 85.6% of respondents find PDFs likely to pose significant accessibility barriers, compared to just 31% for Word documents.</p>
    <p><strong>The Quick Takeaway:</strong> If you create a well-structured document in Word or Google Docs using true headings, bulleted lists, and simple tables with header rows, keep it in that native format.</p>
    <p> </p>
    <h3><strong>October Challenge: The Structure Check</strong></h3>
    <p>In last month’s newsletter, we encouraged you to gather feedback from students and colleagues about accessibility barriers. This month, put what you've learned about structure into practice.</p>
    <p><strong>Your Challenge:</strong> Pick one document (or several!) you use regularly and check its structural accessibility:</p>
    <p><strong>Lists:</strong></p>
    <ul>
    <li>Find any content that's grouped together (steps, options, requirements, resources)</li>
    <li>If you typed dashes (-), asterisks (*), or manual numbers, convert them to true lists using the <strong>Bulleted List</strong> or <strong>Numbered List</strong> button in your editor</li>
    </ul>
    <p><strong>Tables:</strong></p>
    <ul>
    <li>Locate any tables in your document</li>
    <li>Ask: Is this table showing data relationships, or just formatting the page layout?</li>
    <li>If it's data, ensure you've designated the <strong>Header Row</strong> (in Word/PowerPoint: Table Design tab → check "Header Row")</li>
    <li>If it's layout, consider replacing it with columns or simple paragraphs</li>
    </ul>
    <p><strong>Quick Win:</strong> Even fixing one list or one table makes your content more navigable for screen reader users and clearer for everyone.</p>
    <p>Share your before-and-after insight on LinkedIn using <strong>#USMAccessibility</strong>—what did you discover? What surprised you about the structure of your own materials?</p>
    <p> </p>
    <h3><strong>Introducing the 2026-2027 Boosting Course Accessibility Faculty Fellows</strong></h3>
    <p>The USM Kirwan Center for Academic Innovation is excited to welcome 21 faculty members from across the University System of Maryland to the 2026-2027 Boosting Course Accessibility Faculty Fellows program.</p>
    <p>These faculty leaders represent diverse disciplines from nursing and engineering to communication studies and library science and span ten USM institutions. Over the coming year, they will redesign courses with accessibility at the center, implementing universal design principles that remove barriers and benefit all learners. Their work will not only improve access for students in their own courses but also model effective practices that colleagues across Maryland and beyond can learn from and adapt.</p>
    <p><strong>Meet the 2026-2027 Fellows:</strong></p>
    <p><strong>Bowie State University</strong></p>
    <ul>
    <li>Jerry Diabor, Adjunct Professor, Computer Science</li>
    <li>Elkanah Faux, Assistant Professor, Accounting, Finance and Information Systems</li>
    <li>Ebony Toussaint, Assistant Professor, Nursing</li>
    <li>Aislinn Woody, Instructor and Research Specialist, Nursing Education</li>
    </ul>
    <p><strong>Coppin State University</strong></p>
    <ul>
    <li>Patience Ebuwei, Assistant Professor, Health Information Management</li>
    <li>Tammira Lucas, Assistant Professor of Marketing and Interim Director of the Center for Strategic Entrepreneurship</li>
    <li>Mamunur Rahman, Assistant Professor of Decision Sciences</li>
    </ul>
    <p><strong>Frostburg State University</strong></p>
    <ul>
    <li>
    <p>Stefanie Hay, Professor of Nursing</p>
    </li>
    </ul>
    <p><strong>Salisbury University</strong></p>
    <ul>
    <li>
    <p>Viktoria Basham, Lecturer, Clarke Honors College</p>
    </li>
    </ul>
    <p><strong>Towson University</strong></p>
    <ul>
    <li>Audra McMullen, Professor of Communication Studies</li>
    <li>Zach Runge, Adjunct Professor, Communication Studies</li>
    </ul>
    <p><strong>University of Baltimore</strong></p>
    <ul>
    <li>
    <p>Praneet Randhawa, Associate Professor of Marketing</p>
    </li>
    </ul>
    <p><strong>University of Maryland, Baltimore</strong></p>
    <ul>
    <li>
    <p>Jeanine Gargiulo, Didactic Director, Physician Assistant Program</p>
    </li>
    </ul>
    <p><strong>University of Maryland, Baltimore County</strong></p>
    <ul>
    <li>
    <p>Milvia Hernandez, Teaching Professor, Modern Languages, Linguistics and Intercultural Communication</p>
    </li>
    </ul>
    <p><strong>University of Maryland, College Park</strong></p>
    <ul>
    <li>Rasha Alkhateeb, Lecturer, English</li>
    <li>Anna Greenstone, Instructional Designer, Maryland Fire and Rescue Institute (MFRI)</li>
    <li>Helene Nguemgaing, Assistant Clinical Professor, First-Year Innovation &amp; Research Experience (FIRE)</li>
    <li>Ryan O'Grady, Senior Lecturer, Master of Library and Information Science Program</li>
    </ul>
    <p><strong>University of Maryland Eastern Shore</strong></p>
    <ul>
    <li>Jia Liu, Assistant Professor, Engineering</li>
    <li>Madhumi Mitra, Professor of Biology and Environmental Sciences</li>
    <li>Masoud Moghaddam, Associate Professor, Physical Therapy</li>
    </ul>
    <p>We look forward to sharing their progress and insights throughout the year. Congratulations to all the Fellows!</p>
    <p> </p>
    <h3><strong>Get Involved</strong></h3>
    <p>Whether you’re ready to lead, want to share an accessibility success story, or are looking for practical guidance, we want to hear from you.</p>
    <p><a href="https://forms.office.com/Pages/ResponsePage.aspx?id=rzR0-QmX4kSEaAIqtK9LNMBrgG4-0tFEoiFGumnz1dRUNEk1MU9NUTY1UlU2ODQ4UkI2U1hYSjk0WS4u" rel="nofollow external" class="bo">Share or Nominate an Accessibility Win</a></p>
    <p>Visit the <a href="https://www.usmd.edu/digital-accessibility/" rel="nofollow external" class="bo">USM Digital Accessibility Hub</a></p>
    </div>
]]>
</Body>
<Summary>Welcome to October! As we continue toward the midpoint of the fall semester, it's a good time to check in on how our courses and communications are working for students and colleagues. This month,...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/163735/guest@my.umbc.edu/ffb898d7c8e55e8db6f93c9a4d830d1e/api/pixel</TrackingUrl>
<Tag>accessibility</Tag>
<Tag>digital-accessibility</Tag>
<Tag>newsletter</Tag>
<Tag>usm</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/163/735/c2b3ff76ff4ae58725a96bdef627f171/xxlarge.jpg?1791221362</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/163/735/c2b3ff76ff4ae58725a96bdef627f171/xlarge.jpg?1791221362</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/163/735/c2b3ff76ff4ae58725a96bdef627f171/large.jpg?1791221362</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/163/735/c2b3ff76ff4ae58725a96bdef627f171/medium.jpg?1791221362</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/163/735/c2b3ff76ff4ae58725a96bdef627f171/small.jpg?1791221362</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/163/735/c2b3ff76ff4ae58725a96bdef627f171/xsmall.jpg?1791221362</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/163/735/c2b3ff76ff4ae58725a96bdef627f171/xxsmall.jpg?1791221362</ThumbnailUrl>
<ThumbnailAltText>Banner with red, gray, gold, and black wave with the text "USM Accessibility in Action. Accessible by Design. Inclusive for All."</ThumbnailAltText>
<PawCount>2</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Wed, 07 Oct 2026 13:00:00 -0400</PostedAt>
<EditAt>Wed, 07 Oct 2026 13:50:04 -0400</EditAt>
</NewsItem>

<NewsItem contentIssues="false" id="162471" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/162471">
<Title>Take the #NoMouse Challenge!</Title>
<Tagline>Discover how accessible your digital content really is</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Here's a quick challenge: close your laptop trackpad, put your mouse to the side, and try to get through the next ten minutes using only your keyboard.</p>
    <p>Can you navigate to your Blackboard course? Open a Google Doc? Reply to an email? Move through a PowerPoint presentation?</p>
    <p>If it feels frustrating or impossible, you've just experienced what many of your colleagues and students navigate every day. The #NoMouse Challenge is a global awareness effort that invites people who create digital content -- websites, documents, slides, course materials -- to experience the web and their own tools the way users with disabilities often do. People with physical disabilities, low vision, or motor impairments frequently rely on keyboards, screen readers, voice recognition, or other assistive technologies to do their work. When the content we create isn't designed with those tools in mind, we accidentally close the door on them.</p>
    <p>Here's how to take the challenge -- and what to do with what you learn.</p>
    <h3><strong>1. Try it: Navigate without your mouse</strong></h3>
    <p>Pick any digital space you use regularly and try it keyboard-only for a few minutes. Here are good places to start:</p>
    <ul>
    <li>
    <p>Your Blackboard course or organization</p>
    </li>
    <li>
    <p>A Google Doc, Slide, or Form you've shared with students or colleagues</p>
    </li>
    <li>
    <p>Your department's myUMBC page or a UMBC Sites page</p>
    </li>
    <li>
    <p>Your email inbox in Gmail</p>
    </li>
    </ul>
    <p>Use these keyboard shortcuts to get around:</p>
    <ul>
    <li>
    <p><strong>Tab</strong> -- move to the next link, button, or form element</p>
    </li>
    <li>
    <p><strong>Shift + Tab</strong> -- move backward</p>
    </li>
    <li>
    <p><strong>Enter or Space</strong> -- activate a link or button</p>
    </li>
    <li>
    <p><strong>Arrow keys</strong> -- navigate menus, dropdowns, or slider controls</p>
    </li>
    <li>
    <p><strong>Escape</strong> -- close a dialog or menu</p>
    </li>
    </ul>
    <p>As you go, ask yourself:</p>
    <ul>
    <li>
    <p>Can I reach everything on this page or in this document?</p>
    </li>
    <li>
    <p>Can I tell where I am at any point?</p>
    </li>
    <li>
    <p>Can I operate every button, slider, or control?</p>
    </li>
    </ul>
    <p>You may be surprised by what you find -- and what you can't find.</p>
    <h3><strong>2. Think about who's on the other side</strong></h3>
    <p>Accessibility isn't just a website issue. Every piece of digital content you create -- a syllabus, a slide deck, a course announcement, a shared Google Sheet -- is a potential barrier for someone if it's not made thoughtfully. Consider a few examples:</p>
    <ul>
    <li>
    <p>A colleague with a repetitive strain injury relies on keyboard navigation. If your Google Doc doesn't support Tab order correctly, they may not be able to complete it.</p>
    </li>
    <li>
    <p>A student with low vision uses screen magnification and browser zoom. If your Blackboard content uses images of text instead of real text, the content becomes illegible when enlarged.</p>
    </li>
    <li>
    <p>A student who is deaf or hard of hearing cannot access audio unless it's captioned or transcribed. If your video announcement in Blackboard isn't captioned, that student misses the message entirely.</p>
    </li>
    <li>
    <p>A student with dyslexia uses a text-to-speech tool to read course documents. If your Word doc or PDF doesn't have proper heading structure, the tool reads the page in a jumbled order -- or not at all.</p>
    </li>
    </ul>
    <p>The methods for creating accessible content are well established, and in many cases, they take just a few extra minutes. The barrier is usually awareness, not effort.</p>
    <h3><strong>3. Make one change</strong></h3>
    <p>The challenge doesn't end with the experiment. After you've tried keyboard-only navigation, pick one thing to improve in your own digital content. Even small changes make a real difference.</p>
    <ul>
    <li>
    <p>Add <a href="https://my3.my.umbc.edu/groups/instructional-technology/posts/153366" rel="nofollow external" class="bo">alt text to an image</a> in your Blackboard course or a Google Slide.</p>
    </li>
    <li>
    <p>Apply heading styles in <a href="https://my3.my.umbc.edu/groups/doit/posts/160956" rel="nofollow external" class="bo">a Word doc</a> or <a href="https://my3.my.umbc.edu/groups/doit/posts/161092" rel="nofollow external" class="bo">Google Doc</a> instead of just bolding and resizing text.</p>
    </li>
    <li>
    <p>Review the <a href="https://my3.my.umbc.edu/groups/instructional-technology/posts/155041" rel="nofollow external" class="bo">captions on a video</a> you've posted and correct any errors.</p>
    </li>
    <li>
    <p>Check that the link text in your next email announcement actually <a href="https://my3.my.umbc.edu/groups/doit/posts/160632" rel="nofollow external" class="bo">describes the destination</a> -- "Visit the Digital Accessibility site" rather than "click here."</p>
    </li>
    </ul>
    <p>Not sure where to start? UMBC's <a href="https://accessibility.umbc.edu/digital-accessibility" rel="nofollow external" class="bo">Digital Accessibility site</a> has quick guides, tutorials, and resources tailored to the tools you use every day, including Blackboard, Google Workspace, Microsoft 365, and myUMBC.</p>
    <p>Ready to take the challenge? Put down your mouse and see what you discover. Then share what surprised you with a colleague -- awareness is contagious.</p>
    <p><strong><br><br></strong></p>
    <p><em><a href="https://nomouse.org/" rel="nofollow external" class="bo">NoMouse.org</a> is a project of <a href="https://uw.edu/doit" rel="nofollow external" class="bo">The DO-IT Center</a> at the University of Washington, and is adapted and reused under a <a href="https://creativecommons.org/licenses/by-nc-sa/4.0/" rel="nofollow external" class="bo">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</a>.</em></p>
    </div>
]]>
</Body>
<Summary>Here's a quick challenge: close your laptop trackpad, put your mouse to the side, and try to get through the next ten minutes using only your keyboard.   Can you navigate to your Blackboard...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/162471/guest@my.umbc.edu/b6cd7e2444100f01fc778fe6c0c297d6/api/pixel</TrackingUrl>
<Tag>digital-accessibility</Tag>
<Tag>no-mouse-challenge</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/162/471/e9dc65b742f858f504a597de6a8f32c0/xxlarge.jpg?1788558682</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/162/471/e9dc65b742f858f504a597de6a8f32c0/xlarge.jpg?1788558682</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/162/471/e9dc65b742f858f504a597de6a8f32c0/large.jpg?1788558682</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/162/471/e9dc65b742f858f504a597de6a8f32c0/medium.jpg?1788558682</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/162/471/e9dc65b742f858f504a597de6a8f32c0/small.jpg?1788558682</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/162/471/e9dc65b742f858f504a597de6a8f32c0/xsmall.jpg?1788558682</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/162/471/e9dc65b742f858f504a597de6a8f32c0/xxsmall.jpg?1788558682</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>10</PawCount>
<CommentCount>1</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Tue, 15 Sep 2026 13:01:33 -0400</PostedAt>
<EditAt>Tue, 15 Sep 2026 13:04:54 -0400</EditAt>
</NewsItem>

<NewsItem contentIssues="false" id="162685" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/162685">
<Title>USM Accessibility in Action - September 2026 Issue</Title>
<Tagline>Accessibility moves from planning into practice</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Repost from the USM Kirwan Center for Academic Innovation and the USM Digital Accessibility Work Group</p>
    <h3>September 2026 Issue</h3>
    <p>As the fall semester gets underway, accessibility moves from planning into practice. Whether you teach courses, support students, manage programs, or create communications, September is when we discover what's working and where our next opportunities for improvement lie. This month's newsletter focuses on accessibility as a shared responsibility that belongs to all of us, regardless of our role. Inside, you'll find a recap of our fall course prep day, an invitation to gather feedback and make real-time improvements, and a deeper look at why accessibility truly is everyone's job. Let's make this semester one where accessibility isn't just built in—it's continuously improved through the insights and actions of our entire USM community.</p>
    <h4>Ready, Set, Accessible! Fall Course Prep Day Recap</h4>
    <p>On August 3, 2026, faculty and staff from across Maryland joined us virtually for a half-day of practical accessibility strategies to start the semester strong. Participants explored how to evaluate course resources for accessibility, redesign assignments for clarity and inclusion, and create learning experiences that support all students.</p>
    <p><strong>We Featured:</strong></p>
    <p><strong>Digital Accessibility 101: A Coffee Chat Refresher</strong> with Nancy O'Neill<br>A foundational overview of accessibility concepts and why they matter for all learners.<br><a href="https://us.list-manage.com/CnwwCY8pLdx?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Recording</a></p>
    
    <p><strong>Before You Assign It: Checking Course Materials for Accessibility</strong> with Haley Cristea<br>Practical strategies for identifying accessibility barriers in PDFs, videos, websites, and publisher resources before students encounter them.<br><a href="https://us.list-manage.com/A_8DDCAA56w?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Recording</a></p>
    
    <p><strong>The 10-Minute Assignment Makeover</strong> with Teresa Valais<br>How to pair generative AI with the Transparency in Learning and Teaching (TILT) framework to quickly redesign assignments that reduce ambiguity and strengthen learning outcomes.<br><a href="https://us.list-manage.com/uKFb4PUTIFL?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Recording</a></p>
    
    <p><strong>Sense-Sational Design: A Full Spectrum Approach</strong> with Karen Silverstrim<br>Moving beyond document fixes to design learning experiences that offer multiple ways to access information, engage with ideas, and demonstrate understanding across visual, auditory, cognitive, and interactive dimensions.<br><a href="https://us.list-manage.com/MCHAAlej50r?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Recording</a></p>
    
    <p><strong>Missed the event or want to revisit a session?</strong> All recordings and resources are available on the <a href="https://us.list-manage.com/rxoAkSgFq46?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Ready, Set, Accessible! resource page</a>.</p>
    <p> </p>
    <h4>September Challenge: The Accessibility Feedback Loop</h4>
    <p>Whether you teach courses, support students, manage programs, or create communication, ask for input, and act on what you learn. This month, gather feedback on accessibility from the people who experience your work:</p>
    <ul>
    <li>
    <p><strong>Faculty:</strong> Ask students: "What's working well in how course materials are presented? What could be clearer or easier to navigate?"</p>
    </li>
    <li>
    <p><strong>Staff:</strong> Ask colleagues or students who use your services: "Is there anything about how we share information or resources that creates unnecessary barriers?"</p>
    </li>
    <li>
    <p><strong>Administrators:</strong> Ask your team: "What would make our communications, documents, or processes more accessible?"</p>
    </li>
    </ul>
    
    <p><strong>Then take action:</strong> Choose one piece of feedback and make an adjustment. It might be as simple as adding headings to a document, providing materials in an alternative format, or clarifying instructions.</p>
    
    <p>When we ask students and colleagues about accessibility barriers, we're not just fixing individual problems; we're building a culture where accessibility feedback is welcomed, expected, and acted upon. This transforms accessibility from a compliance checklist into a continuous improvement practice.</p>
    <p> </p>
    <h4>Why Accessibility Is Everyone’s Job</h4>
    <p>If you’ve ever heard (or thought) the phrase "that's not my job" regarding accessibility, you're not alone. Inspired by <a href="https://us.list-manage.com/16qcnoYtgC2?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Dr. Katie Grennell’s insights</a> on navigating pushback to accessibility work, we will explore why these concerns are common across higher education, and how they reflect real challenges: unclear expectations, competing priorities, and uncertainty about where to start. Despite these challenges, accessibility is woven into the work we all do—teaching, communicating, creating content, supporting students. And it doesn't require becoming an expert overnight.</p>
    
    <p>When colleagues express concerns about accessibility, they're often communicating something legitimate:</p>
    <ul>
    <li>
    <p>"I don't have time" → <em>"I'm overwhelmed and don't know where to start."</em></p>
    </li>
    <li>
    <p>"That's disability services' job" → <em>"I'm unclear about my role."</em></p>
    </li>
    <li>
    <p>"I don't have disabled students" → <em>"I don't see how this benefits my class."</em></p>
    
    </li>
    </ul>
    <p>These aren't excuses, but rather they're signals that we need clearer expectations and better support.</p>
    <p>Accessibility connects to things we already care about as higher education professionals:</p>
    <p><strong>Student success:</strong> Accessible courses remove barriers that prevent disabled students from engaging fully. Accessibility wins such as clear document structure, captions, and transparent instructions help ensure that disabled students including those with visual, auditory, motor, cognitive, or learning disabilities, can engage in learning effectively and independently.</p>
    <p><strong>Practical efficiency:</strong> Building accessibility in from the start saves time later. You won't be scrambling to fix materials when a student requests accommodations.</p>
    <p><strong>Universal Design for Learning:</strong> Accessibility and UDL go together. When you offer multiple ways to access content and demonstrate learning, all students benefit.</p>
    <p><strong>Everyone Plays a Role</strong></p>
    <ul>
    <li>
    <p>Faculty design accessible courses and create clear materials</p>
    </li>
    <li>
    <p>Staff ensure communications and processes work for everyone</p>
    </li>
    <li>
    <p>Instructional designers provide practical guidance and support</p>
    </li>
    <li>
    <p>Administrators set expectations and allocate resources</p>
    </li>
    <li>
    <p>Students give feedback that helps us identify barriers</p>
    </li>
    </ul>
    
    <p>When accessibility becomes part of how we work, it transforms from a compliance task into a shared commitment to student success.</p>
    <p> </p>
    <h4>Applications Open for Fall Cohort of USM Digital Accessibility Fellows</h4>
    <p>The USM Kirwan Center for Academic Innovation is accepting applications for the Boosting Course Accessibility Faculty Fellows program. This initiative supports up to 12 USM faculty members in digital accessibility-related course redesign to reduce barriers and improve access for all students.</p>
    
    <p><strong>What You'll Receive:</strong></p>
    <ul>
    <li>
    <p>$1,500 stipend</p>
    </li>
    <li>
    <p>Structured support for accessibility-focused course improvements</p>
    </li>
    <li>
    <p>Connection to a cohort of faculty working on similar goals</p>
    </li>
    </ul>
    
    <p><strong>Application Deadline:</strong> Thursday, September 11, 2026</p>
    
    <p>Whether you're ready to tackle captions for an entire course, redesign assignments for clarity, or systematically improve document accessibility, this program provides the time and support to make meaningful progress.</p>
    <p><a href="https://us.list-manage.com/18tkpscWUUC?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Learn More and Apply</a> </p>
    <h4>Faculty Spotlight: Dr. Angela Freeman, Associate Professor of Biological Sciences, Salisbury University</h4>
    <p>Angela Freeman's entry into digital accessibility started long before the updated Title II regulations. She is a millennial who keeps her phone with the sound off all the time, which means uncaptioned videos are a particular pet peeve. It was such a pet peeve, in fact, that Angela has been captioning her own videos, for class or otherwise, for 9 years.</p>
    <p>When colleagues began discussing the approaching Title II deadline, Angela found herself already ahead of the curve on video captions. But her home discipline, Biology, presented STEM-specific challenges that standard accessibility guides don't always address. How do you make a lab handout screen-readable when it's full of underscores for fill-in-the-blank answers? How do you write alt-text for an anatomy quiz without providing the answer? Angela addressed the first by moving away from the “hundreds of underscores” that screen readers often skip or misread, instead using Word’s developer tools to create accessible form fields. For the second, she navigated assessments by using descriptive but non-identifying language, describing a "vessel colored red" rather than simply naming it an "artery."</p>
    <p>Rather than tackling these disciplinary challenges alone, Angela brought her colleagues into the conversation. At the November 2025 Biological Sciences Department meeting, she presented a 21-slide roadmap that addressed why improving digital accessibility benefits everyone and provided practical "how-to" steps for headings, captions, and alt text. Drawing on her background as a "tech-native" who grew up with command-line computers, she didn't just tell her colleagues <em>what</em> to do; she showed them <em>how</em> to do it efficiently. She created a Word template so that accessibility is baked in the moment a colleague opens a new document, preventing them from having to "reinvent the wheel" every time. She also volunteered to help fellow faculty with ongoing accessibility questions and made her presentation available to the entire department.</p>
    <p>Angela's leadership has moved the department to an estimated 85-90% compliance rate. Beyond her department, she now sits on the curriculum committee for the Henson School of Science and Technology, where she catches the small but vital details, like ensuring a syllabus file has a proper title rather than a string of characters. She's also become a go-to resource for colleagues who are working on improving the accessibility of their course materials.</p>
    <p>But Angela hasn't abandoned her original passion: captions. She still goes the extra mile for videos, even when they're not her own. "A lot of YouTube videos don't have captions," she explains. "And so I end up including links [to the video], but then I usually screen record, put new captions on, or I share a transcript that I just made with all the students, and I'm like, take this. You should have it. Because this video is great, but it's from 10 years ago, and no one captioned it." Even when auto-captions exist, she provides corrected transcripts for her students, warning them that "the captions are okay, but some of those science words are mixed up." For example, auto-captions often want to turn “caecilians,” the amphibians, into “Sicilians,” the people from Italy. If you don’t check, a student will get the wrong answer.</p>
    <p>Angela's approach demonstrates that accessibility is most sustainable when it's integrated into daily habits rather than treated as a compliance checkbox, and her work has created a ripple effect across SU’s Henson School of Science &amp; Technology. What started as a personal pet peeve about uncaptioned videos has become a shared departmental practice to make materials more usable for everyone.</p>
    <p> </p>
    <h4>Get Involved</h4>
    <p>Whether you’re ready to lead, want to share an accessibility success story, or are looking for practical guidance, we want to hear from you.</p>
    <p><a href="https://us.list-manage.com/HYHoGjMR7N9?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Share or Nominate an Accessibility Win</a></p>
    <p>Visit the <a href="https://us.list-manage.com/7UZEQUD2AGM?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">USM Digital Accessibility Hub</a></p>
    <p> <a href="https://us.list-manage.com/weOTgWErNDR?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Subscribe to our Newsletter!</a><a href="https://us.list-manage.com/frEZ1aLKEMO?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo"><img src="https://ci3.googleusercontent.com/meips/ADKq_NarKlxhrX1_bHbTbvsMcDAv1If1m9vKchpHV7y7hgxHjY_8w41JUJJq632sbbCANtyNFVH8t_A6PVb-pa9Ey-_BKA-QnF6B7EtwlzhYOQ8LtGVdSG38iSzdrK7vnxHXj44jbhZqsyYHh-Nh23x_J9_NC9rTQm9q=s0-d-e1-ft#https://cdn-images.mailchimp.com/icons/social-block-v3/block-icons-v3/linkedin-filled-gray-40.png" alt="LinkedIn icon" style="max-width: 100%; height: auto;"></a><a href="https://us.list-manage.com/sg8_wUpWzBP?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Follow us on LinkedIn</a></p>
    <p><em>This document is licensed under a </em><a href="https://us.list-manage.com/aIxU99MUp6P?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo"><em>Creative Commons Attribution-NonCommercial-ShareAlike 4.0 [CC BY-NC-SA 4.0] International license</em></a><em>. Users are welcome to distribute, adapt, remix, and build upon the material in any medium or format provided they give attribution to the USM Kirwan Center for Academic Innovation, provide a link to the Creative Commons license, and indicate if changes were made. Per the Creative Commons stipulations, users may provide this information in any reasonable manner, but not in any way that suggests the Kirwan Center, as licensor, endorses them or their use. Users must also abide by the following stipulations: They must not use the material for </em><a href="https://us.list-manage.com/HheIeQZrxmF?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo"><em>commercial purposes</em></a><em>, and if they remix, transform, or build upon the material, they must distribute their contributions under the same CC BY-NC-SA 4.0 license. This license does not extend to materials that are linked to this document.</em><br><br>Our mailing address is:<br>University System of Maryland, 3300 Metzerott Road, Adelphi, MD 20783</p>
    </div>
]]>
</Body>
<Summary>Repost from the USM Kirwan Center for Academic Innovation and the USM Digital Accessibility Work Group   September 2026 Issue   As the fall semester gets underway, accessibility moves from...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/162685/guest@my.umbc.edu/4b0e04dca9941c3bfc84ad33cd63aa7f/api/pixel</TrackingUrl>
<Tag>accessibility</Tag>
<Tag>digital-accessibility</Tag>
<Tag>usm</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://assets3-my.umbc.edu/system/shared/thumbnails/news/000/162/685/fbb4d19406f02d9dcaae8ea53dc030a4/xxlarge.jpg?1789094038</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/162/685/fbb4d19406f02d9dcaae8ea53dc030a4/xlarge.jpg?1789094038</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/162/685/fbb4d19406f02d9dcaae8ea53dc030a4/large.jpg?1789094038</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/162/685/fbb4d19406f02d9dcaae8ea53dc030a4/medium.jpg?1789094038</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/162/685/fbb4d19406f02d9dcaae8ea53dc030a4/small.jpg?1789094038</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/162/685/fbb4d19406f02d9dcaae8ea53dc030a4/xsmall.jpg?1789094038</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/162/685/fbb4d19406f02d9dcaae8ea53dc030a4/xxsmall.jpg?1789094038</ThumbnailUrl>
<ThumbnailAltText>Red, gray, gold, and black wave banner design with the text "USM Accessibility in Action. Accessible by Design. Inclusive for All."</ThumbnailAltText>
<PawCount>1</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Mon, 14 Sep 2026 11:38:58 -0400</PostedAt>
</NewsItem>

<NewsItem contentIssues="false" id="161402" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/161402">
<Title>Beyond PDFs: 5 Better Ways to Share Content</Title>
<Tagline>Rethinking a default file format to remove barriers.</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>You've probably uploaded a PDF to your course or website dozens of times without a second thought: a syllabus, an article, a set of lecture notes. </p>
    <p>PDFs are everywhere in higher ed. For years they have functioned as the safe, universal choice to prevent editing a file once it’s shared; however, PDFs are often the format most likely to create barriers for students, particularly those using assistive technology. What happens when a student using a screen reader opens that file and the reading order is scrambled, or the text isn’t recognized?  </p>
    <p>The good news: in many cases, you can share the same content in its original format - while preserving accessibility, simplifying updates, and still maintaining control over who can view or edit it. </p>
    <p>When sharing content, here are five considerations that don't depend on a PDF.</p>
    <p><strong>1. PDFs Preserve Content Exactly the Way It’s Designed</strong></p>
    <p>One of the biggest reasons people choose PDFs is that they preserve formatting. Fonts, spacing, images, and page layout appear exactly as intended, regardless of the device or software a student might use. For documents where visual presentation is essential - such as official forms, archival records, or publisher materials - that consistency can be valuable.</p>
    <p>But preserving appearance isn't the same as preserving accessibility. A PDF can look perfect on screen, yet may still be difficult or impossible for a screen reader to interpret if headings, reading order, image descriptions, or searchable text are missing. </p>
    <p><strong>2. Share Word Documents &amp; PowerPoint Presentations</strong><strong><br></strong>A well-structured accessible document, with headings, lists, alt text, and descriptive hyperlinks, is easier for every student to navigate than a scanned or exported PDF. It’s also far easier for you to update next semester. Structure is what makes a document work with a screen reader in the first place: without accurate headings, there's no way to jump between sections or understand how content is organized.</p>
    <p>The same structural principles apply to slides: use built-in layouts instead of freeform text boxes, add alt text to images, and maintain a logical reading order so screen readers announce content in the right sequence.</p>
    <p>Before exporting a document or presentation as a PDF, ask if students really need that fixed-layout file - or whether sharing the original document, presentation, or Blackboard content would provide the same information in a format that's easier to access, navigate, and update.</p>
    <p>Related readings:</p>
    <ul>
    <li>
    <p><a href="https://my3.my.umbc.edu/groups/doit/posts/160956" rel="nofollow external" class="bo">5 Tips for Accessible Word Documents</a></p>
    </li>
    <li>
    <p><a href="https://my3.my.umbc.edu/groups/doit/posts/161203" rel="nofollow external" class="bo">10 Ways to Make Your Slide Decks More Accessible</a> </p>
    </li>
    <li>
    <p><a href="https://my3.my.umbc.edu/groups/instructional-technology/posts/155149" rel="nofollow external" class="bo">5 Ways to Create "Born Accessible" Course Materials</a> </p>
    </li>
    </ul>
    <p><strong>3. Share View-Only Files Instead of PDFs</strong><strong><br></strong>Worried about users editing your original file? You don't need to convert to PDF to protect it.</p>
    <ul>
    <li>
    <p>In Microsoft Office (Word, PowerPoint, Excel), use Share → Can view to send a live, view-only link instead of a flattened export. Recipients still get a fully accessible, screen-reader-friendly document — just without edit access.</p>
    </li>
    <li>
    <p>In Google Drive, set sharing permissions to Viewer so students can read but not edit or comment. Because the file stays in its native Google Docs or Slides format, it keeps its accessibility structure — no PDF export needed.</p>
    </li>
    </ul>
    <p><strong>4. Let Blackboard Permissions Do the Work</strong><strong><br></strong>Blackboard already has built-in tools for controlling access without ever touching a PDF.</p>
    <ul>
    <li>
    <p>Post content as an Ultra Document or in a Content Area, and use role-based permissions to control who can view, edit, or download.</p>
    </li>
    <li>
    <p>This keeps materials in accessible, native web format while still restricting student access to editing.</p>
    </li>
    </ul>
    <p><strong>5. Reconsider the Legacy of PDFs</strong><strong><br></strong>This mindset isn't just for new content. Before you fix a PDF that's already in your course, ask the same question you'd ask about a new one: <strong>do you still need it?</strong> If the content has been replaced elsewhere, is redundant, or is simply out of date, removing it is the fastest way to improve accessibility - no reformatting required.</p>
    <p>Sometimes a PDF really is the only option - a signed form, a publisher file, an archival document. When that happens, our <a href="https://my3.my.umbc.edu/groups/doit/posts/161221" rel="nofollow external" class="bo">4 Strategies for Creating Accessible PDFs</a> walks through how to remake or remediate it properly.</p>
    <p>Visit UMBC's <a href="https://accessibility.umbc.edu/digital-accessibility/accessible-documents-presentations/" rel="nofollow external" class="bo">Digital Accessibility resource</a> to learn more about managing PDF files. </p>
    </div>
]]>
</Body>
<Summary>You've probably uploaded a PDF to your course or website dozens of times without a second thought: a syllabus, an article, a set of lecture notes.    PDFs are everywhere in higher ed. For years...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/161402/guest@my.umbc.edu/9444369deeea41b520887668210207ea/api/pixel</TrackingUrl>
<Tag>biro</Tag>
<Tag>da</Tag>
<Tag>digital-accessibility</Tag>
<Tag>pdf</Tag>
<Tag>remediation</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/402/8fe12e945c2464d2598afad1d7229db5/xxlarge.jpg?1785764592</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/402/8fe12e945c2464d2598afad1d7229db5/xlarge.jpg?1785764592</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/161/402/8fe12e945c2464d2598afad1d7229db5/large.jpg?1785764592</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/402/8fe12e945c2464d2598afad1d7229db5/medium.jpg?1785764592</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/402/8fe12e945c2464d2598afad1d7229db5/small.jpg?1785764592</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/161/402/8fe12e945c2464d2598afad1d7229db5/xsmall.jpg?1785764592</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/161/402/8fe12e945c2464d2598afad1d7229db5/xxsmall.jpg?1785764592</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>2</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Thu, 06 Aug 2026 09:29:14 -0400</PostedAt>
<EditAt>Wed, 12 Aug 2026 15:00:49 -0400</EditAt>
</NewsItem>

<NewsItem contentIssues="false" id="161221" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/161221">
<Title>Creating Accessible PDFs: 4 Tips for Success</Title>
<Tagline>Ensure your digital PDFs are inclusive for all learners.</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>PDFs are a staple of academic life, used for everything from syllabi to complex research articles. However, without intentional design, they can create significant barriers for students using screen readers or other assistive technologies. Making your PDFs accessible ensures that information is clear, searchable, and usable for every member of our community. By focusing on accessible creation and remediation techniques, transform your materials into inclusive learning tools.</p>
    <h3><strong>1. Start with an Accessible Foundation</strong></h3>
    <p>The most effective way to create an accessible PDF is to ensure the source file is accessible from the start. Whether you are working in Microsoft Word, Google Docs, or PowerPoint, following these core principles will save time and improve the final result:</p>
    <ul>
    <li>
    <p><strong>Use Built-in Heading Styles: </strong>Instead of manually bolding or enlarging text, use styles like Heading 1, 2, and 3. This creates a logical structure that screen readers can navigate.</p>
    </li>
    <li>
    <p><strong>Add Meaningful Alt Text: </strong>Provide concise descriptions for images, charts, and graphics so their purpose is clear to those who cannot see them.</p>
    </li>
    <li>
    <p><strong>Use Descriptive Links: </strong>Avoid generic phrases like "click here." Use text that describes the destination or action, such as "Download the 2026 Course Syllabus." (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>
    </li>
    </ul>
    <h3><strong>2. Export the PDF with Accessibility </strong></h3>
    <p>How you save your file as a PDF is just as important as how you format it. To ensure all your accessibility tags, like headings and alt text, are preserved, you must use the correct export method:</p>
    <ul>
    <li>
    <p><strong>Avoid "Print to PDF": </strong>This function strips away the structural tags required for screen readers. (Tags provide the essential structure and semantics for a PDF, enabling screen reader navigation, defining logical reading order, and allowing content to reflow correctly on different devices.)</p>
    </li>
    <li>
    <p><strong>Save As/Download as PDF: </strong>In Microsoft Word or PowerPoint, use "Save As" and select the "Best for electronic distribution and accessibility" option. In Google Docs, use “File → Download → PDF Document” to generate a tagged file.</p>
    </li>
    <li>
    <p><strong>Verify Content: </strong>After exporting, perform a quick test to see if you can select the text. If you can, the text is searchable and accessible; if not, further work is needed.</p>
    </li>
    </ul>
    <h3><strong>3. Remediate Existing PDFs</strong></h3>
    <p>When an original source file isn't available, remediating an existing PDF ensures that all students, including those relying on screen readers or other assistive technologies, can engage with course materials seamlessly.</p>
    <ul>
    <li>
    <p><strong>Quick Fixes with Blackboard Ally:</strong> If your PDF is hosted in Blackboard, check Blackboard Ally first. Ally can resolve minor accessibility issues directly.</p>
    </li>
    <li>
    <p><strong>Comprehensive Remediation in Adobe Acrobat:</strong> For more complex documents, archived files, or scanned readings where you lack source files, Adobe Acrobat provides powerful remediation tools:</p>
    <ul>
    <li>
    <p><strong>Apply OCR (Optical Character Recognition):</strong> Convert image-based scanned pages into searchable, readable text so screen readers can process the content.</p>
    </li>
    <li>
    <p><strong>Run Accessibility Checks:</strong> Use the built-in Accessibility Checker to detect structural barriers, missing tags, alt text gaps, or form field labels.</p>
    </li>
    <li>
    <p><strong>Manually verify Reading Order:</strong> Use the Reading Order tool to ensure assistive technologies present the content in a logical sequence that supports understanding.</p>
    </li>
    <li>
    <p><strong>Export the PDF</strong>: Remediate with Microsoft Word or PowerPoint’s Accessibility Checker. Then, converting it back to a source format is often the easiest way to add clear headings, alt text, and structured lists using familiar editing tools.</p>
    </li>
    </ul>
    </li>
    </ul>
    <h3><strong>4. Prioritize What You Fix First</strong></h3>
    <p>Remediating all course PDFs simultaneously is not necessary. Instead, use the insights from your Blackboard Ally course report to determine where to start:</p>
    <ul>
    <li>
    <p><strong>Prioritize Required Materials: </strong>Focus on syllabi and required readings before optional handouts.</p>
    </li>
    <li>
    <p><strong>Target Low Scores: </strong>Address files with the lowest <a href="https://umbc.atlassian.net/wiki/x/CEPVAQ" rel="nofollow external" class="bo">Blackboard Ally Course scores</a> first to remove the most significant hurdles.</p>
    </li>
    <li>
    <p><strong>Actionable Elements: </strong>Ensure interactive elements like worksheets or forms are remediated so all students can participate.</p>
    </li>
    <li>
    <p><strong>Substitute When Needed: </strong>Replace uneditable files with accessible versions by collaborating with the UMBC Library or publishers.</p>
    </li>
    </ul>
    <p><strong> </strong></p>
    <p>For additional guidance, visit the UMBC Digital Accessibility website on <a href="https://accessibility.umbc.edu/digital-accessibility/accessible-documents-presentations/" rel="nofollow external" class="bo">Accessible Documents &amp; Presentations &gt; Specific tools used at UMBC &gt; PDFs</a> to discover further methods for formatting accessible PDF files.</p>
    </div>
]]>
</Body>
<Summary>PDFs are a staple of academic life, used for everything from syllabi to complex research articles. However, without intentional design, they can create significant barriers for students using...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/161221/guest@my.umbc.edu/daae62d02d587b274e639d8c0f2ee0ac/api/pixel</TrackingUrl>
<Tag>adobe-acrobat</Tag>
<Tag>ally</Tag>
<Tag>crutchfield</Tag>
<Tag>digital-accessibility</Tag>
<Tag>faculty</Tag>
<Tag>pdf</Tag>
<Tag>remediation</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://assets3-my.umbc.edu/system/shared/thumbnails/news/000/161/221/947bfc4139626776fbf85b85583077d2/xxlarge.jpg?1784660804</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/221/947bfc4139626776fbf85b85583077d2/xlarge.jpg?1784660804</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/161/221/947bfc4139626776fbf85b85583077d2/large.jpg?1784660804</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/161/221/947bfc4139626776fbf85b85583077d2/medium.jpg?1784660804</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/161/221/947bfc4139626776fbf85b85583077d2/small.jpg?1784660804</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/221/947bfc4139626776fbf85b85583077d2/xsmall.jpg?1784660804</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/161/221/947bfc4139626776fbf85b85583077d2/xxsmall.jpg?1784660804</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, 28 Jul 2026 12:15:00 -0400</PostedAt>
</NewsItem>

<NewsItem contentIssues="false" id="161203" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/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>8</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/veterans/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/veterans/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/veterans/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>

</News>
