Website Accessibility at UMBC

Accessible web content ensures that all users, including those using screen readers, keyboard navigation, or assistive technology, can interact with your website and digital content. At UMBC, this applies to both Sites@UMBC, myUMBC groups, and other platforms that present course, departmental, or university information.

Accessibility isn’t just a legal requirement—it’s part of inclusive, student-centered design. This page provides easy-to-follow guidance grounded in WCAG 2.1 standards and the POUR principles:

  • Perceivable: Everyone can perceive the content (e.g., text descriptions for images)
  • Operable: Everyone can navigate the site (e.g., keyboard friendly menus)
  • Understandable: Everyone can comprehend the information (e.g., clear instructions and consistent layout)
  • Robust: Everyone can use the site across different devices and technologies (e.g., follow HTML standards and semantic markup)

Common Accessibility Issues

Even with accessible templates, website editors must ensure that their content meets accessibility standards. Below are common content types and how to improve them.

  • Use heading levels in orderdon’t skip levels
  • Use headings to organize content for both sighted users and screen readers
  • Don’t simulate headers by resizing or bolding text

Quick Win: Start pages with a clear <h1> and use <h2> for major sections

  • Don’t rely on color alone to convey meaning (e.g., “Items in red are overdue”)
  • Ensure text contrast is at least 4.5:1 for body text
  • Use tools like the WebAIM Contrast Checker

Quick Win: Check your headings and buttons for contrast with the background. Review this handy guide to UMBC Brand Color Contrast combinations.

  • Use meaningful link text (e.g., “View our schedule” instead of “Click here”)
  • Avoid duplicate links with the same text that go to different places
  • Indicate when a link opens a new window or downloads a file

Quick Win: Hover over your links — do they make sense out of context?

  • Use tables only for data, not for layout
  • Never use images of tables — use the tables themselves to display data
  • Ensure tables read logically when linearized by screen readers
  • Include row and column headers with <th> tags
  • Sites and myUMBC do not support creating or editing tables, but you can use Tables Generator for HTML

Quick Win: Try reading your table aloud — does it make sense?

  • Images must have descriptions, even thumbnails and inline visuals. Not sure whether an image needs a description or if it should be marked decorative? Try this decision tree.
  • Avoid using text inside images since screen readers cannot interpret them.
  • Complex images (e.g., infographics, charts) should include a longer description or linked text alternative

Quick Win: Ask yourself, “What would I say if I were describing this image out loud?”

Adding descriptions to images in Sites@UMBC:

  • Option 1: Edit the page → click image → pencil icon → add alt text → update
  • Option 2: Go to Media → Library → select image → add description

Adding descriptions to images in myUMBC:

    • Edit the post or event
      • Thumbnail: Enter description
      • Inline image: Use “Add Alt Text” feature
    • Save!
    • Learn more with this FAQ.
  • All videos must include captions
  • Audio content should have transcripts
  • Avoid autoplay media or provide controls to stop it

Quick Win: Use our video capture platform’s auto-caption feature, then edit for accuracy. Note: UMBC uses Panopto through Dec 2025 and will start using YuJa in 2026.

  • Include a “Skip to Main Content” link at the top of each page
  • Ensure all interactive elements are accessible using the keyboard only
  • Avoid hover-only content (e.g., tooltips or dropdowns that don’t work with keyboard focus)

Quick Win: Try navigating your site using only the tab key

  • Label all form fields clearly
  • Provide instructions for completing the form (e.g., required fields)
  • Avoid placeholder-only labels — use actual visible labels

Quick Win: Use the preview mode and test your form with a screen reader

Using Accessibility Checkers

UMBC currently uses Acquia Optimize (Monsido) to check Sites@UMBC.

  • Focus on the Accessibility Checklist tab
  • Prioritize fixing issues related to images and files
  • Don’t panic if the Front-End template flags issues—those are usually out of your control
  • Request access via this online form using your myUMBC login.

Note: Monsido does not scan myUMBC pages — manual checks are necessary.

Additional Tips for Faculty & Staff

  • Use UMBC-branded templates when possible—they’re built with accessibility in mind
  • Always preview your content on mobile and with keyboard navigation
  • When embedding third-party content (e.g., Google Forms, embedded videos), make sure it’s accessible or provide alternatives
  • If you’re not sure how to fix something, reach out for help — you’re not alone!
  • Have a question or need support for web accessibility at UMBC? Email us at webaccessibility@umbc.edu

Resources

UMBC Training

External Resources

WebAIM (web accessibility in mind)

W3C.org