WCAG Technical Accessibility Standards

Texas A&M University-Corpus Christi must comply with federal and state regulations on nondiscrimination based on disability:

With the most recent updates to our regulations, the general requirement is for all information and communications technologies (ICT) to conform with Web Content Accessibility Guidelines (WCAG) 2.1 Level A and Level AA (WCAG 2.1 AA). These are our technical accessibility standards.

TAC 206 and TAC 213 are expected to align with the ADA Title II update soon. The tables below show the current minimum requirements, though conforming with WCAG 2.1 AA is recommended. The higher technical accessibility standards improves access for people of all abilities. It reduces their need to report their disabilities when requesting an ADA accommodation.

Hardware with a user interface is also covered in TAC 213. It is not in the tables below because the review does not include WCAG success criteria. TAC 213 references ICT Accessibility 508 Standards and 255 Guidelines, Chapter 4: Hardware.

WCAG 2.1 AA

Perceivable

Principle 1: Information and user interface components must be presentable to users in ways they can perceive.
Success Criteria Website or Web App Mobile App Desktop Software Authoring Tool Support Doc
1.1.1 Non-text Content (Level A) Title II Title II TAC 213 TAC 213 Title II
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Title II Title II TAC 213 TAC 213 Title II
1.2.2 Captions (Prerecorded) (Level A) Title II Title II TAC 213 TAC 213 Title II
1.3.1 Info and Relationships (Level A) Title II Title II TAC 213 TAC 213 Title II
1.3.2 Meaningful Sequence (Level A) Title II Title II TAC 213 TAC 213 Title II
1.3.3 Sensory Characteristics (Level A) Title II Title II TAC 213 TAC 213 Title II
1.4.1 Use of Color (Level A) Title II Title II TAC 213 TAC 213 Title II
1.4.2 Audio Control (Level A) Title II Title II TAC 213 TAC 213 Title II
1.2.4 Captions (Live) (Level AA) Title II Title II TAC 213 TAC 213 Title II
1.2.5 Audio Description (Prerecorded) (Level AA) Title II Title II TAC 213 TAC 213 Title II
1.3.4 Orientation (Level AA) Title II Title II Can apply Can apply Title II
1.3.5 Identify Input Purpose (Level AA) Title II Title II Can apply Can apply Title II
1.4.3 Contrast (Minimum) (Level AA) Title II Title II TAC 213 TAC 213 Title II
1.4.4 Resize text (Level AA) Title II Title II TAC 213 TAC 213 Title II
1.4.5 Images of Text (Level AA) Title II Title II TAC 213 TAC 213 Title II
1.4.10 Reflow (Level AA) Title II Title II Can apply Can apply Title II
1.4.11 Non-text Contrast (Level AA) Title II Title II Can apply Can apply Title II
1.4.12 Text Spacing (Level AA) Title II Title II Can apply Can apply Title II
1.4.13 Content on Hover or Focus (Level AA) Title II Title II Can apply Can apply Title II

Operable

Principle 2: User interface components and navigation must be operable.
Success Criteria Website or Web App Mobile App Desktop Software Authoring Tool Support Doc
2.1.1 Keyboard (Level A) Title II Title II TAC 213 TAC 213 Title II
2.1.2 No Keyboard Trap (Level A) Title II Title II TAC 213 TAC 213 Title II
2.1.4 Character Key Shortcuts (Level A) Title II Title II Can apply Can apply Title II
2.2.1 Timing Adjustable (Level A) Title II Title II TAC 213 TAC 213 Title II
2.2.2 Pause, Stop, Hide (Level A) Title II Title II TAC 213 TAC 213 Title II
2.3.1 Three Flashes or Below Threshold (Level A) Title II Title II TAC 213 TAC 213 Title II
2.4.1 Bypass Blocks (Level A) Title II Does not apply Does not apply TAC 213 Title II unless it is a non-web doc
2.4.2 Page Titled (Level A) Title II Title II TAC 213 TAC 213 Title II
2.4.3 Focus Order (Level A) Title II Title II TAC 213 TAC 213 Title II
2.4.4 Link Purpose (In Context) (Level A) Title II Title II TAC 213 TAC 213 Title II
2.5.1 Pointer Gestures (Level A) Title II Title II Can apply Can apply Title II
2.5.2 Pointer Cancellation (Level A) Title II Title II Can apply Can apply Title II
2.5.3 Label in Name (Level A) Title II Title II Can apply Can apply Title II
2.5.4 Motion Actuation (Level A) Title II Title II Can apply Can apply Title II
2.4.5 Multiple Ways (Level AA) Title II Does not apply Does not apply TAC 213 Title II unless it is a non-web doc
2.4.6 Headings and Labels (Level AA) Title II Title II TAC 213 TAC 213 Title II
2.4.7 Focus Visible (Level AA) Title II Title II TAC 213 TAC 213 Title II

Understandable

Principle 3: Information and the operation of user interface must be understandable.
Success Criteria Website or Web App Mobile App Desktop Software Authoring Tool Support Doc
3.1.1 Language of Page (Level A) Title II Title II TAC 213 TAC 213 Title II
3.2.1 On Focus (Level A) Title II Title II TAC 213 TAC 213 Title II
3.2.2 On Input (Level A) Title II Title II TAC 213 TAC 213 Title II
3.3.1 Error Identification (Level A) Title II Title II TAC 213 TAC 213 Title II
3.3.2 Labels or Instructions (Level A) Title II Title II TAC 213 TAC 213 Title II
3.1.2 Language of Parts (Level AA) Title II Title II TAC 213 TAC 213 Title II
3.2.3 Consistent Navigation (Level AA) Title II Does not apply Does not apply TAC 213 Title II unless it is a non-web doc
3.2.4 Consistent Identification (Level AA) Title II Does not apply Does not apply TAC 213 Title II unless it is a non-web doc
3.3.3 Error Suggestion (Level AA) Title II Title II TAC 213 TAC 213 Title II
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Title II Title II TAC 213 TAC 213 Title II

Robust

Principle 4: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Success Criteria Website or Web App Mobile App Desktop Software Authoring Tool Support Doc
4.1.1 Parsing* (Level A) Supports Supports Supports Supports Supports
4.1.2 Name, Role, Value (Level A) Title II Title II TAC 213 TAC 213 Title II
4.1.3 Status Messages (Level AA) Title II Title II Can apply Can apply Title II

* For WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata.