Effective for content created or significantly updated on or after April 24, 2026
Use the University of Maryland, Baltimore (UMB) High-Risk Video Content Checklist to triage your existing videos that primarily live on YouTube or are embedded on the UMB website using another video player.
If videos are saved to a server or drive and need to be remediated or removed because they pose a high risk, create a folder labeled “Archive,” and place assets in the folder. Delete archived versions after they are remediated.
If the video is on YouTube or Vimeo and needs remediation or is high risk, change the video’s visibility to private until remediated. Delete the video if it is no longer needed, cannot be remediated, or when the remediated version is published.
Step 1
When was the content created?
- Created or significantly updated ON or AFTER April 24, 2026
- Must meet WCAG 2.1 Level AA before publication.
- If not compliant, do not publish.
- Created BEFORE April 24, 2026
- Proceed to Step 2.
Step 2
Is the content still publicly available?
- NO
- No action required unless republished.
- YES
- Proceed to Step 3.
Step 3
Is the content actively serving an institutional function?
Remediation is required ONLY if the content is publicly available AND at least one of the following applies:
- Embedded on an official UMB webpage
- Used for admissions recruitment
- Used for marketing or brand promotion
- Required for course participation
- Provides instructional material
- Provides tutorials or guides
- Explains access to student services
- Explains enrollment, housing, financial aid, or registration
- Actively promoted to students or redistributed by UMB
High-Priority Content Types (Mandatory Review if Step 3 Applies)
- Admissions recruitment videos
- Course lectures or recorded classes
- Student service tutorials
- Enrollment or financial aid explainers
- Research explainers with charts or statistics
- Videos embedded on official webpages
Step 4
Platform Risk Level (Additional Review for Content Identified in Step 3)
This step applies ONLY to content that triggered remediation under Step 3.
Platform presence alone does NOT require retroactive remediation of all legacy content.