SDSC is committed to providing digital content that is accessible to all users.
Accessibility is not just about compliance; it is about ensuring equal access to information and services, and empowering everyone to access what they need, when they need it. Accessibility improves the user experience for everyone, whether they have a permanent disability, a temporary impairment (such as a broken hand), or a situational barrier (such as a loud environment or low-light area).
UC provides resources to help you. If you learn the basics and put accessibility at the forefront when creating new content, then you will reach a broader audience, increase engagement, and enhance overall user experience.
Digital Content Accessibility Standards
The U.S. Department of Justice (DOJ) requires all public entities to make digital content accessible under Title II of the Americans with Disabilities Act (ADA). UC San Diego, as a public university committed to the citizens of California and beyond, will abide by the new rules set forth in the Web Content Accessibility Guidelines (WCAG) 2.1 AA standards.
These rules require compliance of all digital content by April 24, 2026.
What must be accessible?
The standard applies to all digital resources, including:
- websites
- portals
- web-based applications
- online forms
- training and course content
- video and audio content
- social media content
- digital documents
Are there exceptions?
The DOJ allows for specific exceptions:
- Archived web content, i.e. content that is not actively used or updated, is exempt unless it becomes actively used again. Content must be kept in a special area specifically for archived content.
- Documents created before the compliance date that are not used in ongoing services or activities are exempt.
- Content posted by external parties (third-party content) that is not under a formal contract with UC San Diego is exempt.
- Personal documents shared with specific individuals that are password-protected are exempt.
- Social media content posted before the compliance date is exempt. Youtube videos are considered social media posts.
Shared Responsibility: Who Does What?
Content Creators
Proper headings, alt text, descriptive links, accessible documents
Web Developers
WCAG-compliant code, ARIA attributes, keyboard navigation, semantic HTML
Videographers
Accurate captions, transcripts, and audio descriptions for all media
Social Media
Alt text on images, captions on video, accessible post formatting
Educators
Accessible course materials, captioned lectures, readable syllabi
Procurement
Ensure purchased tools meet accessibility standards before acquisition
Take the UC Learning courses and role-based training that is appropriate for your role and skill level.
Guidance for Websites
Site owners are responsible for making sure websites meet accessibility and usability standards. This may include one-time coding fixes by a web developer, as well as making sure that content creators are following standards on an ongoing basis.
Getting Started
- Set up the website to be scanned by Siteimprove. There's a UC-wide license and no cost for UCSD sites.
- In the scan results, go to the Accessibility Overview to get your baseline score.
- Fix all Level A and Level AA issues. This must be done even if the site meets the benchmark.
- Review the potential issues and resolve all Level A and Level AA.
- Fix issues in other conformance categories if you can. At minimum, fix issues until you meet the benchmark.
- Add an Accessibility Statement to your site. SDSC subdomains may choose to point to the SDSC Accessibility Statement.
Getting Help
SDSC's Web & Database Services team offers expert consulting on a fee-for-service basis to assist you with meeting compliance requirements. This service is offered to both hosted customers and other UCSD sites.
UCOP offers digital accessibility office hours to UC employees.
Common Issues
The following describes some common problems and issues to look for. It is not a comprehensive list.
Some issues require a nuanced approach and specialized knowledge to correctly implement. Siteimprove's scan results include a difficulty scale on each issue to help you determine when to seek additional training or consulting help.
- Add an alt tag to all of your images, which describes the image for visually impaired users. Some content management systems will put an identifier or file name into the alt tag. You must change this to descriptive text.
- Use appropriately sized images. Web browsers will download the entire full-size image and then size it to fit the display. When the image is significantly larger than the display size, the page loads slower than necessary.
- Text content should not be in an image. For example, a graphic banner image promoting an event, which was created for printed material, is not appropriate on a website. Instead, you can write the text content in html and set a background image. Be mindful of color contrast, and test for multiple screen sizes as the text may overlay different parts of the image depending on the screen size and resolution.
See the images and graphics checklist for more best practices.
- Make links visually distinct from surrounding text. Color alone is not enough, and must be paired with a visual difference such as underline, bold, or change in font.
- Use descriptive link text.
- Avoid urls as link text. Screen readers read out the entire url character by character, which is time-consuming and frustrating for users.
- Avoid generic text like "Click Here" and "Learn More".
- How to write descriptive links.
- For icon-only links with no text, add aria-label.
- Users can navigate to links using only a keyboard.
- Use a player that is fully keyboard accessible.
- Neither audio nor video plays automatically without user input.
- Provide captions and a transcript.
- Note that YouTube is considered a social media platform, which means that all new videos must be accessible, but content posted prior to the compliance date is exempt.
See the audio and video checklist for specific requirements on pre-recorded and streaming content. The Web Accessibility Initiative (WAI) provides in-depth information on how to create new AV content that is accessible.
- Add controls to pause, stop, or hide animations lasting over 5 seconds. This includes carousels and banner videos.
- Avoid excessive motion and flashing. Remove/replace anything that flashes more than three times in a one-second period.
- Provide text alternatives.
- Respect user settings that turn off animations by implementing the prefers-reduced-motion CSS media query .
Accessible headings reflect page structure and act like an outline of your content. Heading levels must be properly nested, without skipping levels. For example, if you have an H2, then the next header nested under it must be H3, and you can't skip to H4 just to get a particular font or font size.
Beware of heading tags in the page footer. These are usually not part of the page structure, rather they are implemented to achieve a certain look (font, font size, color, etc.) In such cases, CSS styles should be used to replace the heading tags.
Read more about the correct use of heading tags.
- Ensure source code order matches visual page flow to make the website keyboard accessible.
- Use semantic HTML elements, such as <nav> for navigation menus, to help screen readers interpret content correctly.
- Use ARIA attributes (Accessible Rich Internet Applications) where necessary, such as aria-labeled-by for form input.
- Use a skip link to provide quick access to the main content of each page. This allows a person to bypass globally repeated content such as navigation menus and banners.
See the websites checklist for more requirements.
- Don't use color as the only way to indicate meaning or convey information.
- This video on use of color alone explains why it's a problem and how to fix it.
- Use a contrast ratio of at least 4.5:1 between text color and background color. Large font (18 pt or larger) has a minimum ratio of 3:1.
- This video on color contrast explains color ratios and how to check color contrast in your browser.
- Test colors with a contrast checker.
- Using UC San Diego brand color combinations will ensure compliance and is preferred for all sites. Division and departmental sites are required to conform to the UCSD brand.
Guidance for Documents and Forms
All documents and forms which are actively in use must be accessible, regardless of when the document or form was created.
For example, an internship application form that was created two years ago and will continue to be used for new applicants must meet accessibility standards. Any associated documentation or instructions must also meet accessibility standards. Completed applications that are kept on file for record keeping purposes do not need to be changed.
Is the document on a website?
Question whether it is necessary to post the document in the current format, or if an HTML page can serve the same purpose.
Is it a form?
Determine which form to use: PDF, Google, Qualtrics, or Docusign
How to make your documents accessible
- Use headings to organize content, convey relationships, and provide landmarks for quick understanding and navigation.
- Only use tables for information that needs to be presented in columns and rows. Do not use tables for creating visual layout.
- Add titles to tables, charts, and graphs.
- Provide descriptions of images and graphics.
- Never post a scanned file, because it will be a photographic image that a screen reader can't read.
- Application-specific guidance
Resources
- UC San Diego Accessibility Standards: including an Accessibility Advisor chatbot to answer questions
- UC Electronic Accessibility Initiative: including best practices, coding tips, and testing tools
- Training
- Read an overview of Digital Accessibility Basics
- Take a UC Learning course and role-based training
- Watch the Practical Accessibility Webinar Series