Title II of the Americans with Disabilities Act (ADA) requires that, by April 26, 2027, all digital course materials provided to students meet the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards. To learn more, please see the University’s IT Accessibility Policy (ITAP), which sets expectations for digital accessibility across the University of California.
The Web Content Accessibility Guidelines (WCAG, pronounced “wuh-cag”) are international standards based on four accessibility principles sometimes known by the acronym POUR:
-
Perceivable: Present information in ways that people can recognize and use, no matter what senses they rely on or how they consume content. Some people have low vision, have hearing loss, or use assistive technologies like screen readers.
-
Examples: providing text alternatives for images (alt text), using captions for audio and video
-
Operable: Make controls and information easy to navigate and use, no matter how someone interacts with it. People who do not use a mouse may use their voice, or press the 'Tab' key to move the keyboard's focus to interactive controls.
-
Example: people who can't use their hands should be able to click buttons using dictation software
-
Understandable: Information and the operation of the user interface must be clear and logical.
-
Example: people using any device or assistive technology should be able to identify links and understand what happens when they click them
-
Robust: Content must be compatible with a wide variety of assistive technologies, browsers, and devices.
-
It's easier to make materials accessible when creating them than to attempt to retroactively make them accessible.
-
Instructors aren’t notified about enrolled students’ DSP accommodations until the first weeks of classes.
-
There may be enrolled students who rely on some level of accessibility but aren’t in the DSP system.
-
It’s now both a federal and university requirement for all course materials to be accessible.
The main focus of our effort will be the course material shared with students via bCourses—syllabi, slides of lectures, readings, possibly also videos, Course Capture recordings of lectures, and other materials.
Anything that is created directly in bCourses (for example, the text of a quiz which an instructor either copies and pastes or types directly into a bCourses assignment) will be very accessible, because it will be an “in-line” part the bCourses website for your class, and will work with all the accessibility tools made to work with web pages. This means that files created outside of bCourses and then uploaded to a bCourses site will require the majority of our attention.
For general bCourses resources and help, please refer to RTL’s bCourses resource page, which includes links to step-by-step tutorials as well as contact information for the bCourses help team: (510) 664-9000, bcourseshelp@berkeley.edu. The bCourses help team is usually very responsive.
The main resource for information and support around creating accessible course materials will be the Accessibility in Teaching & Learning Commons page on the Research, Teaching, & Learning (RTL) Commons site. This page, with its explanations, list of “Top 5 Actions You Can Take Now,” FAQs and links to many subpages with information on specific topics, contains A LOT of information, all useful, but possibly a bit overwhelming. The steps outlined below attempt to make the process more manageable, following the likely steps most instructors will go through in building a bCourses site. We’ll link to subpages in the Research, Teaching & Learning Commons site when it’s necessary, to provide detail on a process.
A note on PDF documents: PDFs have long been considered the most universally accessible and easiest to share document format, and they’re one of the most common file types instructors upload to bCourses. But in the context of the new accessibility standards, they’re actually one of the most inaccessible formats, and are also among the most challenging to retroactively bring into compliance. You’ll find more information about accessibility in PDF documents on the Accessible PDF Files page on RTL Common’s site
A note on Ally: Ally is an accessibility tool built into bCourses which can scan your bCourses site, creating a Course Accessibility Report showing which elements are accessible and which aren’t, and providing suggestions for creating accessible versions of materials that currently aren’t accessible. Ally can also create alternate, more accessible, forms of some types of course materials.
If you’re creating the bCourses site for your fall class from scratch—not importing the contents of a bCourses site from a previous iteration of the class—please skip ahead to the SYLLABI section below.
Analyze existing materials
If you are recycling a bCourses site from a previous iteration of your the course, once you’ve imported it into your the new bCourses site for your fall course, please
-
Scan the materials you’re hoping to recycle using Ally. For step-by-step guidance, see the Ally in bCourses page on the RTL Commons site
-
Restrict access to materials that aren’t compliant with the accessibility standards while you work to find/create versions of the materials that are compliant. For step-by-step guidance, see the bCourses Knowledge Board on how to restrict access to a bCourses site or materials
Using this approach, you can update materials gradually, beginning with those that students will need earlier in the semester. Consider letting students know you are actively working on accessibility and invite them to flag any files that are inaccessible.
Syllabi
Creating syllabi in Word or Google Docs will continue to work well, both because it will be relatively accessible if you upload it to bCourses as a Word file or add it as a link to a Google Doc, and because the History Department will continue requesting that you email your syllabi to the office each semester to be archived. Avoid saving your syllabus as a PDF document and uploading that to bCourses. Microsoft and Google documents give students many options for accessing them, and both Microsoft and Google will be continually working to make their platforms more accessible. By keeping documents in these file formats they’re created in, they are more likely to be compliant and to remain compliant.
You can find tips on creating accessible documents in Word and Google docs on RTL Commons’ Accessible Documents (Microsoft Word & Google Docs) page
To maximize the accessibility of your syllabus, you can build a version of it directly in bCourses. The bCourses syllabus template includes the syllabus, course summary, and sidebar—you can find a step-by-step bCourses tutorial, including a video, here. At minimum, you can copy and paste the text of your syllabus from Word or Google Docs into the syllabus description field.
Lecture slides
There’s detailed tutorial on creating accessible slides on RTL Commons’ Accessible Slides (Microsoft PowerPoint, Google Slides, & LaTeX) page. Key steps for making slide decks accessible include:
-
Add alt-text to images and other visuals.
-
Add unique titles to each slide.
-
Upload the slide deck to bCourses in its original format (Powerpoint file, Google Slides link) rather than saving as a PDF file and then uploading.
Readings
The readings you add to your bCourses site will most likely be the materials that need the most attention. Faculty who’ve already begun work on making their course materials accessible have probably found that bringing readings into compliance has been the most challenging. When possible, link to accessible licensed library resources instead of uploading scanned pages or personal PDF copies. Please refer to the Library’s Digital accessibility of Library collections page, and submit questions, suggestions, or requests for support through the Library intake form
Other Course Materials
When creating other course materials—components such as assignments and quizzes—avoid uploading documents created in another platform, or linking to documents saved in another platform. Instead, either type text directly into fields bCourses, or type and edit text in another platform but then copy and paste the text directly into fields in bCourses. Anything that’s created directly in bCourses in this way will be very accessible, because it will be an in-line part of your bCourses website, and will work with all the accessibility tools available for accessing websites.
Additional Campus Resources
RTL Commons Accessibility Guidance Inquiries
Submit an inquiry using this Google form.
Research, Teaching & Learning Commons Events & Trainings for Digital AccessibilityRTL Commons offers events and workshops that bring together instructors, researchers, graduate student instructors (GSIs), and academic support staff to share ideas and explore teaching practices.
For questions related to accessible teaching and learning, please email: course-accessibility@berkeley.edu.
Department Resources
Loading Accessible PowerPoint Slides to bCourses
Maximizing Accessibility Functions in PowerPoint
Loading Accessible Google Slides to bCourses
Maximizing Accessibility Functions in Google Slides
Quick Accessibility Fixes in bCourses
The Three Quickest Ways to Increase Your bCourses Ally Score
Questions? Reach out to: David Harris athistory-scheduling@berkeley.edu.