eCampus Accessibility Checklist and Guide

Last modified on 

November 13, 2026

 by 

Kelsey Keefe

Overview

This article is a practical guide to implementing the eCampus Accessibility Checklist, developed to help faculty meet UConn’s accessibility requirements and WCAG 2.1, Level AA under Title II. For each checklist item, it explains the accessibility barrier the item addresses, provides guidance on how and when to apply it, and points to relevant tools and documentation. It also describes how each item aligns with WCAG, Quality Matters, and Universal Design for Learning, connecting day-to-day implementation to the broader frameworks that shape accessible course design.

Introduction

The eCampus Accessibility Checklist and accompanying Guide were developed to aid faculty in developing digital content and materials in an online course site accessible to students with disabilities.

All faculty teaching at UConn (in any modality) are responsible for ensuring that their course content meets the accessibility requirements established by the University’s Digital Accessibility Policy and applicable federal and state accessibility laws, including Title II of the Americans with Disabilities Act (ADA).

Title II expands digital accessibility by requiring public entities to ensure their programs, events, and services meet Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. WCAG is a set of internationally recognized guidelines addressing web, document, and app accessibility. While all courses at UConn are subject to Title II, online courses typically have more digital content and apps to address than a traditional in-person course.

This checklist is designed to help faculty meet relevant accessibility requirements for teaching, and the guide provides context and implementation guidance for checklist items.

Guidance

This guide lists each checklist item followed by corresponding guidance. The guidance for each item is organized into the following sections:

  1. Requirement Level – Whether an item is required or recommended.
  2. Purpose – Why a checklist item matters: how the content, technology, and the person using it interact; what goes wrong when they don’t align; and what makes the experience more accessible.
  3. Implementation – When and how to apply a checklist item, including different approaches and when an exception may be appropriate.
    1. How-to Guides – Links to external documentation for implementing the checklist item.
    2. Tools – Links to external tools and software that help implement or verify the checklist item.
    3. Accessibility Checkers – Information on the availability and limitations of built-in accessibility checkers for common platforms.
  4. Framework Mapping – A table identifying the disability categories a checklist item supports, along with its alignment with WCAG 2.1, Quality Matters (QM), and Universal Design for Learning (UDL).

Refer to the Appendix for additional information about how to interpret these fields.

Section 1. Text Style

Section 1 items apply to all document types and web content.

Purpose

Simple, familiar, or easily parsed typefaces allow for easy readability on computers and mobile devices. Ornate typefaces require additional cognitive processing to understand. The simpler letterforms of sans serif fonts (e.g., Arial, Aptos, Calibri) remain clear at smaller sizes, on lower resolution screens (WebAIM, 2020, Typefaces and fonts), and when enlarged.

Familiar fonts have recognizable letterforms that require less orientation and cognitive processing to the reader (WebAIM, 2020, Typefaces and fonts). Familiar fonts are also more likely to be supported across devices. When a font is unsupported or unavailable, the system typically substitutes a different typeface. The substituted font can cause formatting issues that reduce readability and increase cognitive load.

Implementation

Follow established typeface conventions for specialized content. For example, present code in a familiar monospaced font.

Otherwise, use a simple, familiar font, preferably a sans serif font, for paragraphs and other extended blocks of text. If a style guide requires a different font, select the clearest and most familiar option permitted.

How-to Guides
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked. However, the text editor has a limited number of fonts, all of which are simple, familiar, or sans serif.
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports readability and visual customization; Reduces cognitive load (processing)
  • Visual – Supports visual perception and customization
WCAG 2.1 Alignment
  • None
Quality Matters Alignment
  • Standard 8.2 – The course design facilitates readability – 3 points
UDL Alignment
  • None

Purpose

Each added font used requires some orientation and cognitive load to the reader (WebAIM, 2020, Typefaces and fonts).

When a document has many fonts, it is also more likely that one or more fonts is unsupported or unavailable. When a font is unsupported or unavailable, the system typically substitutes a different typeface. The substituted font can cause formatting issues that reduce readability and increase cognitive load.

Implementation

This item recommends using only one to two fonts or font families in each document. For example, Arial and Arial Black can be used as variations within the same family.

Follow established typeface conventions for specialized content, even if it requires introducing an additional font. For example, present code in a monospaced font.

How-to Guides
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked. However, the text editor has a limited number of fonts.
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports readability; Reduces cognitive load (processing)
  • Visual – Supports visual perception and customization
WCAG 2.1 Alignment
  • None
Quality Matters Alignment
  • Standard 8.2 – The course design facilitates readability – 3 points (Supported)
UDL Alignment
  • None

Purpose

Long sections and many variations of text in bold, italics, capitalization, color, and other styling can make text more difficult to read. Each variation requires some orientation and cognitive load to the reader (WebAIM, 2020, Typefaces and fonts).

Visual customization settings and assistive technologies (e.g., screen readers, refreshable braille displays) may alter or omit text decorations. Information conveyed through styling alone may be lost or unclear with use of these tools.

Underlining is a well-established convention for hyperlinks. Using underlining for other purposes will likely cause confusion, as some may mistake underlined text for a link and try to select it (WebAIM, 2020, Text/typographical layout).

Implementation

Style text according to style guides and established conventions for specialized content. For example, publication titles may be italicized, and acronyms may be in all capital letters.

Otherwise, apply text decoration sparingly for emphasis — do not style entire paragraphs and other extended blocks of text.

Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports readability and visual customization; Reduces cognitive load (interpretation and processing); Prevents sensory overload
  • Visual – Supports visual perception and customization
WCAG 2.1 Alignment
  • None
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points
  • Standard 8.2 – The course design facilitates readability – 3 points
UDL Alignment
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 7.4 – Address biases, threats, and distractions (Supported)

Purpose

Real Text

Real text—text that is rendered as text characters in documents and web pages—has many advantages over images of text (W3C WAI, 2026, Understanding SC 1.4.5; WebAIM, 2020, Typefaces and fonts). (Note that handwritten notes are rendered as images.)

Real text can be recognized by assistive technologies, allowing the content to be presented in a variety of modalities (e.g., text-to-speech, refreshable Braille display) (W3C WAI, 2025, Technique PDF7). Readers can also customize the typeface, font size, text and background colors, line spacing, and zoom level to improve readability. Real text also supports search, translation, and copy/paste (W3C WAI, 2025, Technique PDF7; W3C WAI, 2026, Understanding SC 1.4.5; WebAIM, 2020, Typefaces and fonts).

Mathematical Notation

Presenting equations as mathematical notation created with an equation editor provides many of the same benefits of real text. Mathematical notation created with an equation editor improves readability compared to handwritten math. In many cases, learners can customize the visual display (similar to real text) to further support readability (W3C WAI, 2025, Technique PDF7; W3C WAI, 2026, Understanding SC 1.4.5; WebAIM, 2020, Typefaces and fonts). Mathematical notation also provides information about components and relationships within an expression. It can be recognized by assistive technologies, allowing the content to be presented in a variety of modalities (The University of Melbourne, n.d.; White, 2019).

Structured Mathematical Notation

Depending on the mathematical notation tool and format used, assistive technologies may access mathematical information and relationships through the structured equation or equivalent text. The Microsoft Equation Editor stores equations using Office Math Markup Language (OMML) (Microsoft Support, n.d., Editing equations…). The Blackboard LMS Math Editor (powered by MathType) uses the entered mathematical notation to generate the displayed equation and accompanying accessibility information (MathType, n.d.). While these mathematical notation methods meet technical accessibility requirements, they do not always provide the most usable experience for reading complex equations (White, 2019).

Semantic Mathematical Notation

Depending on the notation, software, and assistive technology used, a complex expression may be presented as a long linear sequence. Having a single-line readout of an expression requires a great deal of working memory and leaves few cognitive resources “to ‘do mathematics’—that is, to understand, manipulate, and write symbolic expressions in order to solve a mathematical problem or to develop a mathematical proof” (White, 2019, p. 3).

Mathematical Markup Language (MathML), a W3C standard, is a web-based semantic mathematical notation; it presents expressions on webpages in a way that preserves their underlying meaning. Assistive technology users can navigate through the components of an equation and explore their relationships (The University of Melbourne, n.d.; White, 2019).

Implementation

Application
Handwriting in Videos

Handwritten text and equations may be used within instructional videos when they are presented as part of the teaching process (e.g., solving a problem on a whiteboard or tablet). However, the information must still be available to learners who cannot adequately perceive the visual content. Depending on the context, this may require audio descriptions (Checklist Item 5.5) or an accessible digital copy of the content (Checklist Item 5.6).

Images of Equations

The W3C Web Accessibility Initiative (WAI) states that “images of math expressions should only be used in exceptional circumstances” (W3C WAI, 2017, Images tutorial). In these circumstances, an image of an equation with alt text may meet applicable WCAG requirements if the text alternative serves the equation’s equivalent purpose (W3C WAI, 2026, Understanding SC 1.1.1). As an expression becomes more complex, a text description may not adequately communicate its grouping, order, or mathematical relationships. Refer to Checklist Item 2.3 for guidance on providing text alternatives.

Choosing Structured vs. Semantic Notation

While MathML is recommended, WCAG does not require MathML specifically (W3C WAI, 2017, Images tutorial). Structured notation (e.g., Microsoft’s OMML) may meet applicable WCAG requirements. The mathematical notation chosen should support what learners need to do with an equation. MathML is recommended for complex mathematical content because it may provide greater usability (The University of Melbourne, n.d.; White, 2019).

Creating MathML

Create MathML expressions by using a supported editor that generates MathML or converting LaTeX input into MathML. Then, present MathML content in a compatible web-based format, such as HTML or EPUB. Converting MathML content into other formats, such as a PDF, may replace or remove the original MathML. Always evaluate the output file to ensure retention of the original MathML.

LaTeX

LaTeX syntax is commonly used to write mathematical expressions, particularly complex equations. Depending on the authoring and publishing workflow, a LaTeX expression may be output as an image, structured mathematical notation (e.g., Microsoft’s OMML), or semantic mathematical notation (i.e., MathML).

The resulting equation may be delivered within a PDF, PowerPoint presentation, HTML file, EPUB, or other file format. Both Microsoft Word and HuskyCT support using LaTeX to create and edit equations (Blackboard LMS Help Center, 2026, Math editor; Microsoft Support, n.d., Linear format equations …).

Accessibility depends on the resulting equation and file format. Converting or moving an equation into different file formats may alter or remove its underlying structure. Always evaluate the output file to ensure accessibility. Refer to Checklist Item 4.11 for guidance on selecting an output format for LaTeX-authored materials, particularly when using LaTeX more broadly for document-preparation.

How-to Guides
Tools
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT:
    • Uploaded PDFs: Ally identifies PDFs that are scanned (full-page images). It does not otherwise verify use of real text and mathematical notation.
    • Other content: Not checked
  • Adobe Acrobat Pro: The accessibility checker identifies PDFs that are scanned (full-page images). It does not otherwise verify use of real text and mathematical notation.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports readability, visual customization, and assistive technology access
  • Visual – Supports visual perception, customization, and assistive technology access
WCAG 2.1 Alignment
  • Success Criterion 1.1.1 – Non-text Content – Level A
  • Success Criterion 1.3.1 – Info and Relationships – Level A
  • Success Criterion 1.4.5 – Images of Text – Level AA
Quality Matters Alignment
  • Standard 8.3 – Text in the course is accessible – 3 points
UDL Alignment
  • Consideration 1.1 – Support opportunities to customize the display of information
  • Consideration 1.2 – Support multiple ways to perceive information
  • Consideration 2.2 – Support decoding of text, mathematical notation, and symbols
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

For languages read from left to right, left-aligned text is almost always easiest to read. Long blocks of centered text require additional cognitive load to read, as each line starts in a slightly different location. Fully justified text creates spacing variations and distracting patterns of whitespace, which also increase cognitive load (WebAIM, 2020, Text/typographical layout).

Implementation

Align the text according to the reading direction of the language:

  • Languages read left-to-right: Left-align text
  • Languages read right-to-left: Right-align text

