[XYZ] Evaluation

This document contains the findings of an accessibility evaluation performed by the Center for User Experience. This is not a comprehensive list of barriers. [XYZ product] is a [product description] to [problem it solves].

Date evaluated: [Date]
Report date: [Date]

Overview

The Center for UX evaluates digital content using the Web Content Accessibility Guidelines (WCAG) version 2.1, Levels A and AA as our technical standard, using both manual and automated testing methods.

Our manual testing methods include:

  • checking for keyboard and screen reader support
  • reflow at high levels of magnification
  • accessible video and audio content
  • sufficient color contrast 

We may also identify usability barriers.

This evaluation is not comprehensive and should not be used as a replacement for internal quality assurance of a product. We find patterns of accessibility barriers and show examples of the types of barriers we find.

For more about WCAG conformance refer to: href="https://www.w3.org/WAI/WCAG21/Understanding/conformance#levels">https://www.w3.org/WAI/WCAG21/Understanding/conformance#levels

Get Help

  • To discuss accessibility barriers, contact [xyz@wisc.edu]
  • For general assistance, contact the DoIT Help Desk
  • See also: [related KB docs]

Common barriers and related WCAG criteria (delete when publishing)

  • Poor color contrast:
    • Provide sufficient contrast between content and its background, WCAG 1.4.3
  • Using color or language like "see below" to describe location:
    • Describe controls by name, not just by appearance or location, WCAG 1.3.3
  • Missing alt text:
    • Provide text alternatives for any non-text content, WCAG 1.1.1
  • Headings missing or improperly nested OR missing labels
    • Use headings and labels, WCAG 2.4.6
    • Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text, WCAG 1.3.1
  • Other screen reader barriers:
    • Make web pages appear and operate in predictable ways, WCAG 3.2
    • People using assistive technology should understand all components (Name, value, role), WCAG 4.1.2
  • Non-descriptive links:
  • Small text:
    • Resize text up to 200% without assistive technology: WCAG 1.4.4
  • Poor reflow/magnification:
    • Resize without assistive technology up to 200 percent without loss of content or functionality, WCAG 1.4.4
    • Reflow: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions, WCAG 1.4.10
  • Keyboard-only barriers
    • Everything can be done with a keyboard, WCAG 2.1.1
  • Pre-recorded video content lacking captions or audio descriptions:
    • Provide captions for all prerecorded audio content in synchronized media, WCAG 1.2.2
    • Provide an audio description for video content in synchronized media, WCAG 1.2.5
  • Audio-only content (i.e., podcasts) lacking transcript:
    • Provide text alternatives for non-text content, WCAG 1.1.1

Test conditions

  • Device: [MacBook Pro 16]
  • Operating system[Tahoe 26.1]
  • Web browser: Chrome
  • Screen reader[VoiceOver]

[Elements] [Pages] tested

  1. [Element A]

  2. [Element B]
  3. [Element C]

Barriers found in testing

[Element A]

blank image space holder

Barrier: 

Relevant WCAG criteria:
Expected behavior:

[Element B]

blank image space holder

Barrier: 

Relevant WCAG criteria:
Expected behavior:

[Element C]

blank image space holder

Barrier: 

Relevant WCAG criteria:
Expected behavior:


Keywords:
evaluation, automated testing, manual testing, [add more keywords] 
Doc ID:
162335
Owned by:
Digital Accessibility Team in IT Accessibility and Usability
Created:
2026-06-30
Updated:
2026-07-03
Sites:
IT Accessibility and Usability