<?xml version="1.0"?>
<News hasArchived="false" page="2" pageCount="108" pageSize="10" timestamp="Sat, 29 Aug 2026 05:07:51 -0400" url="https://my3.my.umbc.edu/groups/veterans/posts.xml?mode=pawpularity&amp;page=2">
<NewsItem contentIssues="false" id="161127" important="true" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/161127">
<Title>Service Alert: DocuSign Temporarily Unavailable</Title>
<Body>
<![CDATA[
    <div class="html-content">
    <p><strong>Affected Service:</strong> DocuSign</p>
    <p><strong>Time Identified:</strong> 10:00 AM | July 16, 2026</p>
    <p>Please be advised that DocuSign is currently experiencing a temporary service outage.</p>
    <ul>
    <li>
    <p><strong>The Impact:</strong> Users may be unable to log in, send, or sign electronic documents at this time.</p>
    </li>
    <li>
    <p><strong>Our Action: </strong>The Division of Information Technology is actively working to resolve the issue and restore full services as swiftly as possible. We are monitoring the situation closely and will provide status updates as soon as more information is available.</p>
    </li>
    </ul>
    <p>Thank you for your patience and understanding.</p>
    </div>
]]>
</Body>
<Summary>Affected Service: DocuSign   Time Identified: 10:00 AM | July 16, 2026   Please be advised that DocuSign is currently experiencing a temporary service outage.       The Impact: Users may be unable...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/161127/guest@my.umbc.edu/687cd89c27590c1642de7a68963feeb4/api/pixel</TrackingUrl>
<Tag>alert</Tag>
<Tag>docusign</Tag>
<Tag>system</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/161/127/f3e9c2f56caaa82a0466dffc48c238b8/xxlarge.jpg?1784210800</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/161/127/f3e9c2f56caaa82a0466dffc48c238b8/xlarge.jpg?1784210800</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/161/127/f3e9c2f56caaa82a0466dffc48c238b8/large.jpg?1784210800</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/161/127/f3e9c2f56caaa82a0466dffc48c238b8/medium.jpg?1784210800</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/161/127/f3e9c2f56caaa82a0466dffc48c238b8/small.jpg?1784210800</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/161/127/f3e9c2f56caaa82a0466dffc48c238b8/xsmall.jpg?1784210800</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/161/127/f3e9c2f56caaa82a0466dffc48c238b8/xxsmall.jpg?1784210800</ThumbnailUrl>
<ThumbnailAltText>U-M-B-C shield with the text "DoIT System Update"</ThumbnailAltText>
<PawCount>1</PawCount>
<CommentCount>1</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Thu, 16 Jul 2026 10:25:35 -0400</PostedAt>
<EditAt>Thu, 16 Jul 2026 10:35:59 -0400</EditAt>
</NewsItem>