Apply this principle to paragraphs and other extended blocks of text. Headings, short captions, labels, asides, and other brief text may use a different alignment if readability is maintained.

Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked. However, the text editor defaults to left-aligned text.
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports readability; Reduces cognitive load (processing)
WCAG 2.1 Alignment
  • Success Criterion 1.4.8 – Visual Presentation – Level AAA
Quality Matters Alignment
  • Standard 8.2 – The course design facilitates readability – 3 points (Supported)
UDL Alignment
  • None

Section 2. Images

Section 2 items apply to figures, images, charts, and graphs in all document types and web content.

Purpose

Referring to figures in terms of their location on the page (e.g., the image to the right) may be confusing or meaningless to learners, especially if they have impaired vision. Due to adaptive displays, any learner, regardless of disability, viewing materials on a different screen size (e.g., mobile device) than the creator may see the figure in a different position.

Using built-in caption tools to label figures identifies the relationship between a figure, its label, and any references to the figure elsewhere in the content.

Implementation

Figure numbers are most useful when a document, page, or slide contains multiple figures that may need to be referenced within the surrounding content. When only a single figure is present, a figure number may add little value.

Use built-in caption tools when they are available within the platform. If a platform does not provide a built-in tool, label the figure using the available formatting options.

For example, label a figure in PowerPoint by adding a text box with the label immediately before or after the figure. Do not group the text box label with the image (which is contrary to Microsoft Support’s guidance for inserting a caption in PowerPoint). Screen readers announce only the alt text attributed to the highest level of a grouped object, so the text box will not be read if it’s within a group.

How-to Guides
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports visual customization; Reduces cognitive load (interpretation)
  • Visual – Provides equivalent alternative to visuals; Supports visual customization and assistive technology access
WCAG 2.1 Alignment
  • Success Criterion 1.3.1 – Info and Relationships – Level A
  • Success Criterion 1.3.3 – Sensory Characteristics – Level A
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points (Supported)
  • Standard 8.2 – The course design facilitates readability – 3 points (Supported)
UDL Alignment
  • Consideration 1.2 – Support multiple ways to perceive information (Supported)
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 2.5 – Illustrate through multiple media (Supported)
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

In Word, images or figures requiring alt text must be placed “in line with text” (default setting) to be recognized by assistive technology (e.g., screen reader, refreshable Braille display). Screen readers skip images using a different text wrap setting (WebAIM, 2024, [Course materials]; WebAIM, 2023, Word and PowerPoint accessibility evaluation guide).

Placing figures near the content they support reduces the cognitive load associated with locating figures. It also reduces the working memory needed to consume information presented in multiple modalities.

Implementation

How-to Guides
Accessibility Checkers
  • Microsoft 365:
    • Word: The accessibility checker identifies images or objects within the document’s body that are not placed in line with text. It does not verify that figures are placed near the content they support.
    • Other Products: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports visual customization and assistive technology access; Reduces cognitive load (processing)
  • Visual – Supports visual customization and assistive technology access
WCAG 2.1 Alignment
  • Success Criterion 1.3.1 – Info and Relationships – Level A
  • Success Criterion 1.3.2 – Meaningful Sequence – Level A
Quality Matters Alignment
  • Standard 8.2 – The course design facilitates readability – 3 points
UDL Alignment
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

As WebAIM explains, “alternative text [or alt text] is a textual substitute for non-text content in web pages” and other digital formats. “Screen readers announce alternative text in place of images, helping users with visual or certain cognitive disabilities perceive the content and function of the images” (WebAIM, 2021, Alternative text). Alt text is also displayed in place of an image if it fails to load.

The following video demonstrates experiencing images with and without alt text in HuskyCT using NVDA screen reader:

Implementation

Images that convey content, function, or meaning should have a text alternative: alt text or a long description.

  • Alt text is added to the image attributes and is intended for brief descriptions.
  • A long description issued when a complete description cannot fit within the platform’s alt text limit or can no longer be expressed in a few sentences. Long descriptions are typically provided in nearby text, linked content, slideshow speaker notes, or another accessible format depending on the platform.

The text alternative should contain the image’s content and function, so considering the context is important. Decorative images should be marked as decorative rather than provided with alt text.

Complex figures have special considerations when providing text alternatives, which include the following:

  • Charts and Graphs: While charts and graphs presented as images require alt text or a long description, charts with accessible underlying data and navigable chart elements (e.g., charts embedded using Excel) may not require a separate description.
  • Grouped Objects: In Microsoft 365 documents and slideshows, screen readers announce only the alt text attributed to the highest level of a grouped object or SmartArt graphic. Learners typically cannot navigate the individual elements within the graphic. Ensure important content, relationships, and text within the graphic are available by ungrouping objects or through another accessible means.
  • Tables: Accessibility checkers may occasionally identify data tables as needing alt text. Data tables generally do not need alt text when made accessible through proper structure and headers. Refer to Checklist Item 4.7 for table accessibility.
How-to Guides
Accessibility Checkers
  • Microsoft 365: The accessibility checker identifies objects missing alt text and not marked as decorative. (However, it incorrectly identifies tables as needing alt text.) The accessibility checker also identifies objects with alt text containing image names or file extensions, as this indicates the alt text is not descriptive. It is unable to verify that alt text is clear and descriptive or identify if an image is inappropriately marked as decorative.
  • Ally in HuskyCT: Ally identifies images missing alt text and not marked as decorative. It is unable to verify that alt text is clear and descriptive or identify if an image is inappropriately marked as decorative.
    • Uploaded Images: Additionally, Ally identifies uploaded images where the alt text matches the file name, as a means to identify alt text that is not descriptive.
  • Adobe Acrobat Pro: The accessibility checker identifies objects missing alt text and not marked as artifacts (i.e., decorative). It is unable to verify that alt text is clear and descriptive or identify if an image is inappropriately marked as an artifact.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Reduces cognitive load (interpretation)
  • Visual – Provides equivalent alternative to visuals
WCAG 2.1 Alignment
  • Success Criterion 1.1.1 – Non-text Content – Level A
Quality Matters Alignment
  • Standard 8.4 – Images in the course are accessible – 2 points
UDL Alignment
  • Consideration 1.2 – Support multiple ways to perceive information
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Section 3. Sensory Characteristics

Section 3 items apply to all document types and web content.

Purpose

Text and graphics with poor contrast may be impossible or difficult to see. Contrast refers to the difference in perceived brightness between a foreground color and its background. Contrast is expressed as a ratio ranging from 1:1 for the same color to 21:1 for black and white (WebAIM, 2021, Contrast and color accessibility).

Implementation

Sufficient contrast is required for non-decorative text, figures, and other visual elements that convey content, function, or meaning. Decorative elements are not required to meet contrast requirements (WebAIM, 2021, Contrast and color accessibility).

“Sufficient” contrast is defined as follows:

Foreground ElementMinimum Contrast Ratio
Normal Text4.5:1
Large Text
  • Text that is 18pt or larger
  • Bolded text that is 14pt or larger
3:1
Graphical Objects3:1
User Interface Components3:1

Contrast can be measured with a contrast checker (WebAIM, 2021, Contrast and color accessibility).

How-to Guides
Tools
  • WebAIM Contrast Checker – Test contrast by entering color hex values or using the color picker to select the color of any element on the screen.
  • Adobe Color Contrast Checker – Create custom color palettes. Assess color palettes for sufficient contrast.
  • This Hue Shall Pass – Assess color palettes for sufficient contrast. Automatically adjust colors that are close to passing.
Accessibility Checkers
  • Microsoft 365:
    • PowerPoint: The accessibility checker only identifies insufficient contrast between text and a solid text box fill color. When a text box has no fill color (default), the checker skips the text; it cannot verify the contrast between text and “no background.” When a text box has a gradient, image, or pattern as the fill, the checker also skips the text; it cannot verify the contrast between text and many background colors. The accessibility checker does not verify sufficient contrast between layered elements (e.g., lines, shapes), with the slide background, or within images.
    • Other Products: The accessibility checker identifies insufficient contrast between text and the background. It does not verify sufficient contrast between other foreground and background elements.
  • Ally in HuskyCT:
    • Text Editor: The text editor has a limited number of font colors, all of which have sufficient contrast with the white background. Text pasted from other sources may contain other colors; Ally will identify instances with insufficient contrast.
    • Uploaded Files: The Accessibility Report identifies insufficient contrast with text and images, but it may provide a false warning for decorative elements. Since Ally uses a pixel-by-pixel comparison, Ally typically identifies contrast issues that other accessibility checkers miss.
  • Adobe Acrobat Pro: Prompts manual check of color contrast.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports readability
  • Visual – Supports visual perception
WCAG 2.1 Alignment
  • Success Criterion 1.4.3 – Contrast (Minimum) – Level AA
  • Success Criterion 1.4.11 – Non-text Contrast – Level AA
Quality Matters Alignment
  • Standard 8.2 – The course design facilitates readability – 3 points
UDL Alignment
  • None

Purpose

Sensory characteristics, such as color, shape, size, visual location, or orientation, may be difficult or impossible for some people to perceive (W3C WAI, 2025, Understanding SC 1.3.3).

Color enhances the user experience and helps convey, differentiate, or reinforce information. However, identifying or distinguishing colors may be difficult or impossible for those with color vision deficiency (commonly known as colorblindness) (WebAIM, 2021, Contrast and color accessibility; WebAIM, 2021, Visual disabilities). Shape, size, location, or orientation are other visual sensory characteristics that may not be perceivable to someone with impaired vision (W3C WAI, 2025, Understanding SC 1.3.3).

Accessibility tools that filter colors, increase contrast, magnify content, or support other visual customizations may override default document colors, sizing, and object placement. Due to mobile-responsive displays, any learner, regardless of disability, may experience differences in sizing and location. References to these sensory characteristics alone may be confusing or meaningless to learners.

Implementation

Instead of using sensory characteristics alone to convey meaning, use an additional indicator such as a text label. (e.g., Instead of adding comments to a paper using red text alone, begin each instructor comment with “Instructor comment,” or use built-in commenting tools.) These labels must be available to everyone, not limited to those using a particular method of accessing content. For example, presenting the label only in alt text makes the label readily available only to screen reader and Braille display users (W3C WAI, 2025, Understanding SC 1.3.3; W3C WAI, 2025, Understanding SC 1.4.1).

Continue using sensory characteristics such as color alongside labels when doing so supports a pedagogical goal. Color coding helps students organize, differentiate, and recall information, and can increase engagement with course materials (Linscott, 2025). Support color differentiation with textures, patterns, or “colorblind-friendly” color palettes. Colorblind learners continue to benefit from the pedagogical value color provides compared to using the label alone.

How-to Guides
Accessibility Checkers
  • Microsoft 365:
    • Excel: The accessibility checker identifies cells that convey negative number values using red color only. It does not identify other uses of other sensory cues alone to convey meaning.
    • Other Products: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports visual customization; Reduces cognitive load (interpretation)
  • Visual – Provides equivalent alternative to visuals; Supports visual perception and customization
WCAG 2.1 Alignment
  • Success Criterion 1.3.3 – Sensory Characteristics – Level A
  • Success Criterion 1.4.1 – Use of Color – Level A
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points (Supported)
  • Standard 8.2 – The course design facilitates readability – 3 points
  • Standard 8.3 – Text in the course is accessible – 3 points
UDL Alignment
  • Consideration 1.2 – Support multiple ways to perceive information (Supported)
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures

Section 4. Content Authoring Tools

Content authoring tools include all software used to create content such as HuskyCT, Word, and PowerPoint.

Purpose

Most people navigating a computer have multiple windows and tabs open at a given time, and screen reader users are no different. Using unique descriptive metadata titles and file names helps orient screen reader users as they navigate. Meaningful metadata titles and file names also reduce learners’ cognitive load, as they know what to expect from the document (Chen, n.d.).

Implementation

Add the document metadata title to the document properties. Document properties can typically be edited from within the open document or from the file’s save location.

How-to Guides
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT:
    • Uploaded PDFs: Ally identifies PDFs that do not have a metadata title. It is unable to verify that the PDF’s metadata title and file name are unique and descriptive.
    • Other Content: Not checked
  • Adobe Acrobat Pro: The Accessibility Checker identifies documents that do not have a metadata title. It is unable to verify that the document’s metadata title and file name are unique and descriptive.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Reduces cognitive load (processing)
  • Visual – Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 2.4.2 – Page Titled – Level A
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points (Supported)
UDL Alignment
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools
  • Consideration 7.4 – Address biases, threats, and distractions (Supported)

Purpose

Specifying the correct document or page language and identifying language changes in text allow assistive technology (e.g., text-to-speech software, screen reader, refreshable Braille display) to correctly pronounce or display the text (WebAIM, 2021, Document and content languages).

Implementation

Application

In general, language is specified as a document or page property. All content is assumed to be in that language unless otherwise specified at the character level. For example, the language settings might communicate: “This whole document is in English, except for this one sentence, which is in Spanish.”

Microsoft 365

Microsoft 365 apps do not have a separate document-level language setting; language is specified at the character level throughout the content (Blom, 2023; Jones, 2020). For example, the language settings might communicate: “This paragraph is in English, this sentence is in Spanish, and these two sentences are in English.”

Language for content is set automatically based on the author’s installed proofing language(s). As an author types, Word generally detects and specifies the correct language for each word. Spot-checking is recommended, though, since detection is not always accurate (Microsoft Support, n.d., Check spelling and grammar…). For example, an instructor creating a course document in both English and Spanish, with both installed as proofing languages, can generally expect each word to be automatically tagged with its correct language while typing. If a passage of Spanish text is marked as misspelled, the proofing language is likely incorrectly set for that passage and should be manually corrected to Spanish.

If language detection is not working correctly, language can also be specified in text styles. This is a more reliable way to track which language has been applied and is less susceptible to accidental overrides (Blom, 2023; Jones, 2020). However, this method only helps if styles are applied correctly and consistently throughout the document; inconsistent or incorrect style use can make language tagging less accurate. This approach is best suited for authors already comfortable working with Word’s styles.

HuskyCT

HuskyCT determines page language using a hierarchy:

  1. A course-level language marked as “enforced” takes precedence.
  2. If no “enforced” course-level language is set: The user-level language is applied.
  3. If no user-level language is set: The course-level language (not “enforced”) is applied.
  4. If no course-level language is set: The institutional system-level default language is applied (Blackboard LMS Help Center, 2026, Set your language).

This hierarchy means a page’s specified language may be incorrect if a student has changed their own account language. Most UConn courses are in English, and the institutional default is English (United States), so a page’s language will typically be correct unless a student has switched their personal account setting to a different language. It is not a conformance failure if the page language is incorrectly specified due to a user’s account setting.

HuskyCT does not support identifying language at a more granular level than the course. An individual page within a course cannot be assigned a different language, and changes in language within a page cannot be tagged.

For language courses presenting most content in the target language (e.g., a Spanish course presenting primarily Spanish-language content), coordinate with HuskyCT Support (ITS Technology Support Center) to set and enforce the course-level language. Most students have not specified an individual account language, so they default to the institutional system-level setting of English. Without an enforced course-level language, most course content would be incorrectly specified as English for these students despite being written in another language.

How-to Guides
Accessibility Checkers
  • Microsoft 365: Language of content is detected and specified automatically based on set proofing language(s). If content is marked as misspelled, the set language is likely incorrect.
  • Ally in HuskyCT:
    • Uploaded PDFs: Ally identifies PDFs that do not have a specified page language. It is unable to verify that the specified page language is correct nor that language changes in content are correctly specified.
    • Other Content: Not checked
  • Adobe Acrobat Pro: The accessibility checker identifies documents that do not have a specified page language. It is unable to verify that the specified page language is correct nor that language changes in content are correctly specified.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports assistive technology access
  • Visual – Supports assistive technology access
WCAG 2.1 Alignment
  • Success Criterion 3.1.1 – Language of Page – Level A
  • Success Criterion 3.1.2 – Language of Parts – Level AA
Quality Matters Alignment
  • Standard 8.2 – The course design facilitates readability – 3 points (Supported)
UDL Alignment
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

Headings create the structure and outline of a page. They help readers understand how content is organized and allow users to navigate quickly between sections. Screen reader users rely on headings to navigate content, and navigation can become cumbersome and confusing if headings are absent, vague, or not hierarchical (WebAIM, 2024, Headings).

The following video demonstrates navigating a document with and without headings in HuskyCT using NVDA screen reader:

Some platforms also use built-in headings to ease navigation for everyone. For example, built-in headings appear in the Navigation pane in Word documents. Designating headings also makes it easier to manage the appearance and styling of your document. With the click of one button, font size, font decoration, line spacing, and other attributes are automatically applied or changed.

Implementation

Appllication

Many authors create headings by visually styling their heading text with bolding or a larger font size. Rather than only changing the appearance, it is important to designate heading text as a heading by applying the appropriate built-in heading style. Heading styles provide the underlying structure that assistive technologies rely on (WebAIM, 2024, Headings).

Heading Structure

There are six levels of headings:

  1. Heading 1 (H1) – Document or page title. H1 is used only once per webpage or document (though some exceptions exist). H1 is often the same as the document’s metadata title (Checklist Item 4.1).
  2. Heading 2 (H2) – Main sections. Use H2 to outline the main content of your document. Each H2 in a document should be unique to avoid confusion.
  3. Heading 3 (H3) through Heading 6 (H6) – Subsections. Use H3, H4, H5, and H6 to create hierarchical subsections. These heading levels do not need to be unique since they are nested under a unique H2.

Use heading levels in order and do not skip levels when nesting (for example, H2 directly to H4 skips H3). You may move back to a higher-level heading when starting a new section (for example, H4 back to H2) (WebAIM, 2024, Headings).

Most assistive technology does not support headings greater than H6; do not use them even if available (e.g., in Microsoft Word).

Headings in Common Platforms

Use built-in headings appropriate for the content authoring platform. The following table outlines how some Microsoft 365 products and HuskyCT manage headings.

WordPowerPointExcelHuskyCT
Heading ToolStyleSlide TitlesWorksheet NamesText Style
Heading 1Heading 1 (do not use “Title” style)Title Placeholder on “Title Slide” layoutWorksheet NameTitle of Document, Assignment, Test, etc. (created automatically)
Heading 2Heading 2Title Placeholder on other slide layoutsNot available“Title” style
Heading 3Heading 3Not availableNot available“Header” style
Heading 4Heading 4Not availableNot available“Subheader” style”
Heading 5Heading 5Not availableNot availableNot available
Heading 6Heading 6Not availableNot availableNot available
Descriptive Headings

Do not use heading styles to visually style content as larger or bolder. Headings should only be used for content that is functioning as a heading (i.e., describing the content that follows).

Headings should be descriptive. For example, “Section 4. Content Authoring Tools” instead of just “Section 4.” Ensure your content does not have empty headings (WebAIM, 2024, Headings).

How-to Guides
Accessibility Checkers
  • Microsoft 365:
    • Word: The accessibility checker identifies content that does not use any built-in headings when the document meets certain criteria (lengthy, contains many paragraphs). However, a single heading at any level “resolves” the issue. It does not identify instances of skipped heading levels or verify that headings are unique and descriptive.
    • PowerPoint: The accessibility checker identifies slides that are missing slide titles. It identifies section names and slide titles that are not unique. It identifies section names with default or placeholder names as an indicator that the name is not descriptive, but it cannot otherwise verify that headings are descriptive.
    • Excel: By default, Excel requires workbooks to have unique sheet names. The accessibility checker identifies sheet names with default or placeholder names as an indicator that the name is not descriptive, but it cannot otherwise verify that headings are descriptive.
  • Ally in HuskyCT:
    • Text Editor: Ally identifies content that skips heading levels and content with empty headings.
    • Uploaded Documents: Ally identifies content that skips heading levels. It also identifies documents without built-in headings when the content meets a minimum length: PDFs, minimum of 3 pages; Word documents, minimum of 12 paragraphs; PowerPoint presentations, minimum of 1 title per 7 slides.
    • Other Content: Not checked
  • Adobe Acrobat Pro: The accessibility checker identifies headings that are not in the correct hierarchical order. (Adobe calls this “appropriate nesting.”) It does not identify content that is missing built-in headings.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Reduces cognitive load (interpretation and processing)
  • Visual – Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 1.3.1 – Info and Relationships – Level A
  • Success Criterion 2.4.6 – Headings and Labels – Level AA
  • Success Criterion 2.4.10 – Section Headings – Level AAA
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points (Supported)
  • Standard 8.2 – The course design facilitates readability – 3 points (Supported)
  • Standard 8.3 – Text in the course is accessible – 3 points
UDL Alignment
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 3.2 – Highlight and explore patterns, critical features, big ideas, and relationships
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools
  • Consideration 7.4 – Address biases, threats, and distractions (Supported)

Purpose

Assistive technologies (e.g., screen readers, refreshable Braille displays) may skip content in headers and footers as well as Word document text boxes. Any learner, regardless of disability, viewing Word with the “Separate Pages” setting turned off also will not see header and footer content.

Implementation

In PowerPoint, place essential information in the document’s body by using the proper placeholders, when possible. Using slide placeholders helps all learners by making text visible in the outline view.

How-to Guides
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports visual customization and assistive technology access
  • Visual – Supports visual customization; Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 1.3.2 – Meaningful Sequence – Level A
Quality Matters Alignment
  • Standard 8.2 – The course design facilitates readability – 3 points
UDL Alignment
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

Screen readers generally announce or display “link” followed by the text of the link. Keyboard users and “screen reader users often navigate from link to link, skipping text in between,” and “screen reader users sometimes obtain an alphabetically-organized list of links” (WebAIM, 2021, Links and hypertext). Therefore, the link text needs to be long enough to be descriptive (but not too long), and it should make sense out of context.

“Click here,” “link to [destination],” or similar directions do not make sense out of context and, in some cases, are redundant. Writing out a URL as link text is usually lengthy, lacks meaning, and should not be used (WebAIM, 2021, Links and hypertext).

The following video demonstrates reading descriptive and non-descriptive links in HuskyCT using NVDA screen reader:

Implementation

Generally, it’s best practice to use the article or resource title as link text. When conveying a short, meaningful, and memorable URL (e.g., ecampus.uconn.edu) for the purpose of facilitating web navigation in the future, it may be appropriate to use the URL as link text.

Within a page or document, use consistent link text for links that go to the same destination, and different link text for links that go to different destinations:

  • Multiple links with the same destination (URL) should use consistent link text where possible. For example, a syllabus has multiple links to https://lms.uconn.edu. The link text uses lms.uconn.edu the first occurrence and HuskyCT for the other instances.
  • Multiple links with the same link text must go to the same destination. For example, a syllabus is listing required software and the accessibility statement for each. Instead of repeating “Accessibility Statement” for each destination, the link text uses “Blackboard Accessibility Statement” and “Microsoft Accessibility Statement.”

Many style guides specify including the URL in the citation entry. This makes sense for printed content but hinders accessibility for digital content. Instead, use the article or resource title within the citation as the link text. Then, omit the written URL or include the written URL as plain, unlinked text.

How-to Guides
Accessibility Checkers
  • Microsoft 365:
    • Word: The accessibility checker identifies links that use the URL or phrases like “click here” as link text when the document meets certain criteria (lengthy, contains many links).
    • Other Products: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Reduces cognitive load (interpretation and processing)
  • Visual – Supports assistive technology navigation
WCAG 2.1 Alignment
  • Success Criterion 2.4.4 – Link Purpose (In Context) – Level A
  • Success Criterion 2.4.9 – Link Purpose (Link Only) – Level AAA
  • Success Criterion 3.2.4 – Consistent Identification – Level AA
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points
UDL Alignment
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

Lists are a great way to organize information and “list structure should be used wherever a logical list is present” (WebAIM, 2024, Semantic structure). Using the correct list structure communicates how items relate to one another.

  • Ordered lists (e.g., 1, 2, 3, …) provide a defined sequence or order for the items in the list.
  • Unordered lists (e.g., bullet points) convey that the items in the list have no specific order.

Creating lists using built-in tools allows assistive technology users to navigate the list and access the relative position of each item in the list (Wolfe, 2020).

Implementation

Don’t create lists by manually typing in numbers, dashes, or indenting. Instead, use the built in “lists” tool.

Lists are recommended as potential replacements for simple tables, since correctly formatted lists are easier to navigate with screen readers (Wolfe, 2020).

Accessibility Checkers
  • Microsoft 365: Not checked. However, when manually typing numbers or dashes to create a list, Microsoft typically converts it to a built-in list automatically.
  • Ally in HuskyCT: Not checked. However, when manually typing numbers or dashes to create a list in the text editor, HuskyCT typically converts it to a built-in list automatically.
  • Adobe Acrobat Pro: The accessibility checker identifies list tags that have issues. It does not verify that lists are specified as lists nor verify correct use of ordered and unordered lists.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Reduces cognitive load (interpretation)
  • Visual – Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 1.3.1 – Info and Relationships – Level A
Quality Matters Alignment
  • Standard 8.2 – The course design facilitates readability – 3 points (Supported)
UDL Alignment
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 3.2 – Highlight and explore patterns, critical features, big ideas, and relationships (Supported)
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

Tables are a great way to present data and allow learners to make visual associations they might not make with a different presentation (WebAIM, 2018, Creating accessible tables).

Tables should only be used to present data or tabular information. Using tables to lay out a page attempts to fix content to a specific position. Use of accessibility tools that magnify or reflow content in layout tables may result in horizontal scrollbars, text overflow, or overlapping elements that impair readability. Screen readers or refreshable Braille displays present layout tables with a linearized reading order (row-by-row) that may be illogical (WebAIM, 2018, Creating accessible tables).

When tables are properly formatted, screen reader users and refreshable Braille display users can navigate through the components of a table. Designating a header row and/or column allows the learner to use “table reading mode” to navigate the data cells and explore their relationships. Without designated headers, the table is difficult to understand — data is not labeled, and the screen reader may read the table straight through row-by-row (WebAIM, 2018, Creating accessible tables).

The following video demonstrates navigating accessible and inaccessible data tables in HuskyCT using NVDA screen reader:

Repeat header rows reprint the header row at the top of each page. Frozen headers freeze the header row or column to the top or left of the spreadsheet, respectively. They reduce the cognitive load of remembering which column or row is which when scrolling through a long table. It’s important to use the repeat header row feature rather than simply duplicating the row, however, as it allows screen reader users to ignore the repeated information as they navigate the table (WebAIM, 2024, [Course materials]).

Implementation

Application
Designating Table Headers

This item requires that tables have headers, which could be:

  • Only the first row
  • Only the first column
  • Both the first row and the first column (W3C WAI, 2023, Tables tutorial)

Many authors create table headers by visually styling the first row and/or first column with bold text or shading. Rather than only changing the appearance, it is important to designate table headers with the appropriate built-in tool, which provides the underlying structure that assistive technologies rely on.

Repeat/Freeze Headers

Repeat header rows or freeze headers when the setting is available within the platform. For example:

  • Word: Repeat header row
  • Excel: Freeze panes (i.e., headers)
  • HuskyCT: No option available

Repeat or freeze headers according to which headers are present:

Table Headers PresentRepeat HeadersFreeze Headers
Only the first rowRepeat row 1 as the header rowFreeze top row
Only the first columnDo not repeat row oneFreeze first column
Both the first row and the first columnRepeat row 1 as the header rowFreeze either the top row or first column. Choose the header that makes the most sense for the data being presented. If unsure, freeze the top row.
Complex Tables

When possible, avoid complex table formatting such as merged cells and multiple levels of headers. Most screen readers fully support complex formatting, but not all. And even when technically accessible to screen reader users, extremely complex tables may be functionally inaccessible due to the cognitive load needed to understand the table (WebAIM, 2018, Creating accessible tables).

Layout Tables

WCAG 2 does not prohibit the use of layout tables, though it’s not recommended in favor of other formatting methods. A layout table may be the best available option in some cases due to platform limitations — for example, creating an aside or callout box in Word. A text box may be skipped or read out of order. Paragraph borders or shading works for a single paragraph, but the styling breaks with paragraph breaks or use of multiple styles (e.g., lists). A single-cell layout table preserves reading order, allows the needed visual styling, and still allows semantic markup (e.g., headings, lists) within its one cell. When creating a layout table, do not designate any header cells. A layout table with header cells is a WCAG failure because it designates header and data relationships that don’t exist (W3C WAI, 2026, Technique F46). Accessibility checkers typically will identify tables missing headers; in this context, that flag should be disregarded.

How-to Guides
Accessibility Checkers
  • Microsoft 365: When creating a table, Microsoft automatically designates the first row and first column as headers. The accessibility checker identifies tables that do not specify a header row or first column. It also identifies tables with split cells, merged cells, or nesting, which can indicate use of tables for layout. It does not verify that tables have repeat/frozen header rows or that tables are used for data (not layout).
  • Ally in HuskyCT: Ally identifies content (text editor, uploaded documents) with tables that do not specify a header row or column. It does not verify that tables have repeat header rows or that tables are used for data (and not layout).
  • Adobe Acrobat Pro: The accessibility checker identifies tables that do not specify a header row or column. It also identifies tables with split or merged cells, which can indicate use of tables for layout. It does not verify that tables are specified as tables, are used for data (not layout), or have repeat header rows.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports visual customization and assistive technology access; Reduces cognitive load (processing)
  • Visual – Supports visual customization; Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 1.3.1 – Info and Relationships – Level A
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points (Supported)
  • Standard 8.2 – The course design facilitates readability – 3 points (Supported)
  • Standard 8.3 – Text in the course is accessible – 3 points
UDL Alignment
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

In spreadsheets (e.g., Excel), data is organized as an undifferentiated grid of cells by default. Converting a data range to a table provides structural components, including a table title and headers. Some screen readers can access these components, allowing users to navigate the data using table reading mode. Using tables also allows for streamlined set-up of total rows, calculated columns, filters, and consistent visual styling.

Large numbers of repeated empty rows and columns can be cumbersome and confusing to navigate. Screen reader users, keyboard users, and other non-mouse users navigate within an Excel spreadsheet primarily by using the arrow key to move between cells. A series of empty rows or columns between elements requires the user to arrow through each blank cell to reach the next element. A visually impaired screen reader user may not see that another element exists and mistakenly conclude there is no more content. Or, if a blank worksheet is present, the visually impaired user may search for nonexistent content (WebAIM, 2021, Microsoft Excel).

Unused columns and rows beyond the populated area of the worksheet can also be visually distracting and slow load times (WebAIM, 2021, Microsoft Excel).

Implementation

Use the formatting required for the data’s intended use. For example, if a range is required for import into statistical software, use a range. Otherwise convert a data range to a table when it makes sense for the data being presented. Be sure to rename your table with a unique, descriptive title.

When a worksheet has multiple data elements, separate elements with only one row or column, where possible. If more visual spacing is desired, increase the row height or column width instead of using multiple empty rows and columns (WebAIM, 2021, Microsoft Excel).

Hide unused rows and columns that extend beyond the populated area of the worksheet. If continuous additions to the spreadsheet are likely, keep an unused row and column visible — this makes it easy to add new rows or columns while reducing visual noise.

How-to Guides
Accessibility Checkers
  • Microsoft 365:
    • Excel: The accessibility checker identifies blank sheets but does not otherwise verify that repeated empty rows are removed or hidden. It does not verify conversion of data ranges to tables.
    • Other Products: Not applicable
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not applicable

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Reduces cognitive load (processing)
  • Physical/Motor – Supports non-mouse navigation
  • Visual – Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • None
Quality Matters Alignment
  • None
UDL Alignment
  • Consideration 4.1 – Vary and honor the methods for response, navigation, and movement (Supported)
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

Most content is authored and viewed as a two-dimensional layout, but many assistive technologies and tools present content as a singular linear sequence (WebAIM, 2017, Designing for screen reader compatibility). Content can be reflowed to change the visual appearance or adapt to different screen sizes (WebAIM, 2024, Responsive design and reflow). Text-to-speech and screen readers convert text to an audio presentation (WebAIM, 2017, Designing for screen reader compatibility), and refreshable Braille displays convert text to a tactile presentation (Accessibility.com, n.d.). Keyboard and other non-mouse users navigate content by tabbing through interactive elements in order (WebAIM, 2024, Keyboard accessibility).

This linear sequence — reading order and navigation order — should be logical and align with the visual layout (WebAIM, 2024, Keyboard accessibility). While often set and checked together, reading order and navigation order are slightly different:

  • Reading order is the linear sequence that content is presented. Content marked as “decorative” is not included in the reading order. The sequence should be logical and align with the visual layout.
  • Navigation order (or focus order) is the linear sequence that interactive elements (e.g., links, buttons, form fields) in content receive “focus” for use. The sequence should be logical and align with the visual layout.

In practice, the reading order and navigation order of a document or webpage typically follow the same linear sequence: the reading order includes all content (except content marked as decorative), while the navigation order includes only interactive elements of that content.

Implementation

Application

This item most often applies to PowerPoint slides and PDFs, though it can apply to other platforms that allow content to be freely arranged, such as HuskyCT document block layouts.

PowerPoint Reading Order and Selection Panes

In PowerPoint, the Reading Order Pane lists every element in the reading order and notes which items are marked as decorative (skipped). Grouped elements are presented as one object with alt text. The Reading Order pane is read from top to bottom.

The Selection Pane lists every element, including individual items within groups and decorative items that are omitted from the reading order. The Selection Pane is read from bottom to top, similar to layers in other design tools.

In view-only uses of PowerPoint slides, the navigation order is essentially the same as the reading order set in the Reading Order Pane.

When providing PowerPoint slides for edit use (e.g., presentation template, collaborative activity), the navigation order of all elements should be set using the Selection Pane.

Using PowerPoint Slide Layouts and Placeholders

In PowerPoint, the reading and navigation order is as follows:

  1. Slide layout placeholders:
    1. Title placeholder
    2. Content in other placeholders
  2. Additional content added to the slide:
    1. Item added first
    2. Item added second
    3. Item added third, and so forth

When possible, create PowerPoint slides by placing content into the slide layout’s existing placeholders. Placeholders are typically already logically ordered in the slide layout settings. Additional content can be correctly sequenced using PowerPoint’s Reading Order pane (WebAIM, 2021, PowerPoint accessibility).

If the slide layouts available don’t accommodate the content needed, edit an existing slide layout or create a new slide layout in the Slide Master view. Use the Reading Order pane to correctly sequence the placeholders. Slides using that layout will then already have a logical reading order.

Managing the Reading/Navigation Order when Creating Custom Figures in PowerPoint

When creating a custom figure or graphic built from many individual elements (shapes, text boxes, lines), consider these practices to simplify setting the reading and navigation order:

  • Use the Selection Pane to rename elements and keep them organized as layers are added, rather than leaving them with default generic names.
  • Group the elements so the entire figure becomes a single item in the Reading Order Pane, rather than requiring each individual element to be sequenced separately. (Refer to Checklist Item 2.3 for information on providing alt text for grouped objects.)
  • Build the graphic in a separate working file, group the finished elements, and export the result as a single image. Place that image in the version of the slides distributed to students. If edits are needed later, return to the original working file, make changes, and export a new image. This approach is especially useful for a graphic that builds incrementally across several slides (e.g., a base image on one slide, with one or two new elements added on each subsequent slide).
HuskyCT Document Block Layouts

HuskyCT Documents allow for responsive block layout. Blocks are read row-by-row from left to right. Organize your content to be logical in this sequence. Double check the sequence by resizing your browser window. Narrow the width of your browser window until the blocks stack into a single column, and confirm that your content is in the intended order.

How-to Guides
Accessibility Checkers
  • Microsoft 365:
    • PowerPoint: The accessibility checker prompts the user to manually check slide reading order for slides that meet certain criteria (e.g., number of objects added, position on the slide). Does not verify that objects have a logical, sequential navigation order.
    • Other Products: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: The accessibility checker prompts the user to manually check page reading order.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports visual customization and assistive technology access
  • Physical/Motor – Supports non-mouse navigation
  • Visual – Supports visual customization; Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 1.3.2 – Meaningful Sequence – Level A
  • Success Criterion 2.4.3 – Focus Order – Level A
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points
  • Standard 8.2 – The course design facilitates readability – 3 points
  • Standard 8.3 – Text in the course is accessible – 3 points (Supported)
