UMD Web Accessibility Guidelines


Table of contents

Overview 

The University of Maryland (University) is committed to ensuring that people with disabilities have equitable access to its programs, services, activities, information, and opportunities. This includes websites and web-based services used by students, employees, visitors, and the broader public.
The UMD Electronic Information, Communication, and Technology (EICT) Accessibility Policy establishes accessibility requirements for University web-based information, including conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA. These responsibilities apply whether websites are developed, managed, or updated by UMD units, third-party vendors, or both.
This document provides content stewards and web developers with introductory guidance for creating accessible websites and content, evaluating existing websites, and correcting accessibility barriers. It covers foundational practices, automated and manual evaluation, training, resources, and support. The WCAG 2 Checklist can help explain accessibility requirements and how they are evaluated. More comprehensive evaluations may require assistance from University web accessibility specialists or qualified third-party organizations.
Accessibility must be addressed from the beginning of a website project and maintained as content and functionality change. Evaluation must combine automated tools with manual testing and knowledgeable human review. Automated tools alone cannot determine whether a website meets accessibility standards.

Top

Websites developed or managed by third-party vendors

When hiring a vendor to build, redesign, manage, or maintain a website, units must work with Procurement to ensure accessibility requirements are included in the request for quotations or proposals (RFQ or RFP) and the contract. These requirements must address the work the vendor will perform, including design, development, content creation, and ongoing maintenance, as applicable.
The contract must identify the applicable accessibility standards, evaluation milestones, required testing documentation, and timelines for correcting both self-identified and UMD-identified barriers. It must require accessibility throughout the project, automated and manual testing during development, and correction of accessibility failures before final acceptance. Any contracted maintenance or content services must also preserve accessibility.
Website responsibilities may be shared: a vendor may build the website while a UMD unit manages its content, or a vendor may provide both technical and content services. Units must clearly document who is responsible for testing, correcting technical issues, maintaining accessible content, and addressing new barriers after launch. Using a vendor does not remove the unit’s responsibility for ensuring that its website remains accessible.
Work with Procurement to adapt and include a clause such as the following:

The <vendor name> must ensure that all website deliverables and services within the scope of this contract meet applicable requirements of the University of Maryland Electronic Information, Communication, and Technology (EICT) Accessibility Policy and conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA success criteria and conformance requirements. Accessibility must be incorporated from the start of the project and evaluated at agreed milestones and before final delivery. Evaluation must include automated and manual testing, including keyboard navigation, screen reader testing, and completion of essential user tasks. The vendor must provide written testing results, correct identified failures in its deliverables at no additional cost to the University, and verify corrections before final acceptance. During any contracted maintenance or content management period, vendor-provided updates and content must maintain accessibility. Accessibility defects within the vendor’s scope of responsibility must be corrected within timelines specified in the contract.

Top

Websites developed and managed by UMD units

Units that build and manage their own websites must incorporate accessibility into planning, design, development, content creation, and ongoing maintenance. Units must assign clear responsibilities for content and technical accessibility and ensure that the people performing this work have appropriate training and access to support.
Content stewards are responsible for creating and maintaining accessible content. Web developers are responsible for accessible templates, code, and interactive features, and for resolving technical barriers that content stewards cannot address. When one person performs both roles, both sets of responsibilities apply.
Units must conduct automated and manual evaluations during development, before launch, and as content or functionality changes. Testing must include essential user tasks across relevant browsers, devices, and assistive technologies. Identified barriers must be documented, assigned to the appropriate person or team, corrected, and retested. The following section describes the knowledge and skills expected of content stewards and web developers.

Top

Content stewards and web developers

The responsibilities described above depend on coordination between the people who maintain website content and those who manage its technical features. Whether these roles are performed by UMD personnel, vendors, or both, the following knowledge and skills support accessible websites. One person may perform both roles.

Top

Content stewards