<NewsItem contentIssues="false" id="160758" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/160758">
<Title>Instructional Technology Team Honored with 2026 Blackboard Catalyst Award</Title>
<Tagline>UMBC's accessibility work recognized nationally</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>UMBC's Instructional Technology team has been recognized as <a href="https://blackboard.com/catalyst-awards" rel="nofollow external" class="bo">a winner of a 2026 Blackboard Catalyst Award for Training &amp; Professional Development</a>, honoring the institution's leadership in advancing innovative, impactful, and student-centered educational experiences through technology. </p>
    <p>The Catalyst award recognizes UMBC's <strong>Course Roadmap to Equity (CoRE)</strong>, a phased digital accessibility initiative designed to build lasting faculty competency through a combination of live professional development and a structured, self-paced microcredential. Designed to model the very standards it teaches, CoRE treats accessibility not as a compliance checkbox, but as a genuine equity commitment to student success.</p>
    <p><strong>Congratulations to Mariann Hawken, Josh Abrams, Susan Biro, Ada Crutchfield, Ben Amudzi, and Peter Ariev.</strong></p>
    <p>The CoRE initiative launched in Summer 2025 with a two-day Digital Accessibility Summer Camp for faculty and staff, followed by a live workshop series in Fall 2025 that reached more than 350 participants. CoRE workshops invited faculty to generate Blackboard Ally accessibility reports for their own courses in real time, creating immediate, personal motivation to act. By mid-Spring 2026, the program expanded to include customized department-level training and a microcredential, CoRE Foundations, with more than 250 faculty enrolled.</p>
    <blockquote>
    <p>"Digital accessibility has to be woven into how we teach and how we build our instructional materials,” says Mariann Hawken, Director of Instructional Technology. “CoRE gives faculty the tools and the time to make that shift, and the data show they're doing exactly that."</p>
    </blockquote>
    <p>The results have been measurable and significant. UMBC's institutional Ally accessibility score rose from 66.5% to 78.7% -- a 12.2-point gain between Spring 2025 and Spring 2026. Faculty use of Ally's feedback tools grew dramatically over the same period. Courses actively making accessibility fixes increased tenfold, and the number of individual fixes made grew from 378 to nearly 7,000. Scanned PDFs decreased by 41%, and images missing descriptions dropped by 36% -- reflecting faculty applying exactly the remediation skills CoRE taught.</p>
    <p>CoRE is built in phases, with peer mentoring and a student-facing track still ahead. Phase 4, launching Fall 2026, envisions CoRE Peer Mentors embedded in departments and colleges across campus, an approach that mirrors <a href="https://doit.umbc.edu/news/post/126203/" rel="nofollow external" class="bo">UMBC's earlier Catalyst Award-winning PIVOT program for pandemic-era faculty development</a>. By Spring 2027, the program envisions extending training to students, recognizing that accessibility is a shared responsibility across the entire university community.</p>
    <p>UMBC is among thirty institutions across eight countries recognized this year, selected from 136 submissions representing 19 countries, one of the most competitive pools in the program's history. Presented annually by Blackboard, the Catalyst Awards celebrate institutions and individuals who use Blackboard solutions to drive meaningful change in teaching, learning, accessibility, engagement, and institutional success. The Training &amp; Professional Development Award specifically recognizes those who use the Blackboard LMS to elevate training for educators and staff, strengthening skills and supporting successful technology adoption.</p>
    <blockquote>
    <p>"We're inspired by the institutions and educators recognized through this year's Catalyst Awards," said Bruce Dahlgren, CEO of Blackboard. "These winners represent the very best of innovation, collaboration, and commitment to learner success."</p>
    </blockquote>
    <p>To learn more about the Catalyst Awards and see the full list of 2026 winners, visit <a href="https://blackboard.com/catalyst-awards" rel="nofollow external" class="bo">blackboard.com/catalyst-awards</a>.</p>
    <p><strong><br><br><br></strong></p>
    </div>
]]>
</Body>
<Summary>UMBC's Instructional Technology team has been recognized as a winner of a 2026 Blackboard Catalyst Award for Training &amp; Professional Development, honoring the institution's leadership in...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/160758/guest@my.umbc.edu/513f9433cb9317ff468b598c2fe2a6d7/api/pixel</TrackingUrl>
<Tag>awards</Tag>
<Tag>instruction</Tag>
<Tag>itnm</Tag>
<Tag>success</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/160/758/a9fcb43683fd26823b3280db816335fe/xxlarge.jpg?1781808831</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/160/758/a9fcb43683fd26823b3280db816335fe/xlarge.jpg?1781808831</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/758/a9fcb43683fd26823b3280db816335fe/large.jpg?1781808831</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/160/758/a9fcb43683fd26823b3280db816335fe/medium.jpg?1781808831</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/758/a9fcb43683fd26823b3280db816335fe/small.jpg?1781808831</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/758/a9fcb43683fd26823b3280db816335fe/xsmall.jpg?1781808831</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/758/a9fcb43683fd26823b3280db816335fe/xxsmall.jpg?1781808831</ThumbnailUrl>
<ThumbnailAltText>Sleek white text "2026 Catalyst Awards" on a dark blue background</ThumbnailAltText>
<PawCount>11</PawCount>
<CommentCount>1</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Wed, 15 Jul 2026 16:16:52 -0400</PostedAt>
</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="161041" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/161041">
<Title>Elevate Your Impact: USM Champions Accessibility and Fall Prep</Title>
<Tagline>USM Accessibility in Action - July 2026 Issue</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>Welcome to July's edition of USM Accessibility in Action! This month, we're celebrating USM excellence and helping you strengthen one of the most fundamental accessibility skills: writing meaningful alt text.</p>
    
    <h4><strong>Celebrating USM Excellence: Two Blackboard Catalyst Awards</strong></h4>
    
    <p>We're excited to celebrate two University System of Maryland institutions recognized with 2026 Blackboard Catalyst Awards for their outstanding leadership in accessibility and professional development.</p>
    
    <p><strong>Coppin State University</strong> won the Innovation in Accessibility Award for the Innovation, Development, Education, and Assessment (IDEA) Team. Coppin's IDEA Team exemplifies institutional leadership in accessibility by transforming inclusive design into a sustained campus practice through strategic use of Blackboard Ultra and Ally. Rather than approaching accessibility as a compliance obligation, the team embedded it into everyday teaching and learning, equipping faculty to create accessible, engaging learning environments as a standard expectation. Through sustained professional development and cross-campus collaboration, the team built a proactive and durable culture of accessibility. By extending this work into ADA Title II readiness, the IDEA Team has established a scalable, high-impact model that removes barriers, strengthens student success, and sets a compelling benchmark for accessibility leadership in higher education.</p>
    <p><strong>UMBC</strong> received the Training and Professional Development Award for the Course Roadmap to Equity (CoRE) initiative. This phased digital accessibility program builds lasting faculty competency through live professional development and a structured self-paced microcredential in Blackboard. Recognizing accessibility as both a legal obligation and an equity imperative, UMBC designed CoRE to meet faculty where they are, offering flexible pathways for varying schedules and expertise levels. In Fall 2025, 350+ faculty and staff attended live workshops and used Blackboard Ally to generate accessibility reports. Institutional Ally accessibility scores rose from 66.5% to 78.7%—a 12.2 point gain. Results directly informed the CoRE microcredential program with multiple pathways and achievements, recognizing faculty commitment to equitable course design.</p>
    <p>These awards reflect the innovative, equity-centered work happening across USM and they show what’s possible when accessibility becomes a shared institutional priority. Congratulations to both teams!</p>
    <p> </p>
    <h4><strong>Register Now: Ready, Set, Accessible Fall Course Prep Day</strong></h4>
    
    <p><strong>Monday, August 3, 2026 | 9:30 AM-12:30 PM ET | Zoom</strong></p>
    <p>Start the fall semester with course materials that are more accessible, usable, and inclusive for all learners. This half-day virtual event is designed to help faculty take practical, manageable steps to improve the accessibility of their courses before classes begin.</p>
    <p>Across three focused sessions, participants will learn how to:</p>
    <ul>
    <li>
    <p>Evaluate course resources for accessibility</p>
    </li>
    <li>
    <p>Redesign assignments with accessibility in mind</p>
    </li>
    <li>
    <p>Design learning experiences that support students with a range of sensory, cognitive, technological, and learning needs</p>
    </li>
    </ul>
    <p>Whether you're updating an existing course, preparing new materials, or looking for a realistic place to begin, this day will offer concrete strategies, examples, and tools you can apply right away. Faculty are invited to attend one session or participate in the full half-day event.</p>
    <p><a href="https://us.list-manage.com/bSYZkCKNr4K?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Register Now</a> </p>
    <h4></h4>
    <h4><strong>July Challenge: Alt Text in Action</strong></h4>
    
    <p>This month, practice writing meaningful alternative text for images in your materials. To help you master this skill, we recommend exploring this comprehensive <a href="https://us.list-manage.com/IvvA6OuovaF?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Guide to Writing Meaningful Alt Text</a> from Section508.gov.</p>
    
    <h5><strong>Quick Tips for Success:</strong></h5>
    <ul>
    <li>
    <p><strong>Focus on Meaning, Not Appearance:</strong> Instead of describing what an image looks like (e.g., "A person in a suit"), describe the information it conveys (e.g., "Dr. Martin Luther King Jr.").</p>
    </li>
    <li>
    <p><strong>Include Text Word-for-Word:</strong> If an image contains text (like an event flyer), that text must be included in the alt text so screen reader users don't miss vital details.</p>
    </li>
    <li>
    <p><strong>Context is Key:</strong> A photo of a building might need different alt text in a History course than it does in an Architecture course. Ask yourself: <em>What would a user miss if this image didn't load?</em></p>
    </li>
    <li>
    <p><strong>Don't Repeat Yourself:</strong> If the surrounding paragraph already explains the chart's data, your alt text can be brief. Just ensure it still identifies the image’s purpose so screen reader users know what the object is.</p>
    </li>
    </ul>
    <p><strong>The Challenge:</strong> Choose 3–5 images in your own materials and update their alt text using these principles. You’ll likely find that clarifying your images for accessibility actually makes your core concepts clearer for everyone! Post your insights on LinkedIn using #USMAccessibility so we can all learn from each other.</p>
    <p> </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/10kh7F58C06?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">Register for Ready, Set, Accessible Fall Course Prep Day</a></p>
    <p><a href="https://us.list-manage.com/IJrl_YBZuzg?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/gvWrMyyL4ZX?e=5395a9856c&amp;c2id=469e9338bc69d64837a2e6b22d7d387d" rel="nofollow external" class="bo">USM Digital Accessibility Hub</a></p>
    
    
    <p><strong>Repost from the USM Kirwan Center for Academic Innovation and the USM Digital Accessibility Work Group</strong>.</p>
    </div>
]]>
</Body>
<Summary>Welcome to July's edition of USM Accessibility in Action! This month, we're celebrating USM excellence and helping you strengthen one of the most fundamental accessibility skills: writing...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/161041/guest@my.umbc.edu/c5ae029238543caca5960d28ce055b1b/api/pixel</TrackingUrl>
<Tag>accessibility</Tag>
<Tag>award</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>
<PawCount>3</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Thu, 09 Jul 2026 12:11:59 -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>