UDL Alignment
  • Consideration 4.1 – Vary and honor the methods for response, navigation, and movement
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

Fillable form fields (e.g., text boxes, checkboxes, drop-down lists) need to be properly set up and labeled to be accessed by screen reader, keyboard, and other non-mouse users. Using clear, descriptive labels that are associated with the form controls provides important instructions that make the form easier to use and understand, especially for visually impaired screen reader users (WebAIM, 2020, Creating accessible forms).

Implementation

This item refers to forms created within a document (e.g., Word, PDF). It does not apply to form fields or input elements within HuskyCT or common educational technologies.

This item only applies when fillable form fields are actually used; it does not require use of fillable form fields. For example, many course assignments provide a Word document that students download, complete, and submit. The document may leave an empty space where students can add their response.

The accessibility of fillable form fields in Word documents is mixed, depending on the type of form fields and content controls used by the creator and the type of assistive technology (Goulden & Strohmier, 2022; WebAIM, 2023, PDF accessibility). Given these limitations, use the following order of preference when choosing how to deliver a fillable document:

  1. Use a web-based tool rather than a document-based form. For example, create a test in HuskyCT, add questions, and change the grade category to Assignment.
  2. Use a properly tagged PDF form. Refer to Checklist Item 4.11 for more information on PDF accessibility.
  3. Use a Word document without fillable fields, leaving empty space for students to type their responses directly into the document body. Add instructional text, such as “Type your response here,” to help students (particularly screen reader users) locate where to respond.
  4. Use a Word document with fillable fields, only when the previous options aren’t feasible. To maximize form compatibility with screen readers and keyboard only navigation, use document protections to restrict editing, only allowing filling in forms (Goulden & Strohmier, 2022).
How-to Guides
Accessibility Checkers
  • Microsoft 365:
    • Word: The accessibility checker identifies form fields without titles. It does not verify that labels are clear and descriptive.
    • Other Products: Not applicable
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: The accessibility checker identifies form field tags missing a text description or with other issues. It does not verify that labels are clear and descriptive.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Reduces cognitive load (interpretation)
  • Physical/Motor – Supports non-mouse navigation
  • Visual – Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 1.3.1 – Info and Relationships – Level A
  • Success Criterion 3.3.2 – Labels or Instructions – Level A
  • Success Criterion 4.1.2 – Name, Role, Value – Level A
Quality Matters Alignment
  • Standard 8.2 – The course design facilitates readability – 3 points
  • Standard 8.3 – Text in the course is accessible – 3 points
UDL Alignment
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 4.1 – Vary and honor the methods for response, navigation, and movement
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

A PDF preserves a document’s exact visual layout by recording the position of every character, image, and line on a fixed page, rather than storing content as a logical sequence the way a Word document or webpage does.

“PDFs optimize for print fidelity, not adaptive accessibility. The format was designed to preserve exact visual layout across devices—ensuring a document looks the same whether viewed on a MacBook or printed on a laser jet. But accessibility requires the opposite: content that reflows, adapts, and exposes semantic structure to assistive technology. These goals are fundamentally in tension.” (TestParty, 2026)

Creating an accessible PDF requires adding semantic structure called “tags,” which assistive technologies use to access and navigate the content. Tagging a PDF is the process of identifying (“tagging”) headings, lists, tables, and other elements according to their actual meaning and relationship to one another — not just visual styling. For example, text that visually looks like and functions as a heading needs to be tagged as a heading, allowing assistive technology to interpret it as a heading. The tag structure also creates a linear reading and navigation order. Tagging allows for visual customization, navigation without a mouse, and conversion to different modalities (e.g., text to speech, refreshable Braille display) (TestParty, 2026; WebAIM, 2023, PDF accessibility).

Remediating a PDF for accessibility depends on several layers of processing that build upon one another:

  1. Optical Character Recognition (OCR) converts a scanned image of text into real text. Depending on the quality of the scan, the OCR process often interprets some characters incorrectly or misidentifies imperfections on the scanned page as text. OCR text allows users to highlight, search, and use some text-to-speech tools. However, the content does not have any underlying structure; it functions as one large block of text, which may not have a logical sequence.
  2. Auto-tagging is an AI-powered process that analyzes a document’s visual layout and applies structural tags. Auto-tagging is a good starting point for adding structure to a document, especially for simple documents. More commonly, auto-tagging identifies most text as normal paragraph text, adds heading tags with no logical hierarchy, and confuses bulleted list items, tables, and figures.
  3. Semantic tagging is the manual, technically skilled process of reviewing and correcting a document’s tags so that each element is correctly identified and ordered.

PDF files are most often scanned content or content converted from another digital format. Scanned content may not be available in another format, so a remediated PDF may be the only option to present it digitally. However, content already in a digital format has other options than conversion to PDF. Exporting LaTeX content to HTML preserves the underlying semantic structure that is lost with exports to PDF. Converting a Word or PowerPoint file to a PDF does keep some of the semantic tag structure intact. However, converted PDFs typically require additional “cleanup” work to be correctly tagged and accessible (WebAIM, 2023, PDF accessibility).

Because properly remediating a PDF takes technical skill, specialized software, and considerable time, it typically makes more sense to provide the already accessible original Word or PowerPoint file or web-native format.

Implementation

Application
Instructor-Created Content

When creating content and choosing a format delivery, use the following compliant options:

  1. Option 1: Provide an accessible source document or web-native format, such as Word, PowerPoint, or HTML. (If content is authored in LaTeX, export it to HTML rather than PDF to preserve its structure.) Common methods for sharing source documents include:
    • Share the source file with a Microsoft 365 share link set to “Can view.” Students can view the file in their browser and choose to download a copy for more robust use with assistive technology. Instructor updates to the file update dynamically.
    • Share the source file by uploading it to HuskyCT and selecting the “View and download” file option. Students can view most file formats in HuskyCT, download alternative formats generated by Ally, or download a copy for more robust use with assistive technology. Instructors can use Ally to identify and fix some accessibility issues. Changes to the document require uploading a new file to HuskyCT.
  2. Option 2: Provide a semantically tagged PDF.
    1. Ideal: Semantically tag the PDF, then validate it against PDF/UA, the universal standard for PDF accessibility (Adobe, n.d.).
    2. Acceptable: Semantically tag the PDF, then use Adobe Acrobat Pro’s accessibility checker (preferable) or Ally in HuskyCT to identify and fix other accessibility issues (Checklist Item 4.12).
External and Digital Library Content

PDFs are common in instructional content. Consider the following approaches when selecting PDF materials for your course. Refer to Checklist Item 6.1 for additional information on accessibility of external materials.

  • PDF of a Journal Article: Instead of downloading journal articles and adding them to your course, link directly to the article through the library. Some content is available through multiple databases, and databases differ on the format provided (e.g., PDF only, both HTML and PDF). When available, link to the option that provides an HTML format for the greatest accessibility.
  • Content “Printed” to PDF: Some instructors “print to PDF” online content, most commonly from news sources (e.g., The New York Times, The Wall Street Journal) to avoid paywalls or issues with broken links. This is both an accessibility and copyright issue. More often than not, the article is available through the library. Linking through the library provides a persistent link, complies with copyright, and ensures an accessible format.
  • Other PDFs: When using a scanned PDF or a PDF from an external source (website), follow this general workflow:
    1. Verify that the PDF is semantically tagged and use an accessibility checker to identify other potential issues.
    2. If it’s not accessible: Search other sources to ensure that the content is truly not available in another accessible format.
    3. If another version is not available: Consider whether a different resource can be provided instead.
    4. If this specific resource is required for pedagogical reasons: Remediate the pdf to be semantically tagged.
Non-Compliant Methods

If full compliance is not met, reducing barriers to access with some level of remediation is typically better than no remediation. The following non-compliant remediation strategies are listed from most to least accessible:

  1. An auto-tagged PDF, generated by pdf remediation software or Ally in HuskyCT.
  2. A PDF with OCR, completed with pdf remediation software, Ally in HuskyCT, or during the scanning process.
  3. A scanned PDF with no remediation (i.e., an image of the original with no recognized text).
Tools
  • PDF Remediation Software – Comparison of Accessibility features of Acrobat Pro DC, Nitro PDF Pro and Equidox
    • Adobe Acrobat Pro (“Acrobat”) is the industry standard for PDF remediation and requires purchasing an Adobe Creative Cloud license through the University. (Not to be confused with Adobe Acrobat Reader, which is free for viewing PDFs.)
    • Nitro PDF Pro (“Nitro”) is a PDF editor similar to Adobe Acrobat Pro. Nitro’s accessibility remediation tools are only available on Windows and are much more limited than Acrobat; Nitro may not be able to completely remediate a document. Nitro PDF Pro is available for no charge to faculty and staff, as the University is currently fully subsidizing the licensing costs.
    • Equidox is a cloud-based PDF remediation tool designed to support compliance with accessibility standards. UConn ITS manages a small license. Refer to IT Accessibility’s page on Equidox (PDF Remediation) for more information on features and licensing.
  • PAC (PDF Accessibility Checker) – PAC is a free PDF accessibility checker for Windows; checks for PDF/UA and WCAG requirements.
How-to Guides
Accessibility Checkers
  • Microsoft 365: Not applicable
  • Ally in HuskyCT:
    • Uploaded PDFs: Ally identifies PDFs without OCR and without tags. It is unable to verify that the PDF is semantically tagged.
    • Other Content: Not applicable
  • Adobe Acrobat Pro: The accessibility checker identifies PDFs containing content, annotations, and media without tags. If the PDF is not tagged, it provides the option to “Fix,” which auto-tags the document. When certain tags are present (alt text, form fields, tables, lists, headings), the accessibility checker identifies if they are nested or associated incorrectly. It also identifies documents without a set tab order (for navigation) and prompts manual check of the reading order. Verifying correct use of certain tags, a set tab order, and the reading order all support semantic tagging. It is unable to directly verify that the PDF is semantically tagged.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Supports visual customization and assistive technology access
  • Physical/Motor – Supports non-mouse navigation
  • Visual – Supports visual customization; Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 1.3.1 – Info and Relationships – Level A
  • Success Criterion 1.3.2 – Meaningful Sequence – Level A
  • Success Criterion 2.4.3 – Focus Order – Level A
  • Success Criterion 4.1.2 – Name, Role, Value – Level A
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points
  • Standard 8.3 – Text in the course is accessible – 3 points
UDL Alignment
  • Consideration 1.1 – Support opportunities to customize the display of information
  • Consideration 1.2 – Support multiple ways to perceive information
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 2.2 – Support decoding of text, mathematical notation, and symbols
  • Consideration 4.1 – Vary and honor the methods for response, navigation, and movement
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

Reviewing for and editing errors is an important part of any project, and course design and development is no exception. The accessibility checkers in HuskyCT, Word, PowerPoint, Adobe Acrobat, and other programs can help identify and fix many, but not all, accessibility problems.

Implementation

Some accessibility checkers have false positives, identifying issues that may not represent actual accessibility barriers. A checklist item’s “Accessibility Checkers” section will detail when a particular tool is known to incorrectly identify an issue. Additional false positives or bugs may occur beyond what is noted. Evaluate reported issues in context and address those that apply to the content.

While eCampus encourages faculty to resolve all identified accessibility issues, faculty are minimally expected to fix issues that relate to “Required” checklist items in order to comply with UConn’s Digital Accessibility Policy.

How-to Guides
Accessibility Checkers
  • Microsoft 365: Refer to Rules for the Microsoft 365 Accessibility Checker for issues the built-in Microsoft Accessibility Checker identifies.
  • Ally in HuskyCT: Refer to Ally’s Accessibility Checklist for issues Ally identifies and compiles in the Accessibility Report. Note that Ally only identifies issues in content hosted within the course — content built with the text editor and uploaded files. Ally cannot identify accessibility issues within linked documents, websites, and other content (except for linked YouTube videos missing captions).
  • Adobe Acrobat Pro: Refer to Create and verify PDF accessibility: Accessibility issues for issues the built-in Adobe Accessibility Checker identifies.

Framework Mapping

Disability Categories Supported
  • Auditory – Helps identify barriers
  • Cognitive, Learning, and Neurological – Helps identify barriers
  • Physical/Motor – Helps identify barriers
  • Visual – Helps identify barriers
