Title II of the Americans with Disabilities Act (ADA) requires that our courses ensure equal access and opportunity for people with disabilities. How we can do this is by understanding and implementing acts outlined by the Web Content Accessibility Guidelines (WCAG) 2.1, a set of international standards developed by the World Wide Web Consortium (W3C) to make web content more accessible to people with disabilities. WCAG 2.1 builds on WCAG 2.0 by addressing more accessibility needs—especially for users with low vision, cognitive and learning disabilities, and mobile users.

The rubric below can be used to reference various accessibility standards, expectations, and tools to be incorporated into classrooms to improve accessibility. You can find more detailed explanations of these tools on the Best Practices Page on this site, or by visiting the MSU Library's Accessibility Page.

There are many accessibility tools and concepts we can apply in our classrooms, and it can be easy to get overwhelmed—try to select one or two to focus on at a time. Later, when you’re feeling comfortable with these and are ready to add in a new concept, choose another from the rubric.

Accessibility is a process and progression; each step we take moves us closer to a more accessible and supportive campus.

*Note that this rubric is not an exhaustive list of accessibility tools. You may need to include additional or alternative tools to ensure that your courses are fully accessible.

 

WCAG Core Principles: POUR

WCAG 2.1 is organized around four key principles, often abbreviated as POUR:

Information and user interface components must be presentable to users in ways they can perceive.

  • Text alternatives: Provide alt text for images, captions for videos, and transcripts for audio.
  • Adaptable content: Ensure content can be presented in different ways (e.g., simpler layout) without losing meaning.
  • Distinguishable: Make it easier for users to see and hear content (e.g., sufficient color contrast, text resizing).

User interface components and navigation must be operable.

  • Keyboard accessible: All functionality should be available from a keyboard.
  • Enough time: Provide users enough time to read and interact with content.
  • Seizure and physical reaction safety: Avoid content that flashes more than 3 times per second.
  • Navigable: Provide clear navigation and ways to find content (e.g., headings, consistent menus).

Information and operation of the user interface must be understandable.

  • Readable: Use clear and simple language where possible.
  • Predictable: Make web pages operate in predictable ways.
  • Input assistance: Help users avoid and correct mistakes (e.g., error suggestions and labels in forms).

Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.

  • Compatible: Maximize compatibility with current and future technologies (e.g., proper HTML markup).

 

WCAG 2.1 Levels of Conformance

There are three levels of conformance:

  • Level A (minimum)
  • Level AA (mid-range, and most commonly used as a legal/organizational standard)
  • Level AAA (maximum accessibility)

Content Type

Basic

Level A

Level AA

Level AAA

Microsoft Word
  • use built-in styles (headings, lists)
  • ensure keyboard accessibility
  • use built-in accessibility checker
  • provide alt text for all non-text content
  • ensure color contrast ration meets or exceeds 4:5:1 ratio 
  • use descriptive hyperlinks, clear and concise language
  • ensure compatibility with various assistive technologies
  • ensure color contrast meets or exceeds 3:1 for large text
  • use proper heading levels (H1-H6), built-in list features
  • create clear and helpful page titles
  • text and images must have contrast ratio of 7:1 
  • content supports alternate input methods (e.g., pointer activation)

  • Text spacing: line spacing > 1.5 times font size; paragraph spacing > 2 times font size; letter spacing > 0.12 times font size; word spacing > 0.16 times font size
Microsoft PowerPoint
  • use built-in designs
  • provide alt text for images
  • ensure compatibility with assistive technologies
  • use built-in accessibility checker 
  • avoid using tables for layout
  • provide alt-text for all non-text content
  • captions for media
  • 4:5:1 contrast ratio
  • avoid flashes or flickers
  • 3:1 contrast ratio for large text
  • keyboard accessible with visible focus indicators
  • headings and labels organize content and provide context
  • ensure text can be enlarged up to 200% without losing content/functionality
  • 7:1 contrast ratio for text
  • provide mechanisms for users to customize text and background colors
  • include audio description for video content 
  • limit use of text
PDF
  • provide alt-text for images
  • ensure keyboard navigation
  • 4:5:1 color contrast ratio
  • reading order should be logical and presentable
  • don't rely solely on color to convey information
  • 3:1 color contrast ratio for large text
  • avoid horizontal scrolling when content is zoomed
  • provide clear headings, consistent navigation, and mechanisms for bypassing repetitive content
  • 7:1 color contrast ratio 
  • provide captions for pre-recorded audio and video content
  • definitions of unusual words, idioms, abbreviations, pronunciation, or technical terms should be available
Canvas
  • use templates
  • avoid color-only cues
  • use Yuja--integrated in Canvas shells--to ensure basic accessibility standards are being met
  • use alt-text for images
  • ensure keyboard navigatability
  • 4:5:1 color contrast ratio
  • each page much have a unique and descriptive title
  • 3:1 color contrast for large text
  • ensure sufficient color contrast between text and background
  • provide captions for pre-recorded audio and video content
  • 7:1 color contrast ratio
  • avoid content that relies on timing
  • provide sign-language interpretation for pre-recorded audio content
Multimedia (video, audio, etc.)
  • provide captions or transcripts
  • captions or transcripts required
  • captions and synchronized audio description for videos
  • sign language interpretations and extended audio description
 
Math Content
  • write math clearly
  • avoid image-only equations
 
  • use HTML, MathML or LaTeX when possible
  • provide alt-text for images of equations
  • ensure keyboard navigability
 
  • ensure sufficient color contrast between text and background (including within mathematical expressions)
  • provide clear and concise explanations of mathematical concepts
  • avoid reliance on color alone to convey meaning in formulas/graphs
 
  • provide sign language interpretation for video explanations
  • Provide math in multiple formats (e.g., interactive simulations alongside equations)
  • ensure all content can be customized to individual needs
Complex Images, Charts, Graphs, etc.
  • add alt text
  • avoid decorative-only visuals without marking
  • alt text must describe key data points
  • describe complex images separately
  • a separate page with detailed explanations of images must be provided, linked from the image itself or from surrounding content
  • 3:1 for visual presentation of graphical objects
  • 7:1 for graphical objects
  • if image is purely decorative, it should have an empty alt attribute (alt="")
  • detailed text description might be combined with audio description and a link to a page with a simplified map/image
 
Tables
  • use tables only for data (not layout)
  • include table headers
  • use simple structure
 

  • Convery the structure of the table to assistive technologies, i.e., <th> elements for headers; “scope” or “id” attributes to associate data cells with corresponding headers

  • avoid merged cells
 
  • Order must be logical and understandable, whether using a mouse, keyboard, or screen reader
  • Headings and labels should clearly describe content they’re associated with

  • Use ARIA attributes to provide more semantic information about the table

  • allow table resizing
Web Content
  • use semantic HTML (headings, lists, links)
  • ensure keyboard navigability
  • use ARIA roles if needed
  • provide alt-text
  • provide video captions for media
  • avoid flickering or flashing
  • avoid abbreviations or idioms
  • support input assistance
  • provide ways for users to navigate via touch and voice activation
  • 7:1 color contrast ratio for text and background

 

Notes:

  • Basic = Good starting habits even if you don't meet WCAG formally.

  • Level A = Minimum legal standard in many institutions.

  • Level AA = Recommended standard for most universities and public websites.

  • Level AAA = Ideal but difficult to meet in full—aim to implement where feasible.