Content stewards are instructors, staff, or other campus community members who create, add, or edit digital content using UMD web templates or out-of-the-box website-building platforms. Vendors may also perform this role when content services are included in their contracts.
Content stewards are responsible for applying foundational accessibility practices when creating and updating content. They do not need to resolve every technical issue, but they must recognize when a barrier requires assistance and refer it to the appropriate web developer or vendor. Using a template or website-building platform does not automatically ensure that content is accessible.
Content stewards should be able to apply the following practices:

  1. The University of Maryland’s Six Essential Steps: headings, links, color and contrast, images, tables, and media.
  2. Basic manual testing, including keyboard testing, navigation through common user tasks, and introductory screen reader testing.
  3. Basic automated testing, including the use of tools such as WAVE and Siteimprove.
  4. Interpretation of basic testing results, including how to correct identified content issues, prioritize significant accessibility barriers, and determine when assistance from a web developer or vendor is needed.
  5. Verification that content changes resolve identified barriers without introducing new issues.

Top

Web developers

Web developers are instructors, staff, or other members of the campus community who design, build, customize, or maintain websites, templates, and interactive components. Vendors may perform some or all of these functions, depending on the contract. Web developers may also serve as content stewards.
Web developers are responsible for applying accessibility standards throughout design, development, and maintenance and ensuring that websites work with keyboards, screen readers, and other assistive technologies. They should be able to interpret, implement, and remediate complex accessibility requirements while supporting content stewards with barriers they do not have the technical knowledge or authority to resolve. Developers should also provide accessible templates, components, and content-authoring tools and explain how content stewards can use them to maintain accessibility.
Web developers should be able to apply the following practices:

  1. The University of Maryland’s Six Essential Steps and the other foundational accessibility practices expected of content stewards.
  2. The creation of accessible interactive elements, such as menus and sliders, using appropriate HTML and WAI-ARIA when needed.
  3. The interpretation and remediation of complex accessibility issues that content stewards may not have the authority, access, or technical skills to resolve.
  4. The use of advanced automated testing tools, such as Lighthouse and Axe DevTools, combined with manual evaluation.
  5. Testing of keyboard navigation, screen reader interactions, forms, dynamic content, and essential user tasks across relevant browsers and devices.
  6. Documentation of findings, correction and retesting of technical barriers, and checks to ensure that updates preserve accessibility.

Top

Principles of web accessible design 

Web accessibility is often associated with development and the work completed in HTML, CSS, and JavaScript. However, digital accessibility should begin much earlier, during content creation and design. Planning for website accessibility from the start creates a better experience for everyone and reduces the need for remediation later.

Top

Six essential steps

The Six Essential Steps address common accessibility barriers and provide a foundation for creating accessible digital content. Although they are not a comprehensive list of accessibility requirements, they can help content creators, designers, and web developers build accessibility into their work and prioritize issues identified through testing.

  1. Headings - Organize content using properly formatted headings, such as H1, H2, and H3. Plan the heading structure early, follow a logical hierarchy, and do not select headings based only on their visual appearance or skip heading levels when organizing subsections. Learn more about semantic structure and headings.
  2. Links - Write meaningful link text that clearly describes the link’s destination or purpose. Avoid raw URLs and vague phrases such as “click here,” “read more,” “more,” or “continue.” Make links visually recognizable using more than color alone, such as an underline. Learn more about creating accessible links.
  3. Color Contrast - Ensure that text and meaningful visual elements have sufficient color contrast, paying particular attention to lighter shades of orange, yellow, and gray. Do not use color alone to communicate meaning; supplement it with labels, text, patterns, symbols, or other visual indicators. Use a color contrast checker to evaluate color combinations, and refer to guidance on using UMD Brand colors to ensure sufficient contrast.
  4. Images - Provide meaningful alternative text for images that communicate information, including photographs, illustrations, charts, and graphs. Avoid repeating information in alternative text when it is already provided in the surrounding content, and mark decorative images so assistive technologies can ignore them. Whenever possible, use actual text instead of images of text, because actual text is easier to enlarge, translate, customize, and read across devices.
  5. Tables - Use tables to present data, not to control page formatting or layout. Identify information using appropriate column and row headers, keep table structures simple, and avoid merging or splitting cells whenever possible.
  6. Media - Provide accurate captions for all videos and transcripts for audio-only content. Review automated captions for accuracy, punctuation, speaker identification, and synchronization. Include accessible controls that allow users to play, pause, stop, and adjust media.