WCAG 2.1 Alignment
  • Supports identification of success criteria failures
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points (Supported)
  • Standard 8.2 – The course design facilitates readability – 3 points (Supported)
  • Standard 8.3 – Text in the course is accessible – 3 points (Supported)
  • Standard 8.4 – Images in the course are accessible – 2 points (Supported)
  • Standard 8.5 – Video and audio content in the course is accessible – 2 points (Supported)
UDL Alignment
  • None

Section 5. Videos and Audio

Purpose

Video that is grainy or has poor background contrast may be difficult for some learners to see. Audio that has background noise or distortion can be difficult for some learners to hear (W3C Media Working Group, 2015). Poor video and audio are also distracting and unduly increase learners’ cognitive load (ADA Site Compliance, 2024; Kühl et al., 2014).

Implementation

Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Auditory – Supports auditory perception
  • Cognitive, Learning, and Neurological – Reduces cognitive load (processing)
  • Visual – Supports visual perception
WCAG 2.1 Alignment
  • None
Quality Matters Alignment
  • Standard 8.6 – Multimedia in the course is easy to use – 2 points
UDL Alignment
  • Consideration 7.4 – Address biases, threats, and distractions (Supported)

Purpose

Well-designed animated images can make content more accessible and enhance comprehension among learners with cognitive and learning disabilities. However, poorly designed animations can leave some learners, who often have those same disabilities, unable to access the content.

WebAIM advises that “animation should almost always be user controlled or very short in duration” (WebAIM, 2020, Accessible Images). Media that auto-plays or runs without a way to pause or stop increases the cognitive load required to maintain focus while consuming the surrounding content. Learners can experience motion sickness or sensory overload from this unexpected or continuous visual movement or from disorienting motion. Lastly, some flashing and strobing content can potentially trigger a seizure (WebAIM, 2020, Accessible Images).

Implementation

Content must have a way to pause, stop, or hide when it is:

  • Audio lasting more than 3 seconds
  • Moving, blinking, scrolling content lasting more than 5 seconds and presented with other content
  • Auto-updating content

GIFs are one of the most common sources of potentially inaccessible motion in instructional content. Fortunately, PowerPoint automatically adds pause controls to GIFs embedded in slides. Unfortunately, these controls are not available when presenting. Add an animation to automatically hide the GIF within 5 seconds — either have the GIF disappear or have a static image appear on top.

Flashing content should flash no more than 3 times per second or flash below other thresholds for size, color, and contrast. Refer to WebAIM for more information about Graphics that Cause Seizures.

How-to Guides
Tools
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT:
    • Uploaded Images: Ally identifies images that can induce seizures. It does not verify other types of motion.
    • Other Content: Not checked
  • Adobe Acrobat Pro: The accessibility checker identifies elements (e.g., animations, scripts) that can cause seizures. It does not verify other types of motion.

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Reduces cognitive load (processing); Prevents sensory overload and motion sickness; Reduces seizure risk
WCAG 2.1 Alignment
  • Success Criterion 1.4.2 – Audio Control – Level A
  • Success Criterion 2.2.2 – Pause, Stop, Hide – Level A
  • Success Criterion 2.3.1 – Three Flashes or Below Threshold – Level A
  • Success Criterion 2.3.2 – Three Flashes – Level AAA
Quality Matters Alignment
  • Standard 8.6 – Multimedia in the course is easy to use – 2 points
UDL Alignment
  • Consideration 4.1 – Vary and honor the methods for response, navigation, and movement
  • Consideration 7.4 – Address biases, threats, and distractions

Purpose

Meaningful video titles help learners know what to expect from the video (Chen, n.d.). In particular, screen reader users may not be able to see the video thumbnail, which conveys contextual information about the video (New Zealand Government, 2021). Using unique, descriptive video titles helps orient screen reader users as they navigate (Chen, n.d.).

Implementation

How-to Guides
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Cognitive, Learning, and Neurological – Reduces cognitive load (processing)
  • Visual – Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 2.4.2 – Page Titled – Level A
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points (Supported)
UDL Alignment
  • Consideration 2.1 – Clarify vocabulary, symbols, and language structures (Supported)
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools
  • Consideration 7.4 – Address biases, threats, and distractions (Supported)

Purpose

Learners who are hard of hearing or D/deaf need another way to access the audio content of videos, web conferences, and audio recordings, which accurate, complete captions and transcripts provide (W3C WAI, 2021, User experiences…; WebAIM, 2020, Captions…). Captions and transcripts help other learners too; 71% of people without hearing difficulties watch videos with captions (W3C WAI, 2021, User experiences…).

Implementation

Application
Recording Videos with Live Autogenerated Captions

Some recording tools have an option to display captions or subtitles while recording. Do not record videos with captions or subtitles on. Recorded auto-generated captions:

  • May not meet the level of accuracy required by accessibility law and cannot be edited to improve accuracy.
  • Can be distracting to some viewers, particularly due to their delay and inaccuracy.
  • Interfere with accurate captions in the Kaltura player, creating a distracting double-captioned effect that is difficult to read.

Instead, caption videos through Kaltura, which allows for accurate captions that can be toggled on or off by choice.

Captioning Synchronous Virtual Meetings

Do not use PowerPoint’s built-in live captions or subtitles feature while presenting in synchronous online sessions. These captions can be distracting to some learners. And, if the synchronous session is recorded, these captions are burned into the recording and cannot be turned off.

Instead, use the video conferencing platform (i.e., Microsoft Teams) to provide captions, which allows participants to toggle captions on or off by choice.

(PowerPoint’s live captions feature is best for in-person presentations or when using a conferencing tool that doesn’t offer its own live captioning option.)

Captioning Videos or Audio Files with Kaltura

Kaltura is the platform through which the University captions videos and audio files. Media added to Kaltura are automatically machine-captioned. Machine captions are about 70–95% accurate, so faculty must review and edit machine-generated captions for completion and accuracy.

How-to Guides
Accessibility Checkers
  • Microsoft 365:
    • PowerPoint: The accessibility checker identifies embedded video and audio media without time-based closed captions. Auto-generated captions are not considered to be valid captions, which supports accuracy and completeness. The accessibility checker will provide a false warning if a video has open captions or the audio has a written transcript instead of time-based captions.
    • Other Products: Not checked
  • Ally in HuskyCT:
    • YouTube Videos: Ally identifies YouTube videos (hyperlinked or embedded) without closed captions. Auto-generated captions are not considered to be valid captions, which supports accuracy and completeness. Ally will provide a false warning if a video has open captions.
    • Other Content: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Auditory – Provides equivalent alternative to audio
WCAG 2.1 Alignment
  • Success Criterion 1.2.1 – Audio-only and Video-only (Prerecorded) – Level A
  • Success Criterion 1.2.2 – Captions (Prerecorded) – Level A
  • Success Criterion 1.2.4 – Captions (Live) – Level AA
Quality Matters Alignment
  • Standard 8.5 – Video and audio content in the course is accessible – 2 points
UDL Alignment
  • Consideration 1.2 – Support multiple ways to perceive information
  • Consideration 2.4 – Address biases in the use of language and symbols

Purpose

W3C Web Accessibility Initiative (WAI) explains that “description provides content to people who are blind and others who cannot see the video adequately. It describes the visual information needed to understand the content, including text displayed in the video” (W3C WAI, 2022, Audio content…). This may be recorded by a narrator as a separate audio track, especially for TV shows and movies. However, the best way to provide description in instructional videos is with integrated description—integrating all the visual information into the main audio (W3C WAI, 2022, Audio content…; WebAIM, 2020, Captions…).

Implementation

How-to Guides
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Visual – Provides equivalent alternative to visuals
WCAG 2.1 Alignment
  • Success Criterion 1.2.3 – Audio Description or Media Alternative – Level A
  • Success Criterion 1.2.5 – Audio Description (Prerecorded) – Level AA
Quality Matters Alignment
  • Standard 8.5 – Video and audio content in the course is accessible – 2 points
UDL Alignment
  • Consideration 1.2 – Support multiple ways to perceive information

Purpose

Even videos made as accessible as possible have limitations. Providing accessible digital copies of documents shown in videos allows learners to use assistive technology as needed to interact with the document and fully engage with the content.

Implementation

Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Auditory – Supports sequential consumption
  • Cognitive, Learning, and Neurological – Reduces cognitive load (processing); Supports visual customization
  • Physical/Motor – Supports non-mouse navigation
  • Visual – Supports visual customization; Provides alternative to visuals; Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Success Criterion 1.2.3 – Audio Description or Media Alternative – Level A (Supported)
Quality Matters Alignment
  • Standard 8.5 – Video and audio content in the course is accessible – 2 points (Supported)
UDL Alignment
  • Consideration 1.1 – Support opportunities to customize the display of information
  • Consideration 1.2 – Support multiple ways to perceive information
  • Consideration 4.1 – Vary and honor the methods for response, navigation, and movement
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools

Purpose

Kaltura is UConn’s video creation and hosting service, and it has been vetted by the University to comply with accessibility best practice, policy, and the law. In addition to hosting instructor-created videos and audio files, Kaltura can also stream content from YouTube, allowing YouTube videos to benefit from the Kaltura player accessibility features.

  • Captions: Kaltura media is automatically machine captioned, and machine captions can be edited for accuracy. Auto-captioned YouTube videos can be added to Kaltura for accurate captions. Kaltura is the platform through which the University orders professional captioning.
  • Interactive transcripts: Captioned media also provides the text in transcript form, highlighting text phrases as they’re spoken.
  • Chapters: Kaltura videos can be organized into chapters, which allows learners to know what to expect and navigate through the video. Kaltura automatically adds chapters to some videos based on PowerPoint slide transitions.
  • Variable playback speed: The Kaltura media player allows for variable playback speed accommodating learners that need to speed up or slow down the video.
  • Accessible player: The Kaltura media player supports screen reader use and keyboard only navigation. It is also colorblind-compliant and high contrast.
  • Customizable speaker visibility: Recording and sharing videos with Kaltura allows for dual feed capture which is helpful for learners that use mouth movement to understand spoken language. These feeds can be visible or hidden by the viewer as needed to reduce distraction.

(W3C Media Working Group, 2015; W3C WAI, 2021, Media players; W3C WAI, 2021, User experiences; W3C WAI, 2022, Audio content…; WebAIM, 2020, Captions…)

Implementation

This item applies to instructor-created video and audio files. YouTube videos with accurate and complete captions may be embedded with YouTube instead of Kaltura.

This item does not require that media be recorded with Kaltura, only that the completed media file be uploaded and shared using Kaltura. However, some accessibility features require recording and sharing media with Kaltura.

How-to Guides
Accessibility Checkers
  • Microsoft 365: Not checked
  • Ally in HuskyCT: Not checked
  • Adobe Acrobat Pro: Not checked

Framework Mapping

Disability Categories Supported
  • Auditory – Provides equivalent alternative to audio; Supports sequential consumption
  • Cognitive, Learning, and Neurological – Reduces cognitive load (interpretation and processing); Supports visual customization
  • Physical/Motor – Supports non-mouse navigation
  • Visual – Supports visual customization; Supports assistive technology access and navigation
WCAG 2.1 Alignment
  • Reduces risk of success criteria failures
Quality Matters Alignment
  • Standard 8.5 – Video and audio content in the course is accessible – 2 points
  • Standard 8.6 – Multimedia in the course is easy to use – 2 points
UDL Alignment
  • Consideration 1.1 – Support opportunities to customize the display of information
  • Consideration 1.2 – Support multiple ways to perceive information
  • Consideration 4.1 – Vary and honor the methods for response, navigation, and movement
  • Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools
  • Consideration 7.4 – Address biases, threats, and distractions (Supported)

Section 6. External Content

Purpose

Many instructors assign instructional materials, assessments, or other content that are from another source. Course content created by a third party should be as accessible as instructor-created course content.

Implementation

Application

Select third-party content that is accessible based on the required standards in this checklist. If something you select is not already accessible, remediate that resource or create an alternate accessible format to meet required checklist items.

Publisher-Provided Instructor Resources

