On April 26, 2027, public entities serving 50,000 people or more have to meet WCAG 2.1 Level AA. That includes most school districts, community colleges, and public universities. Smaller entities and special district governments have until April 26, 2028. The Department of Justice set those dates on April 20, 2026, pushing its original deadlines back a year after concluding it had overestimated how quickly institutions could fix existing content. The requirement did not change, but the clock did.
Accessibility is for all learners, not only those who self-identify as needing accommodations or alternate content. For example, learners may be distracted, attend courses in noisy environments, have a spotty internet connection, experience limited ability to use equipment due to an injury, and other impairments. Therefore, creating content with accessibility at the forefront of the design process versus retrofitting on the back end helps everyone.
(Before learning more about accessibility, I had in the distant past, prior to my time at Instructure, spent 376 hours redesigning and remediating accessibility errors in a 3-unit college course, so please learn from my hard-won experiences when I say that you will spend less time designing a course if you begin with accessibility at the forefront of the process instead of applying a time-intensive retrofit on the backend. The most important result of this endeavor is that you will be creating an engaging experience for all your learners.)
Inclusive design starts with a learner-centered approach that embraces diversity (welcoming differences, creating understanding, using appropriate language, discussing biases, freeing assumptions, and showing empathy). The best course design allows users to learn from diverse resources that can be accessed anytime and provides different learning modalities and solutions that fit all learners.
Web Content Accessibility Guidelines 2.1 (WCAG 2.1) was developed through the W3C process and has set standards for designing accessible content. The basic accessibility principles start with POUR:
- Perceivable: Content must be present in the form where the user can perceive it, auditorily and/or visually.
Examples: adaptable content, text alternatives, alt tags in images, etc. - Operable: The user interface, such as buttons, navigation, and all components, must be operable.
Examples: keyboard access, slow-moving content, streamlined navigation, etc. - Understandable: Learners should be able to understand, comprehend, learn, and remember.
Examples: the text is readable and easy to understand, know your audience and their specific requirements, predictable layout, etc. - Robust: Content is created that allows for a wide variety of user agents, such as assistive technologies in different environments.
The pillars of accessibility
These seven questions help you think about how to establish solid pillars of accessibility, and are the guidelines we use to create accessible content. They encompass headings, alt tags, descriptive links, color, lists, tables, and closed captions.
How should headings be structured for screen readers?
Headings are text formatting styles used to communicate the organization of the content within a page. They provide a structure and outline and allow screen readers and other assistive technology to scan the content page just like sighted users.
Tips
- Do not use headings to format the text
- Avoid standalone headings - with no paragraph text below
- Consistency! If you use H2 in bold, then make all H2 bold throughout
How do you write good alt text?
Alt Text or Alt Tag is a written (short and concise) description of non-text content on web pages. Alt Text/Alt Tag is essential for accessibility as the screen reader will read the description in place of an image and display the description if the image is not loading in the browser.
Tips
- Exclude the phrase "an image of" or "a picture of" as the screen reader will indicate it's an image
- Remove the file type extension from the alt text (.jpg, .png, etc.)
- Consider personal identifiers and positional information (a glimpse of, a partial view, etc.)
What makes link text accessible?
If the link is posted as the URL address, the screen reader will read a raw link letter/number/symbol by a letter/number/symbol, one by one. Therefore, it is best to describe a link as a descriptive phrase, not a sentence, to avoid confusion. The descriptive phrase should consist of the keywords identifying the item.
Tips
- Avoid linking ambiguous phrases such as "click here," "go here," "learn more," "read this," "start," etc., as these don't convey where the hyperlink will take users
- Screen reader typically announces a "link" before reading the actual link
- Do not post raw URLs
What color contrast does WCAG require?
Text and color background (foreground) need to have sufficient color contrast. Learners who are legally blind, visually impaired, or have color vision deficiency may not be able to identify text in color, emphasized text, or highlighted portions of the text. Using color as the only way to convey meaning is insufficient to meet accessibility standards. Color can be used to convey meaning as long as that meaning is also indicated in some other way, such as using italics, bold, a symbol, an identifier, etc.
Tips
- Canvas Accessibility Checker will alert you if there is not enough contrast
- It's okay to use color as long as the meaning is indicated in some other way
- Add textual reference when describing images or referring to the color on images
Why do lists need list formatting?
Lists are used to itemize related items. An ordered list may have a numerical or alphabetical hierarchy. An unordered list has no hierarchy and should be bulleted.
A "fake" list is created manually simply by hitting a hard return to a new row or by assigning a number, Roman numeral, or a letter. However, the screen reader will not announce the list or the items in it as a list.
Tips
- Lists should be created using the RCE "list tool"
- Use an ordered list when the order of the list is important (displayed in numerical or alphabet style)
- Use an unordered list when the order of the list doesn't have a particular order (displayed in a variety of bullet styles)
How do you make a data table accessible?
Tables are preferred when the content is more complex and requires organizing data. A table is a systematic arrangement of data in rows and columns.
Table scope identifies a caption (title of the table) and whether the cell is a header for a row, column, group of rows, or columns and rows. A header row is a top row in the table in which the individual cell describes the content in the cells that fall directly below. A header column is a left-most column that describes the content in the rows directly to the right.
Tips
- Do not use tables to format content (layout, headings, paragraphs, textbox, etc.)
- Do not use tables to style images (e.g. Home Page buttons)
- Manually styled tables with added color or highlighted cells do not meet accessibility requirements
How accurate do captions need to be?
Audio and video files must be accompanied by complete and accurate transcripts and closed captioning containing proper punctuation, capitalization, and word matching. Captions provide dialogue or a narrative, and audio descriptions provide a non-verbal explanation of what's happening on the screen.
Captions can be open captions (burned into the video that cannot be turned on or off), or closed captions (on-screen text that can be turned on or off).
Tips
- Avoid using auto-generated or open captions, which are not sufficient for accessibility
- Captions are not read automatically by a screen reader; you need to provide instructions ahead of the video on where to access them
- Caption accuracy of 99% is the benchmark captioning vendors and accessibility guidance generally work to, which allows roughly one error every two or three sentences. The ADA itself sets no numeric threshold; it requires effective communication.
Additional A11y (accessibility) resources
You can find more in-depth guidance on accessibility through any of these resources.
- Accessibility Fundamentals
- Write good Alt Text to describe images
- Contrast & Color
- Creating Accessible Tables
- Captions/Subtitles
FAQ
When do schools have to meet WCAG 2.1 Level AA?
The Department of Justice published its ADA Title II web accessibility rule in 2024 and extended the compliance dates on April 20, 2026. Public entities serving 50,000 or more people must comply by April 26, 2027. Those serving fewer, along with special district governments, have until April 26, 2028.
The standard is WCAG 2.1 Level AA, and the rule names one specific static version: the guidelines W3C published on June 5, 2018. That detail matters, because WCAG has moved since then. W3C published WCAG 2.2 on October 5, 2023, adding nine success criteria covering focus visibility, target size, dragging movements, and authentication. Designing to 2.2 will satisfy 2.1 in nearly every case, since the earlier criteria carry forward with a single removal. The legal obligation, though, is written against 2.1.
Does this rule apply to private colleges?
The Title II rule covers state and local government entities, which includes public institutions. Private colleges fall under ADA Title III, which the rule does not address.
Should we build to WCAG 2.1 or 2.2?
The rule requires WCAG 2.1 Level AA. WCAG 2.2 has been the current W3C Recommendation since October 5, 2023 and adds nine criteria on top. Building to 2.2 covers the 2.1 obligation and puts you ahead of the next revision.
Do we have to caption everything?
Content published to students needs captions. The practical benchmark is 99% accuracy, which auto-captioning alone rarely reaches without a human review pass.
Accessibility may at times seem overwhelming and time-consuming, but know that by having an open mind and heart, empathy, and celebrating diversity and inclusion, you will create new generations of independent and empowered learners. Nicole Hiers and Miranda McIntosh from Instructure Learning Services break down ADA Title II, WCAG 2.1 Level AA, and what to prioritize first. Watch their on-demand session to learn more.
About the Author
Saša is a Canvas Instructional Designer and a passionate Accessibility Advocate. Prior to working at Instructure, Saša was a Health and Kinesiology Instructor for multiple districts in the Los Angeles area as well as a Distance Education Coordinator. Besides her passion for all things distance ed and accessibility, Saša loves fitness, cooking, sewing, and salsa dancing.
