Accessibility & ADA Compliance at N.C. A&T

Creating accessible content is both a best practice and a legal obligation for higher education organizations under the Americans with Disabilities Act (ADA). One common accessibility challenge is the use of text within images, which often cannot be read by screen readers or other assistive technologies, excluding students with visual impairments from important information. To ensure ADA compliance and foster an inclusive learning environment, it is essential to avoid embedding text in images and instead use accessible alternatives. These best practices for accessible content creation help focus on strategies to avoid text in images and ensure that all digital materials are usable by everyone.


Deadline for Public Colleges and Universities to comply with WCAG 2.1 Level A and AA standards:

Failing to comply with ADA accessibility requirements in higher education can result in a range of serious negative outcomes. Financial penalties are significant: a first violation can incur a civil penalty of up to $75,000, with subsequent violations reaching $150,000 or more, and lawsuits or settlements can push costs even higher. Institutions also risk losing federal funding, as non-compliance can make them ineligible for government grants, financial aid, and research support, directly impacting operational budgets and student services.

WCAG 2.1 (AA) Requirements

  • Deadline: April 24, 2026.

  • Who is Examined: Public entities (state and local governments) with a population of 50,000 or more. (Entities <50,000 have until April 2027).

  • The Standard: You are being examined on WCAG 2.1 Level AA.

  • The Scope: This standard requires passing exactly 50 Success Criteria. This includes the original 38 criteria from WCAG 2.0, plus 12 new criteria introduced in version 2.1 that specifically target mobile accessibility and low-vision users.

The DOJ does not issue a percentage grade (e.g., "85% compliant"). The legal standard is full compliance, but the final rule includes specific nuances for auditing:

  1. Binary Technical Standard: A page technically "fails" if it misses any of the 50 criteria listed below.

  2. The "Minimal Impact" Safety Net: The DOJ rule states that a public entity will not be penalized for minor noncompliance if they can demonstrate that the error "does not prevent a person with a disability from enjoying the same access, rights, and benefits."

    • Pass Example: A color contrast ratio of 4.4:1 (instead of 4.5:1) on a footer link that is still legible.

    • Fail Example: A "Submit" button that cannot be reached via keyboard.

  3. The 30/70 Audit Rule: Automated tools (like WAVE or Axe) can only detect about 30% of these criteria (mostly programmatic syntax). The remaining 70% (such as logical focus order, meaningful error messages, and consistent navigation) requires manual human testing.

Criteria marked with 🆕 are the 12 additions in WCAG 2.1 that were not present in 2.0.

Principle 1: Perceivable

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

Level Success Criterion Description Source
A 1.1.1 Non-text Content Alt text for images, controls, and inputs. W3C Link
A 1.2.1 Audio/Video-only Transcripts for audio; descriptions for video-only. W3C Link
A 1.2.2 Captions (Prerecorded) Captions for all prerecorded video content. W3C Link
A 1.2.3 Audio Description Audio narration for visual details in video. W3C Link
A 1.3.1 Info and Relationships Semantic HTML (headings, lists, tables) matches visual structure. W3C Link
A 1.3.2 Meaningful Sequence The reading order in the code matches the visual order. W3C Link
A 1.3.3 Sensory Characteristics Instructions don't rely on shape, size, or sound alone. W3C Link
A 1.4.1 Use of Color Color is not the only means of conveying information. W3C Link
A 1.4.2 Audio Control Mechanism to pause/stop auto-playing audio >3 seconds. W3C Link
AA 1.2.4 Captions (Live) Captions for live video streams. W3C Link
AA 1.2.5 Audio Description Audio descriptions for prerecorded video (stricter than 1.2.3). W3C Link
AA 1.3.4 Orientation 🆕 Content does not restrict view to portrait or landscape only. W3C Link
AA 1.3.5 Identify Input Purpose 🆕 Forms support autocomplete attributes (e.g., autocomplete="email"). W3C Link
AA 1.4.3 Contrast (Minimum) Text has a contrast ratio of at least 4.5:1 (3:1 for large text). W3C Link
AA 1.4.4 Resize Text Text can be resized up to 200% without loss of content. W3C Link
AA 1.4.5 Images of Text Use actual text instead of pictures of text (unless essential like logos). W3C Link
AA 1.4.10 Reflow 🆕 Content reflows without horizontal scrolling at 400% zoom (320px width). W3C Link
AA 1.4.11 Non-text Contrast 🆕 UI components and graphics have 3:1 contrast against background. W3C Link
AA 1.4.12 Text Spacing 🆕 Increasing line/letter spacing does not break layout or cut off text. W3C Link
AA 1.4.13 Content on Hover/Focus 🆕 Tooltips are dismissable, hoverable, and persistent. W3C Link

Principle 2: Operable

User interface components and navigation must be operable.