<NewsItem contentIssues="false" id="160715" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/160715">
<Title>Gritty Excellence: Celebrating the Analytics &amp; Business Intelligence Student Team</Title>
<Tagline>From Ground Zero to Tableau Heroes</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>In any major IT modernization project, the secret ingredient isn't just the technology; it’s the grit of the people behind the screens. This spring, the Division of Information Technology (DoIT) is proud to present the <strong>Spring 2026 DoIT Gritty Award to the Analytics &amp; Business Intelligence Student Team</strong>. Please join us in celebrating this outstanding group of student innovators: Amaya Levine, Ling Zhang, Naba Waseem, Pratik Cholkhane, Soumya Bhate, and Sydnee Angus.</p>
    <h3><strong>Tackling a Monumental Migration</strong></h3>
    <p>The team was nominated for their relentless work on a massive, business-critical project: migrating the university's existing REX reports over to Tableau. They have completed over 170+ reports and have over 100 reports in active development. Transitioning nearly 300 intricate reports is no small feat for seasoned professionals, let alone a student team. Yet, this group stepped up to the plate and completely owned the challenge.</p>
    <h3><strong>Embracing the Steep Learning Curve</strong></h3>
    <p>What makes their achievement truly "gritty" is where they started. The team began this initiative with minimal prior knowledge of Tableau. To succeed, they had to simultaneously master a complex new software platform <em>and</em> reverse-engineer how the legacy REX reports functioned under the hood.</p>
    <p>According to their nominator, the team’s attitude has been the cornerstone of the project's success:</p>
    <blockquote>
    <p><strong>"They have been extremely patient through our trial-and-error process with some of these conversions, and they never hesitate to research how to make the reports work the way we need them to."</strong></p>
    </blockquote>
    <h3><strong>A Culture of Collaboration</strong></h3>
    <p>Beyond their technical stamina, the Analytics &amp; Business Intelligence Student Team exemplifies what it means to be a community. Instead of working in silos, these students constantly lean on and support one another. They have actively championed knowledge-sharing across DoIT, with many team members participating in "Lunch and Learns" to present their findings and teach others the Tableau tricks they've picked up along the way.</p>
    <h3><strong>Thank You, Team!</strong></h3>
    <p>A migration of this magnitude is a massive undertaking, and DoIT is incredibly thankful for the dedication, patience, and brilliant problem-solving this team brings to the office every single day.</p>
    <p>Congratulations to<strong> Amaya, Ling, Naba, Pratik, Soumya, and Sydnee</strong>! Thank you for showing us all what true grit looks like.</p>
    <h3><strong>About the DoIT Gritty Award</strong></h3>
    <p>The Gritty Award recognizes outstanding work within the Division and beyond. Full-time employees, student employees, and teams are all eligible. Do you know someone going above and beyond? <a href="https://forms.gle/AQjD2EvnWAQj9Kfa9" rel="nofollow external" class="bo"><strong>Complete the Gritty Nomination Form today!</strong></a></p>
    </div>
]]>
</Body>
<Summary>In any major IT modernization project, the secret ingredient isn't just the technology; it’s the grit of the people behind the screens. This spring, the Division of Information Technology (DoIT)...</Summary>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/160715/guest@my.umbc.edu/1c0d5fe7348fa7f9439d75c160cfe7dd/api/pixel</TrackingUrl>
<Tag>analytics</Tag>
<Tag>gritty</Tag>
<Tag>success</Tag>
<Tag>tableau</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/715/9fb1a468bff6ba161447e538787b124b/xxlarge.jpg?1781626393</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/thumbnails/news/000/160/715/9fb1a468bff6ba161447e538787b124b/xlarge.jpg?1781626393</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/715/9fb1a468bff6ba161447e538787b124b/large.jpg?1781626393</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/715/9fb1a468bff6ba161447e538787b124b/medium.jpg?1781626393</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets4-my.umbc.edu/system/shared/thumbnails/news/000/160/715/9fb1a468bff6ba161447e538787b124b/small.jpg?1781626393</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/715/9fb1a468bff6ba161447e538787b124b/xsmall.jpg?1781626393</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/715/9fb1a468bff6ba161447e538787b124b/xxsmall.jpg?1781626393</ThumbnailUrl>
<ThumbnailAltText>Gold star on a black background with the U-M-B-C shield in the center and the text "D-O-I-T Gritty Award"</ThumbnailAltText>
<PawCount>2</PawCount>
<CommentCount>1</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Wed, 24 Jun 2026 09:00:00 -0400</PostedAt>
</NewsItem>

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