Publishers commonly provide instructor resources, such as PowerPoint slides and test banks, to accompany their textbooks. Despite publisher accessibility commitments, accessibility of these materials is not guaranteed; these materials should be examined before adoption. If publisher materials are not accessible, follow this general workflow:

  • Ask the publisher to make them accessible (i.e., “conform to WCAG 2.1, Level AA”).
  • If the publisher does not comply: Adopt an alternative textbook.
  • If this specific textbook is required for pedagogical reasons: Remediate the materials or create your own.
Websites

Many instructional materials direct students to read a webpage or explore a website, and this instructional content should also be accessible. A full website accessibility conformance audit requires specialized expertise. If (and when) accessibility issues are identified, faculty cannot modify the content directly to make it accessible. Lastly, website conformance may degrade between when a faculty member reviews the content and students encounter it in a course. For these reasons, faculty review of external websites is best focused on checking for conspicuous barriers to accessing the instructional content.

Though this is not an exhaustive list, check for the following when reviewing a website for use as required instructional content:

  • Is any instructional content, such as a table or equation, presented as an image rather than real text or mathematical notation? (Checklist Item 1.4)
  • Are any instructional figures missing alt text or a long description? (Checklist Item 2.3)
  • Does any instructional content have insufficient contrast? (Checklist Item 3.1)
  • Does any content convey meaning through a sensory characteristic, such as color, alone? (Checklist Item 3.2)
  • If the site includes videos, are they missing accurate captions? (Checklist Item 5.4)

If any of these accessibility issues are present, follow this general workflow:

  1. Consider whether the inaccessible content is truly required.
    For example, a table presented as an image might be supplemental to the instructional content. When assigning the webpage as a required instructional material, note that the image of the table is not part of the assigned reading.
  2. If the content is required: Consider whether a different resource can be used to provide similar content.
  3. If this specific resource is required for pedagogical reasons: Create an alternate format for the inaccessible element.
    For example, an image of a graph does not have a text alternative. The instructor could create a long description for the graph in a Word document and place the document in the course. When assigning the webpage as a required instructional material, note that the accompanying Word document has the text alternative for the graph.
PDFs

Refer to Checklist Item 4.11 for suggested workflows to address the accessibility of external PDFs.

How-to Guides
Tools

Framework Mapping

Disability Categories Supported
  • Auditory
  • Cognitive, Learning, and Neurological
  • Physical/Motor
  • Visual
WCAG 2.1 Alignment
  • Reduces risk of success criteria failures
Quality Matters Alignment
  • Standard 8.1 – Course navigation facilitates ease of use – 3 points
  • Standard 8.2 – The course design facilitates readability – 3 points
  • Standard 8.3 – Text in the course is accessible – 3 points
  • Standard 8.4 – Images in the course are accessible – 2 points
  • Standard 8.5 – Video and audio content in the course is accessible – 2 points
  • Standard 8.6 – Multimedia in the course is easy to use – 2 points
UDL Alignment
  • None

Appendix

The guidance for each checklist item explains the disability categories a checklist item supports, its alignment with relevant accessibility frameworks, why the item matters, and resources for implementing it. The following sections explain how to interpret these fields.

Each checklist item has a requirement level of either Required or Recommended.

  • Required – These items:
    • Meet accessibility requirements (i.e., meet WCAG 2.1, Level AA Success Criteria required for Title II)
    • Identify accessibility issues (i.e., identify success criteria failure)
    • Reduce the risk of introducing accessibility issues (i.e., reduce the risk of success criteria failure)
  • Recommended – These items address accessibility best practices beyond Title II.

Faculty developing online courses with comprehensive support from eCampus are expected to meet all required items on the eCampus Accessibility Checklist at an 85% or better level. This threshold aligns with the requirement that faculty meet all essential (3-point) QM standards at an 85% or better level for successful completion of the comprehensive course design and development process. Meeting required accessibility checklist items at this level is treated as evidence that QM Specific Review Standards 8.1–8.6 have been met.

This expectation does not replace or reduce faculty members’ existing responsibility to comply with the UConn Digital Accessibility Policy, which applies whether a course is developed independently or with eCampus funding or support.

Checklist Completion and Legal Conformance

Complying with Title II requires conformance with WCAG 2.1, Level AA. The checklist addresses the success criteria most commonly applicable to online course development across disciplines, but it does not address every Success Criterion or every possible use of digital content.

Certain materials or practices may introduce accessibility requirements not covered by the checklist. Therefore, meeting checklist items to any degree does not guarantee or imply that specific accessibility laws, regulations, or policies are met.

Planning and Prioritizing Accessibility Work

Accessibility work is more manageable when a course is reviewed in smaller components, such as individual pages, documents, videos, and activities. Prioritize identifying and addressing barriers within your control. Do not allow one unresolved issue to prevent improvements throughout the course.

Some accessibility issues may involve required technologies or materials that cannot be directly modified or remediated. In such cases, consider how learners could access the essential information or activity through another equally effective alternative. Any alternative should be consistent with the UConn Digital Accessibility Policy and Policy Procedures.

Why is this checklist item important?

The Purpose section explains why a checklist item matters:

  • How the content, technology, and the person using it interact
  • What goes wrong when they don’t align
  • What makes the experience more accessible

If applicable, this section may also include:

  • What key terms mean
  • Common misunderstandings about the item
  • How accessibility barriers overlap with poor design to create broader barriers for most or all users

When and how do I implement this checklist item?

The Implementation section may include:

  • When to apply a checklist item:
    • When the item applies, and when it doesn’t
    • What the item does and doesn’t require, especially where it could be misread as requiring more than it does
  • How to apply a checklist item:
    • High-level descriptions of what to do
    • Technical details needed to carry out the item
    • How the item works or is handled differently across platforms or tools
    • How to apply the item in more complex or less obvious situations
    • Different approaches to meeting the item, and considerations for choosing an approach
    • Common mistakes with implementation
  • When to deviate from applying a checklist item:
    • Best practices that go beyond what the item strictly requires
    • Specific situations where an otherwise discouraged approach may be acceptable (or even the best option)

How-to Guides

When included, the How-to Guides section contains links to selected external resources on how to implement a checklist item. Linked resources are typically step-by-step instructions from the Knowledge Base or a platform’s support documentation (e.g., Microsoft Support, Blackboard Help Center). For more complex items, linked resources may also cover detailed best practices and tutorials.

Tools

When included, the Tools section contains links to external tools and software that help implement or verify a checklist item. In addition to identifying issues, these tools typically provide guidance on how to resolve them, and some integrate a workflow to fix the issue directly within the tool.

Accessibility Checkers

The Accessibility Checkers section contains information on the availability and limitations of built-in accessibility checkers for common platforms.

The Framework Mapping section identifies the disability categories a checklist item supports, along with how the item aligns with WCAG 2.1, Quality Matters (QM), and Universal Design for Learning (UDL). These three frameworks are related but distinct:

  • Universal Design for Learning (UDL) provides a broad framework for designing flexible learning experiences that anticipate learner variability. UDL addresses access to course content as well as learner engagement, learning strategies, and agency.
  • WCAG 2.1, Level AA, is a technical accessibility standard addressing access to digital content and instruction; Title II requires courses to meet this standard.
  • Quality Matters (QM) General Standard 8 was built on both UDL and WCAG, evaluating accessibility and usability as elements of effective course design. Where they overlap, WCAG requirements are generally more specific than QM. However, QM also addresses usability best practices, some of which overlap with UDL’s broader focus on learner engagement and experience.

Each checklist item is designed to reduce or eliminate barriers that people with disabilities may experience when accessing digital content.

The Disability Categories Supported field identifies the broad disability categories supported by the item. For each disability category listed, the annotation also lists ways the item supports access for people with disabilities in that category (e.g., reduces cognitive load, supports non-mouse navigation, supports visual customization).

The categories and types of support listed are illustrative rather than exhaustive. The same type of support may apply to multiple disability categories. People with the same disability may use different supports. And some people may use different supports in different contexts. The disability categories provide general context about who may be supported by an item without implying a fixed relationship between a disability category and a particular type of support.

Disabilities, Barriers, and Assistive Technologies

People may experience barriers to accessing digital content for a variety of reasons, whether it be a disability from birth, illness, or an accident, a temporary impairment, age-related impairments, or a situational limitation. Some individuals may not identify as having a disability even if they do experience functional limitations.

While not an exhaustive list, types of disabilities include the following (Kemény & Kjellstrand, 2023; W3C WAI, 2024, Diverse abilities and barriers).

CategoryDisabilities and ImpairmentsBarriersAssistive Technology
Auditory Disabilities
  • Hard of hearing
  • Deafness
Audio content without captions or transcripts
  • Captions (Closed Captions – CC)
    • Communication Access Realtime Translation (CART)
    • Auto-generated live captions
  • Transcripts
  • Speech-to-text technology
Cognitive, Learning, and Neurological Disabilities
  • Intellectual disabilities
  • Learning disabilities
  • Mental health disabilities
  • Memory impairments
  • Neurodivergence (e.g., ADHD, Autism Spectrum Disorder)
  • Seizure disorders
  • Vestibular disorders
  • Content not designed for use with a screen reader
    • Complex navigation and page layouts
  • Content not organized with headings or structural elements
  • Moving or blinking content that cannot be turned off
  • Screen reader or text-to-speech technology
  • Custom color themes and filters
  • Reduced motion settings
Physical/Motor Disabilities
  • Amputation
  • Arthritis
  • Reduced dexterity
  • Muscle weakness/damage
  • Paralysis
  • Tremors and spasms
  • Content not designed for keyboard navigation
    • Complex navigation and page layouts
    • Controls as images without equivalent text alternatives
  • Alternative controls:
    • Keyboard only
    • Voice controls
    • Sip and puff (SNP) switch
    • Eye tracking
    • Head wand
Speech Disabilities
  • Apraxia
  • Stuttering
  • Muteness
  • Offering voice as the only way to communicate
  • Text-to-speech technology
  • Augmentative and Alternative Communication (AAC) devices
Visual Disabilities
  • Blindness
  • Color Vision Deficiency (CVD; color blindness)
  • Low vision
  • Content not designed for keyboard navigation:
    • Complex navigation and page layouts
    • Controls as images without equivalent text alternatives
    • Images missing alternative (alt) text
  • Videos without text or audio descriptions
  • Content that cannot be resized or viewed with custom color themes
  • Insufficient contrast
  • Reliance on sensory characteristics or color alone to convey meaning
  • Screen reader
  • Refreshable Braille display
  • Screen magnification
  • Customized color themes and filters
  • Color identification apps

Refer to W3C WAI’s Diverse Abilities and Barriers page for more information about each type of disability and common barriers.

Can learners access the content?

Web Content Accessibility Guidelines (WCAG) define measurable requirements for making digital content accessible. WCAG is developed by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C), an international organization that develops web standards (WebAIM, 2020, WCAG). The eCampus Accessibility Checklist translates relevant WCAG requirements into practices applicable to online course development.

The WCAG 2.1 Alignment field identifies how a checklist item relates to WCAG success criteria (i.e., requirement). The checklist item may:

  • Address the success criterion as a whole
  • Help meet the success criterion
  • Help avoid failure of the success criterion

Because several practices may contribute to meeting one success criterion, completing one aligned checklist item does not necessarily satisfy the entire success criterion.

WCAG 2.1 vs. 2.2

WCAG 2.2 is the current version of WCAG (WebAIM, 2020, WCAG). This guide aligns with WCAG 2.1 because Title II regulation uses WCAG 2.1, Level AA as the technical standard.

WCAG 2.2 adds several new requirements to WCAG 2.1, primarily related to interactive content and functionality (W3C WAI, 2023, What’s New in WCAG 2.2). Faculty who meet WCAG 2.1, Level AA when creating course content will also meet most, if not all, WCAG 2.2, Level AA requirements within their control.

How WCAG Is Structured