Top

Page structure and visual design

  1. Reading Order - Arrange content so the reading order for screen reader users matches the intended visual order. Users should encounter headings, text, controls, and related content in a logical sequence that preserves the meaning and relationships presented visually.
  2. Typography - Use a font size that is comfortable to read without requiring users to zoom, and avoid lines of text that are too long or too short. Allow text to resize and reflow without losing information, obscuring content, or limiting functionality. While both sans-serif and serif fonts may be accessible, use of sans-serif fonts where possible is recommended.

Top

Navigation and interactive features

  1. Keyboard Access - Ensure that all interactive elements can be reached and operated using a keyboard. Provide a clear, visible focus indicator so users can identify which element currently has keyboard focus. Include a keyboard-accessible Skip to Main Content Link near the beginning of each page.
  2. Forms - Ensure that form controls include descriptive labels, clear instructions, and helpful error messages. Clearly identify required fields and errors using text or other indicators rather than relying on color alone.
  3. Components - Ensure that dialogs, menus, tooltips, carousels, and other interactive components are understandable and operable using a keyboard and assistive technologies. Clearly communicate each component’s name, purpose, current state, and available controls.
  4. Motion - Avoid unnecessary or distracting movement and provide controls that allow users to pause, stop, or hide moving or automatically updating content. Do not use flashing content that could trigger seizures or other physical reactions.

Top

UMD website requirements

  1. Accessibility Link - Add the Web Accessibility link to the footer of every website. Use clear, descriptive link text, such as “Web Accessibility,” and ensure that the link is easy to find, visually recognizable, and accessible by keyboard. The link should appear consistently across all pages and direct users to the University’s web accessibility information and resources.
  2. UMD Header - Use the UMD header to provide a consistent university identity and navigation experience across UMD websites. Follow the official guidelines for the header’s content, branding, placement, spacing, and responsive behavior. Ensure that the header remains accessible on different screen sizes and that all links, menus, and interactive controls can be operated using a keyboard and assistive technologies.

Top

Web accessibility evaluation

Web accessibility evaluation, also called assessment, audit, or testing, helps identify accessibility barriers in websites and web applications. This section covers both automated evaluation, which uses tools to detect certain accessibility issues, and manual evaluation, which checks aspects that require human judgment, such as keyboard navigation, screen reader usability, and whether alternative text conveys meaningful information. Both methods are needed because automated tools alone cannot determine whether a website or application is fully accessible.

Automated evaluation

Web accessibility evaluation tools are software programs or online services that help determine if web content meets accessibility standards. 

Evaluation tools 

The Division of IT supports the following tools at the University of Maryland:

  1. Siteimprove: A web governance software offered by the University of Maryland enables users to test websites under the umd.edu domain for accessibility compliance, errors, and best practices. Siteimprove has a comprehensive accessibility module that allows for automated checking and management of various issues that can make your web page non-compliant. You may also use the Siteimprove browser extension for Chrome and Firefox to evaluate pages behind authentication and for quick one-page checks. Visit the Siteimprove help center for more information.
  2. WAVE Firefox and Chrome extensions generate an instant overview of potential accessibility issues on a page. It is available for testing accessibility directly in your web browser — handy for checking password-protected pages, locally stored pages, or highly dynamic pages. Learn how to use Wave.
  3. Web Developers may explore other web accessibility evaluation tools such as Axe by Deque, ANDI, and Lighthouse. 