<NewsItem contentIssues="false" id="160806" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/160806">
<Title>DoIT's Technology Support Center Hiring for the Fall</Title>
<Tagline>Are you looking for a part-time job? Come work for us!</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>The DoIT Technology Support Center is looking to hire additional student consultants to work during the upcoming semester and beyond. Please see our job description below and visit our job posting on <a href="https://app.joinhandshake.com/emp/employers/796884" rel="nofollow external" class="bo">Handshake</a> to apply. (Search for DoIT Technology Support Center Student Consultant.) The application will be open until July 18, 2026.</p>
    <h3>TSC Student Consultant Job Description</h3>
    <p>Technology Support Center (TSC) student consultants are the first points of technical contact for the UMBC community and those who do well often go on to work in other areas of the Division of Information Technology (DoIT). Minimally, consultants are expected to provide initial triage and support for a wide range of information technologies including accounts, hardware, instructional technologies, networking, software, telecommunications, and basic web development.</p>
    <h4>Responsibilities include, but are not limited to the following:</h4>
    <ul>
    <li>Provide technical assistance to users by phone and online;</li>
    <li>Answer TSC phones in a professional and courteous manner;</li>
    <li>Create, update and resolve tickets in the Request Tracker (RT) ticketing system;</li>
    <li>Create, update, suggest and recommend relevant FAQ articles to users (<a href="http://www.umbc.edu/faq">www.umbc.edu/faq</a>);</li>
    <li>Provide direct assistance to users on technical issues they cannot easily resolve on their own;</li>
    <li>Respond to all work-related communications in a timely manner;</li>
    <li>Escalate urgent problems to the Full-Time staff, as appropriate.</li>
    </ul>
    <h4>Required Skills and Experience</h4>
    <ul>
    <li>Demonstrated ability to effectively communicate by phone or in writing.</li>
    <li>Demonstrated writing ability.</li>
    <li>Demonstrated ability to achieve successful outcomes in handling difficult situations and customers.</li>
    <li>Demonstrated analytical and troubleshooting skills.</li>
    <li>Ability &amp; willingness to learn coupled with a clear understanding of one’s technical abilities, so as to triage and escalate an issue that leads to an effective solution for the user.</li>
    </ul>
    <p></p>
    </div>
]]>
</Body>
<Summary>The DoIT Technology Support Center is looking to hire additional student consultants to work during the upcoming semester and beyond. Please see our job description below and visit our job posting...</Summary>
<Website>https://doit.umbc.edu/about/jobs/</Website>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/160806/guest@my.umbc.edu/47642ce2cd87ce9e916d6e212a99c08f/api/pixel</TrackingUrl>
<Tag>job</Tag>
<Tag>tsc</Tag>
<Group token="doit">Division of Information Technology (DoIT)</Group>
<GroupUrl>https://my3.my.umbc.edu/groups/doit</GroupUrl>
<AvatarUrl>https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="original">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/original.JPG?1727453227</AvatarUrl>
<AvatarUrl size="xxlarge">https://assets1-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="xlarge">https://assets3-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xlarge.png?1727453227</AvatarUrl>
<AvatarUrl size="large">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/large.png?1727453227</AvatarUrl>
<AvatarUrl size="medium">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/medium.png?1727453227</AvatarUrl>
<AvatarUrl size="small">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/small.png?1727453227</AvatarUrl>
<AvatarUrl size="xsmall">https://assets2-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xsmall.png?1727453227</AvatarUrl>
<AvatarUrl size="xxsmall">https://assets4-my.umbc.edu/system/shared/avatars/groups/000/000/021/d27760c5de12c74b73faec8d0e631acf/xxsmall.png?1727453227</AvatarUrl>
<Sponsor>Division of Information Technology (DoIT)</Sponsor>
<ThumbnailUrl size="xxlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/806/7d943db53e1b602331285961a1b5ee47/xxlarge.jpg?1782224149</ThumbnailUrl>
<ThumbnailUrl size="xlarge">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/806/7d943db53e1b602331285961a1b5ee47/xlarge.jpg?1782224149</ThumbnailUrl>
<ThumbnailUrl size="large">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/806/7d943db53e1b602331285961a1b5ee47/large.jpg?1782224149</ThumbnailUrl>
<ThumbnailUrl size="medium">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/806/7d943db53e1b602331285961a1b5ee47/medium.jpg?1782224149</ThumbnailUrl>
<ThumbnailUrl size="small">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/806/7d943db53e1b602331285961a1b5ee47/small.jpg?1782224149</ThumbnailUrl>
<ThumbnailUrl size="xsmall">https://assets1-my.umbc.edu/system/shared/thumbnails/news/000/160/806/7d943db53e1b602331285961a1b5ee47/xsmall.jpg?1782224149</ThumbnailUrl>
<ThumbnailUrl size="xxsmall">https://assets2-my.umbc.edu/system/shared/thumbnails/news/000/160/806/7d943db53e1b602331285961a1b5ee47/xxsmall.jpg?1782224149</ThumbnailUrl>
<ThumbnailAltText>Picture of the front of the Engineering Building at an angle</ThumbnailAltText>
<PawCount>0</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>false</CommentsAllowed>
<PostedAt>Tue, 23 Jun 2026 10:18:31 -0400</PostedAt>
</NewsItem>