WCAG provides “layers of guidance” to make content more accessible.

  1. Principles – WCAG is founded on four user-centered Principles of Accessibility, also referred to as “POUR.” These principles provide a constant framework for accessibility even as technology and techniques change.
    1. Perceivable: Content is presented in a way that a user can perceive, regardless of which sense is used (i.e., sight, sound, or touch).
    2. Operable: Users can navigate and interact with the content, including users who do not use a mouse. The design does not cause physical reactions or seizures.
    3. Understandable: Content and layout are clear, consistent, and predictable. The design facilitates readability and reduces cognitive load.
    4. Robust: Users can access content using a variety of devices and assistive technology (Equalize Digital, 2020; WebAIM, 2021, Constructing a POUR website).
  2. Guidelines – Each principle contains guidelines, which are general goals that creators should work toward to make content more accessible (W3C, 2025, WCAG 2.1).
    • Example: Guideline 1.2 – Time-based Media – Provide alternatives for time-based media.
  3. Success Criteria (SC) – Each guideline contains success criteria (SC). Framed as specific outcomes, SC provide testable methods for measuring conformance (W3C, 2025, WCAG 2.1). Conformance is all or nothing — If the SC is not met 100% of the time, it is a failure of the SC (W3C WAI, 2026, Understanding conformance).
    • Example: Success Criterion 1.2.2 Captions (Prerecorded), Level A – Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.
  4. Levels of Conformance – Each SC has a level of conformance: Level A (lowest), AA, and AAA (highest). The levels are cumulative, meaning Level AA conformance (required for Title II) requires meeting all Level A and Level AA success criteria (W3C, 2025, WCAG 2.1). Conformance is all or nothing — failure of one SC is considered non-conformance of the level (W3C WAI, 2026, Understanding conformance).
  5. Techniques and Failures – WCAG supporting documents provide common practices that meet and fail each criterion (W3C, 2025, WCAG 2.1).
WCAG for Non-Web Content

WCAG 2 was written for web content and does not directly address non-web documents and software. WCAG applies directly to content created within HuskyCT’s content editor because it is presented as web content in a browser. However, some WCAG success criteria require interpretation to apply to non-web course materials, such as Word documents and PowerPoint presentations. Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT) interprets how WCAG 2 success criteria can be applied to non-web information and communications technologies (ICT) (W3C WAI, 2026, WCAG2ICT Overview; W3C, 2025, WCAG2ICT).

Is the content usable and well-designed?

Online courses designed with comprehensive support from eCampus must pass a Quality Matters (QM) review to meet evidence-based standards of course design quality. One of these standards is General Standard 8 on Accessibility and Usability.

The Quality Matters Alignment field identifies how a checklist item relates to a Specific Review Standard within General Standard 8. Many checklist items address practices identified in aligned Specific Review Standard annotation. If the checklist item is not a practice identified in the aligned Specific Review Standard annotation, but the item supports the broader intended outcome for the standard, the Quality Matters Alignment field will append “(Supported).” Because several practices may contribute to meeting one Specific Review Standard, completing one aligned checklist item does not necessarily meet the entire standard.

Does the design support variability in learning?

Universal Design for Learning (UDL) is “a framework developed by CAST to improve and optimize teaching and learning for all people based on scientific insights into how humans learn” (CAST, 2024). The UDL Guidelines are a tool used to implement the UDL framework (CAST, 2024). Foundational to UDL is the principle that designing for those “in the margins” helps the design work better for everyone (CAST, 2010).

The UDL Alignment field identifies how a checklist item relates to a UDL Consideration (i.e., strategy to meet a Guideline). Many checklist items address practices identified in aligned Considerations. If the checklist item is not a practice identified in aligned Considerations, but the item supports the broader intended outcome for the Considerations, the UDL Alignment field will append “Supported.” Because several practices may contribute to meeting one Consideration, completing one aligned checklist item does not necessarily meet the entire Consideration.

While the checklist items are technical in nature, considering the UDL framework more broadly allows for a more conceptual approach to creating student-centered and accessible courses.

Overview of the UDL Guidelines

The UDL Guidelines provide concrete considerations for applying the UDL framework. To summarize the UDL Guidelines most simply, they emphasize providing learners with options in their learning.

Creating accessible digital content specifically addresses the following UDL Guidelines and Considerations:

  1. Guideline 1 – Design Options for Perception
    1. Consideration 1.1 – Support opportunities to customize the display of information
    2. Consideration 1.2 – Support multiple ways to perceive information
  2. Guideline 2 – Design Options for Language & Symbols
    1. Consideration 2.1 – Clarify vocabulary, symbols, and language structures
    2. Consideration 2.2 – Support decoding of text, mathematical notation, and symbols
    3. Consideration 2.4 – Address biases in the use of language and symbols
    4. Consideration 2.5 – Illustrate through multiple media
  3. Guideline 3 – Design Options for Building Knowledge
    1. Consideration 3.2 – Highlight and explore patterns, critical features, big ideas, and relationships
  4. Guideline 4 – Design Options for Interaction
    1. Consideration 4.1 – Vary and honor the methods for response, navigation, and movement
    2. Consideration 4.2 – Optimize access to accessible materials and assistive and accessible technologies and tools
  5. Guideline 7 – Design Options for Welcoming Interests & Identities
    1. Consideration 7.4 – Address biases, threats, and distractions

Learn more about Universal Design for Learning with the interactive UDL Guidelines graphic organizer.

Additional Resources

  1. Accessibility.com. (n.d.). Refreshable Braille display.
  2. ADA Site Compliance. (2024, January 3). The impact of audio quality on accessibility: Tips for clear sound delivery.
  3. ADA.gov. (2024, April 8). Fact sheet: New rule on the accessibility of web content and mobile apps provided by state and local governments. U.S. Department of Justice, Civil Rights Division.
  4. Adobe. (n.d.). What is PDF/UA?.
  5. Blackboard LMS Help Center (2026, July 14). Set your language [Student guide].
  6. Blackboard LMS Help Center. (2026, August 26). Math editor [Instructor guide].
  7. Blom, S. (2023, September 7). Re: set document language in word [Comments on online forum post]. Microsoft Q&A.
  8. CAST. (2010, January 6). UDL at a glance [Video]. YouTube.
  9. CAST. (2024). The UDL guidelines.
  10. Chen, A. (n.d.). Write descriptive page titles. Access Guide.
  11. Equalize Digital. (2020, February 5). Web accessibility: POUR acronym explained.
  12. Goulden, J. & Strohmier, J. (2022, June 21). Making fillable forms accessible: What to consider. Vispero.
  13. Jones, B. [CyberTaz]. (2020, August 11–12). Re: Default language in Word [Comments on online forum post]. Microsoft Q&A.
  14. Kemény, P., & Kjellstrand, S. (2023, October). CPACC Body of Knowledge. International Association of Accessibility Professionals.
  15. Kühl, T., Eitel, A., Damnik, G., & Körndle, H. (2014). The impact of disfluency, pacing, and students’ need for cognition on learning with multimedia. Computers in Human Behavior, 35, 189–198.
  16. Linscott, M. (2025, December 5). Using color to code your learning. Purdue Global Academic Success Center.
  17. MathType. (n.d.). Accessibility in MathType for HTML editors. Wiris.
  18. Microsoft Support. (n.d.). Check spelling and grammar in a different language.
  19. Microsoft Support. (n.d.). Editing equations created using Microsoft Equation Editor.
  20. Microsoft Support. (n.d.). Linear format equations using UnicodeMath and LaTeX in Word.
  21. Microsoft Support. (n.d.). Make your PowerPoint presentations accessible to people with disabilities.
  22. Microsoft Support. (n.d.). Make your Word documents accessible to people with disabilities.
  23. New Zealand Government. (2021, June 24). Title attribute, if video published in an <iframe>. Digital.govt.nz.
  24. TestParty. (2026, February 1). Why PDFs break accessibility (and what to do instead).
  25. The University of Melbourne. (n.d.). Accessible equations.
  26. W3C. (2025, May 6). Web Content Accessibility Guidelines (WCAG) 2.1. World Wide Web Consortium (W3C).
  27. W3C. (2025, December 11). Guidance on Applying WCAG 2 to Non-Web Information and Communications Technologies (WCAG2ICT). World Wide Web Consortium (W3C).
  28. W3C Media Working Group. (2015, December 3). Media accessibility user requirements. World Wide Web Consortium (W3C).
  29. W3C Web Accessibility Initiative (WAI). (2017, April 12). Images tutorial: Images of text. World Wide Web Consortium (W3C).
  30. W3C Web Accessibility Initiative (WAI). (2021, November 29). Media players. World Wide Web Consortium (W3C).
  31. W3C Web Accessibility Initiative (WAI). (2021, November 29). User experiences and benefits to organizations. World Wide Web Consortium (W3C).
  32. W3C Web Accessibility Initiative (WAI). (2022, August 31). Audio content and video content. World Wide Web Consortium (W3C).
  33. W3C Web Accessibility Initiative (WAI). (2023, February 16). Tables tutorial. World Wide Web Consortium (W3C).
  34. W3C Web Accessibility Initiative (WAI). (2023, October 5). What’s New in WCAG 2.2. World Wide Web Consortium (W3C).
  35. W3C Web Accessibility Initiative (WAI). (2024, June 25). Diverse abilities and barriers. World Wide Web Consortium (W3C).
  36. W3C Web Accessibility Initiative (WAI). (2025, July 15). Technique PDF7: Performing OCR on a scanned PDF document to provide actual text. World Wide Web Consortium (W3C).
  37. W3C Web Accessibility Initiative (WAI). (2025, September 16). Understanding SC 1.3.3: Sensory characteristics (Level A). World Wide Web Consortium (W3C).
  38. W3C Web Accessibility Initiative (WAI). (2025, September 16). Understanding SC 1.4.1: Use of color (Level A). World Wide Web Consortium (W3C).
  39. W3C Web Accessibility Initiative (WAI). (2026, January 21). WCAG2ICT Overview. World Wide Web Consortium (W3C).
  40. W3C Web Accessibility Initiative (WAI). (2026, March 6). Technique F46: Failure of Success Criterion 1.3.1 due to using th elements, caption elements, or non-empty summary attributes in layout tables. World Wide Web Consortium (W3C).
  41. W3C Web Accessibility Initiative (WAI). (2026, June 28). Understanding SC 1.4.5: Images of text (Level AA). World Wide Web Consortium (W3C).
  42. W3C Web Accessibility Initiative (WAI). (2026, September 6). Understanding SC 1.1.1: Non-text content (Level A). World Wide Web Consortium (W3C).
  43. W3C Web Accessibility Initiative (WAI). (2026, September 20). Understanding conformance. World Wide Web Consortium (W3C).
  44. WebAIM. (2017, April 21). Designing for screen reader compatibility.
  45. WebAIM. (2018, February 9). Creating accessible tables.
  46. WebAIM. (2020, April 16). Creating accessible forms.
  47. WebAIM. (2024, August 30). Semantic structure: Regions, headings, and lists.
  48. WebAIM. (2020, July 1). Captions, transcripts, and audio descriptions.
  49. WebAIM. (2020, September 21). Web Content Accessibility Guidelines.
  50. WebAIM. (2020, September 22). Accessible images.
  51. WebAIM. (2020, October 22). Text/typographical layout.
  52. WebAIM. (2020, October 27). Typefaces and fonts.
  53. WebAIM. (2021, January 9). Contrast and color accessibility.
  54. WebAIM. (2021, February 26). PowerPoint accessibility.
  55. WebAIM. (2021, August 12). Visual disabilities.
  56. WebAIM. (2021, August 24). Document and content language.
  57. WebAIM. (2021, October 4). Constructing a POUR website.
  58. WebAIM. (2021, October 19). Alternative text.
  59. WebAIM. (2021, October 19). Links and hypertext.
  60. WebAIM. (2021, November 29). Microsoft Excel: Optimizing spreadsheet accessibility.
  61. WebAIM. (2023, May 31). PDF accessibility.
  62. WebAIM. (2023, December 21). Word and PowerPoint accessibility evaluation guide.
  63. WebAIM. (2024, January). [Course materials]. Accessible documents: Word, PowerPoint, & Acrobat. Canvas.
  64. WebAIM. (2024, August 30). Headings.
  65. WebAIM. (2024, October 30). Responsive design and reflow.
  66. WebAIM. (2026, May 14). Keyboard accessibility.
  67. White, J. J. G. (2019). The accessibility of mathematical notation on the web and beyond. Journal of Science Education for Students with Disabilities, 23(1), 1–14.
  68. Wolfe, A. (2020). Accessible lists. Accessibility Across the Curriculum.