Areas to check with automated tools 

Use the automatic accessibility tools to evaluate the following:

  1. Page title - Ensure the page title is descriptive and succinct.
  2. Image text alternatives ("alt text") (pictures, illustrations, charts, etc.)
  3. Semantic Structure: Regions, Headings, and Lists
  4. Color and contrast
  5. Links and Hypertext
  6. Fonts
  7. Tables

Top

Manual evaluation

Manual evaluation is fundamental to ensuring accessibility and usability for everyone, especially people who use assistive technologies such as screen readers, operate a computer using only a keyboard, or require captions for video content. Complete the following checks to identify barriers that automated testing tools may not detect.

Site functionality and user tasks

Start by identifying the main activities users need to complete, such as finding information, registering for an event, submitting a form, or accessing course materials. A user journey is the sequence of steps a person takes to complete an activity, from finding the starting point to receiving confirmation that the task is complete.
Test each journey from beginning to end, including any linked pages, documents, or external services needed to complete it. Confirm that users can:

Record where users encounter barriers, cannot proceed independently, or lose access to information or functionality. Use these findings to guide corrections and repeat the affected journey after changes are made.

Keyboard navigation and focus

Include a Skip Navigation” link when a page contains repetitive navigation items. The link should allow users to bypass the navigation and move directly to the main content area.

Keyboard accessibility is one of the most important aspects of web accessibility because many people rely on a keyboard instead of a mouse to navigate and interact with digital content. All links, buttons, menus, form controls, dialogs, and other interactive elements must be reachable and operable using only a keyboard. Important steps:

Screen reader testing

Test the website with a screen reader. WebAIM provides tutorials for JAWS and NVDA on Windows, and VoiceOver on macOS. NVDA is free to download for all users, and VoiceOver is available to all Mac users through their accessibility settings. Eligible users may also access the University of Maryland’s free JAWS license for home use.

Forms and web vomponents 

Review other web components using the following resources:

Text Resizing and responsive layout

Follow best practices for resizing text and evaluate the website at different zoom levels and screen sizes. Complete the following steps:

Multimedia accessibility

Determine whether video and multimedia content requires captions, transcripts, or audio descriptions.

Document accessibility

Documents linked to or embedded in a website must be accessible. This includes PDFs, Word documents, presentations, spreadsheets, and other downloadable materials.

Whenever possible, correct issues in the source file and check accessibility again after exporting or converting it. For detailed instructions, refer to the University Document Accessibility Guidelines.

Top

Cross-browser and mobile testing 

Test the website using major browsers, including Chrome, Firefox, Safari, and Microsoft Edge, as well as different mobile devices and operating systems. Common accessibility features, such as keyboard commands, focus indicators, caption rendering, and screen reader support, may behave differently across browsers and devices. If the website must support legacy systems, include Internet Explorer in the testing plan. Confirm that content, navigation, interactive components, and assistive technologies function consistently across all supported environments.

Top

Archived web content exemption

When the exemption applies

Under the University of Maryland EICT Accessibility Policy, some older web content may qualify as archived and may not be required to meet WCAG 2.1 Level A and AA. 
Content qualifies as archived only when all four conditions below are met:

  1. It was created before April 26, 2027, or reproduces physical media created before that date.
  2. It is kept only for reference, research, or recordkeeping.
  3. It is not altered or updated after it is archived.
  4. It is organized and stored in an area clearly identified as an archive.

When the exemption does not apply

The exemption does not apply when content created before the deadline is used to participate in a current service, program, or activity. For example, a form needed for a current program must be accessible even if it was created before the cutoff date. Historic material placed on a new website must also be accessible when it is part of a current offering.

Archiving requirements

Note: An accessible version may still need to be provided when requested by an individual with a disability, even when the archived-content exception applies.

Top

Support

Top

Revision history 

Version 1 - Published on 9/28/2026