Level Success Criterion Description Source
A 2.1.1 Keyboard All functionality is available via keyboard. W3C Link
A 2.1.2 No Keyboard Trap Focus does not get stuck in any element (like a modal). W3C Link
A 2.1.4 Character Key Shortcuts 🆕 Single-key shortcuts can be turned off or remapped. W3C Link
A 2.2.1 Timing Adjustable Users can extend or turn off time limits. W3C Link
A 2.2.2 Pause, Stop, Hide Moving/blinking content can be paused, stopped, or hidden. W3C Link
A 2.3.1 Three Flashes No content flashes more than 3 times per second (seizure risk). W3C Link
A 2.4.1 Bypass Blocks "Skip to Content" link exists to bypass navigation. W3C Link
A 2.4.2 Page Titled Web pages have unique, descriptive titles. W3C Link
A 2.4.3 Focus Order Navigation sequence is logical and intuitive. W3C Link
A 2.4.4 Link Purpose Link text makes sense alone or within its context. W3C Link
A 2.5.1 Pointer Gestures 🆕 Multipoint gestures (pinch-zoom) have simple alternatives. W3C Link
A 2.5.2 Pointer Cancellation 🆕 Actions trigger on the "up" event, not the "down" event. W3C Link
A 2.5.3 Label in Name 🆕 Visible label matches accessible name (for speech dictation). W3C Link
A 2.5.4 Motion Actuation 🆕 Functions triggered by motion (shaking) can be disabled. W3C Link
AA 2.4.5 Multiple Ways More than one way to find a page (Search, Sitemap, Menu). W3C Link
AA 2.4.6 Headings and Labels Headings and labels describe topic or purpose. W3C Link
AA 2.4.7 Focus Visible Keyboard focus indicator is clearly visible. W3C Link

Principle 3: Understandable

Information and the operation of user interface must be understandable.

Level Success Criterion Description Source
A 3.1.1 Language of Page The page language (<html lang="en">) is defined. W3C Link
A 3.2.1 On Focus Components do not trigger context changes on focus. W3C Link
A 3.2.2 On Input Changing a setting doesn't automatically change context. W3C Link
A 3.3.1 Error Identification Errors are described to the user in text. W3C Link
A 3.3.2 Labels or Instructions Inputs require labels or instructions. W3C Link
AA 3.1.2 Language of Parts Foreign language passages are marked in code. W3C Link
AA 3.2.3 Consistent Navigation Navigation menus appear in the same place across pages. W3C Link
AA 3.2.4 Consistent Identification Icons/buttons with same function look the same everywhere. W3C Link
AA 3.3.3 Error Suggestion If an error occurs, suggestions for correction are provided. W3C Link
AA 3.3.4 Error Prevention Legal/Financial transactions must be reversible or checked. W3C Link

Principle 4: Robust

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

Level Success Criterion Description Source
A 4.1.1 Parsing IDs are unique and code is free of syntax errors. W3C Link
A 4.1.2 Name, Role, Value Custom controls are built for screen readers (ARIA). W3C Link
AA 4.1.3 Status Messages 🆕 Dynamic updates (toasts/alerts) are announced by screen readers. W3C Link

Note on 4.1.1 Parsing: While modern browsers often correct parsing errors automatically (leading to this rule being deprecated in the newer WCAG 2.2), the DOJ law specifically cites WCAG 2.1. Therefore, you must technically still pass 4.1.1, though many auditors treat it lightly under the "Minimal Impact" rule.

The DOJ rule includes five specific exceptions where content does not need to be remediated by April 2026:

  1. Archived Web Content: Content meant only for reference/research, not updated, and clearly marked as archived.

  2. Pre-existing Electronic Documents: PDFs, Word docs, etc., posted before April 24, 2026, unless they are currently being used to apply for or participate in a service/program.

  3. Third-Party Content: Content posted by others (e.g., public comments) that isn't under the entity's control/contract.

  4. Individualized Password-Protected Docs: Documents securely shared with a specific person (e.g., a water bill or medical record).

  5. Pre-existing Social Media Posts: Posts made before the deadline.

1. The Official DOJ Mandate (Title II Rule)

2. The Technical Standard (WCAG 2.1)

  • The Full Standard: W3C WCAG 2.1 Recommendation

    • This is the technical manual for the 50 success criteria. The DOJ rule incorporates this specific document by reference.

  • Quick Reference Guide: How to Meet WCAG (Quick Reference)

    • A filterable W3C tool that allows you to select "WCAG 2.1" and "Level AA" to see exactly what is required.

3. Implementation Guidance

With new DOJ WCAG 2.1 Accessibility Requirements for Higher Education, it is imperative that we are proactive in ensuring our documents are ADA compliant. Please view this walkthrough to make your document more accessible to all users.