Checklist for Captioning Compliance

The following types of videos should be captioned to promote access by everyone:

  • Videos on any of our University websites;
  • Videos used in a classroom setting;
  • Recorded lectures used as reference materials by students; and
  • Additional reference materials presented in class or for assignments (even for extra credit).


Examples of videos include, but are not limited to:

  • Videos created by instructors
  • Any videos used by guest lecturers
  • Any videos used in student presentations
  • Lecture captures
    • Regular lectures
    • Online workshops
    • Workshops
    • Presentations
  • Videos created by others and used in classes
    • Links to web videos (e.g. YouTube)
    • Films on course reserves
  • Supplemental materials
  • Videos posted on websites
    • Departmental
    • Research groups and labs
    • Class websites
  • Recordings of live streamed events
    • Webinars and workshops
    • Video conferences within a course

Achieving compliance

At Texas A&M University, we strive to meet WCAG 2.0 Level AA compliance. If you can answer "yes" to the following questions, your multimedia should be compliant with those guidelines.

  • Can the video player be activated and operated via the keyboard?
  • Does the video only start at the user request (will not start automatically)? If no, can the user stop it?
  • Can the video volume be modified (preferably by keyboard)?
  • Is the video available when Flash and/or style sheets is disabled?
  • If links are in the video, are the links descriptive?
  • Is the video free of flashing content faster than three times per second?
  • Does the video have a text transcript that provides equivalent information to the video?
  • Is the video transcript accessible and located in close proximity to the video?
  • Do captions include all dialogue and audio descriptions that sync with the video?
  • Is the color contrast of the video captions sufficient?

Did you know?

  • In the United States, about 55 million people have a disability (src: 2010 U.S. Census).
  • About 1 in 5 Americans have some kind of disability (src: 2010 U.S. Census).
  • The percentage of people affected by disabilities is growing as our population ages.
  • Two popular, free screen readers are VoiceOver (Mac OS and iOS) and NVDA (Win).
  • Good accessibility practices can improve the search ranking of your website.
  • Form fields without labels can cause problems for some assistive technology users.
  • Low color contrast makes content difficult to see, especially for users with low vision.
  • Documents linked on a website need to be accessible too (e.g., PDF and Word files).
  • Audio content, like podcasts, need transcripts for deaf or hard of hearing users.
  • Online videos should be captioned for deaf or hard of hearing users.
  • Using HTML tags correctly is very important for accessibility.
  • Descriptive link text helps make a website more accessible. Avoid using "Click here" or "Read more."
  • A "screen reader" is an application that reads content aloud to a user.
  • There is no "alt tag" in HTML. "Alt" is an attribute used with the img tag.
  • HTML uses the alt attribute to provide a text description of an image.
  • Alt text should describe an image, if the purpose of the image is to convey information.
  • If an image is a link, the alt text for the image should explain where the link goes.
  • If an image is only being used for decoration, the alt text should be null (i.e., alt="").
  • If a table has headers, using header tags (<th>) will make the table more accessible.
  • An accessible website is one that can be navigated and understood by everyone.