<NewsItem contentIssues="false" id="160630" important="false" status="posted" url="https://my3.my.umbc.edu/groups/veterans/posts/160630">
<Title>Strengthening Our Campus Safety: New myUMBC Features</Title>
<Tagline>A simpler way to manage your emergency alerts and contacts</Tagline>
<Body>
<![CDATA[
    <div class="html-content">
    <p>DoIT has been working with the Division of Student Affairs to introduce a new, easy-to-use <strong>Emergency Settings </strong>page in myUMBC. </p>
    <p>The myUMBC Emergency Settings page integrates our campus-wide emergency alert system and required emergency contact information in one place. You may notice new homepage reminders - these will guide you to sign up for emergency alerts or update your required emergency contact information. When you log in, you may see two specific notifications:</p>
    <ul>
    <li>
    <p><img src="https://my3.my.umbc.edu/inline_images/news/160630/64321" alt="Emergency Settings page with red alerts prompting users to sign up for emergency alerts" style="max-width: 100%; height: auto;"><strong>Emergency Alerts:</strong> If you haven't signed up, you’ll see a prompt to join. </p>
    </li>
    <li>
    <p><strong>Emergency Contacts: </strong>If your contacts are missing, you'll see a reminder. This notification will remain active until a contact is added.</p>
    </li>
    </ul>
    <p><strong>Take Action: </strong>Click the notification to go directly to your settings, or access them anytime by clicking your Profile Photo &gt; Emergency. See “<a href="https://umbc.atlassian.net/wiki/pages/resumedraft.action?draftId=2124840961&amp;draftShareId=0842e2d3-65fe-4f2d-946e-eec1642293c5" rel="nofollow external" class="bo">How do I update my Emergency Settings in myUMBC?</a>” for more information about the page.</p>
    <p>Please take a moment today to ensure your emergency alert enrollment is active and your emergency contacts are up to date. </p>
    <p>If you have any issues, please contact the Technology Support Center via <a href="https://help.umbc.edu" rel="nofollow external" class="bo">help.umbc.edu</a> or by calling 410-455-3838.</p>
    </div>
]]>
</Body>
<Summary>DoIT has been working with the Division of Student Affairs to introduce a new, easy-to-use Emergency Settings page in myUMBC.    The myUMBC Emergency Settings page integrates our campus-wide...</Summary>
<AttachmentKind>Inline Image</AttachmentKind>
<AttachmentUrl>https://assets1-my.umbc.edu/system/shared/attachments/ac6cf784deafd497c7e9a42b2ed0f303/6a92a167/news/000/160/630/09ad6b97b47773d7ff7f499daf333174/mceclip0.png?1781719581</AttachmentUrl>
<Attachments>
<Attachment kind="Inline Image" url="https://my3.my.umbc.edu/groups/veterans/posts/160630/attachments/64321"></Attachment>
</Attachments>
<TrackingUrl>https://my3.my.umbc.edu/api/v0/pixel/news/160630/guest@my.umbc.edu/c32a7f9ba0d9c955da89549b18c8db10/api/pixel</TrackingUrl>
<Tag>myumbc</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>
<PawCount>0</PawCount>
<CommentCount>0</CommentCount>
<CommentsAllowed>true</CommentsAllowed>
<PostedAt>Thu, 18 Jun 2026 13:00:00 -0400</PostedAt>
</NewsItem>

</News>
