AccessivePath
Run a free audit

guide

WCAG 2.2 for education: requirements, priorities, and audit checklist

WCAG 2.2 compliance for education and edtech requires applying Web Content Accessibility Guidelines 2.2 to the specific failure points typical of the education industry — including inaccessible pdf readings and lecture slides, live lectures without real-time captions, proctoring software incompatible with assistive tech.

Sora Ito · IAAP WAS · Screen reader specialist3 min readPublished · Updated

Does WCAG 2.2 apply to education and edtech?

WCAG 2.2 (pronounced 'wuh-cag 2.2') is the World Wide Web Consortium's globally adopted standard for web accessibility, published October 2023, defining 87 testable success criteria organised under four principles: Perceivable, Operable, Understandable, Robust.

Education accessibility — the lay of the land

Universities, K-12 districts, and edtech vendors are subject to overlapping accessibility law: Section 504 (federal funding), ADA Title II (state institutions), DOJ April 2024 rule (state/local entities including public universities), and FERPA (which constrains certain accessibility solutions). The DOJ rule requires WCAG 2.1 AA conformance with compliance staggered through 2026–2027.

Where WCAG 2.2 bites hardest in education and edtech

• Inaccessible PDF readings and lecture slides

• Live lectures without real-time captions

• Proctoring software incompatible with assistive tech

• Math content as images rather than MathML

• Inaccessible assessment platforms

Remediation priorities

• LMS core (Canvas, Blackboard, Moodle)

• Lecture video (captions, transcripts)

• Assessment platforms and proctoring

• PDF documents and course readings

• Student services portals

How to comply with WCAG 2.2 on a Education site

1. Establish scope and baseline: Inventory every public-facing digital property. Run an automated baseline scan to detect the ~25–30% of WCAG criteria that machines can reliably check.

2. Manual + assistive-technology audit: Engage IAAP-credentialed auditors to test the remaining ~70% of criteria — keyboard, screen reader (NVDA, JAWS, VoiceOver), zoom and cognitive criteria.

3. Remediate at source: Fix issues in source code, not via overlay widgets. Train developers; integrate axe-core into CI; track open issues in JIRA or Linear.

4. Publish an accessibility statement: Disclose conformance level, known limitations, contact for accessibility feedback, and remediation timelines. Required under EAA and best-practice under ADA.

5. Monitor and re-test: Re-audit quarterly. Re-test before every major release. Keep an internal VPAT/ACR current and post it publicly.

Sources

FAQ

Frequently asked questions

Cited answers. Sourced. Updated as standards and case law change.

  • Does WCAG 2.2 apply to education websites?

    WCAG 2.2 (pronounced 'wuh-cag 2.2') is the World Wide Web Consortium's globally adopted standard for web accessibility, published October 2023, defining 87 testable success criteria organised under four principles: Perceivable, Operable, Understandable, Robust.

  • What are the most common WCAG 2.2 failures in education and edtech?

    Inaccessible PDF readings and lecture slides Live lectures without real-time captions Proctoring software incompatible with assistive tech

  • What conformance level should a education site target?

    WCAG 2.2 Level AA is the consensus target for legal compliance and the level referenced by virtually every national accessibility law.

  • Does the DOJ April 2024 Title II rule apply to public universities?

    Yes. Public universities and community colleges are state or local government entities under Title II of the ADA. The April 2024 final rule requires WCAG 2.1 AA conformance, with compliance dates of April 2026 (large entities, >50K residents) or April 2027 (smaller).

  • Do private universities have the same accessibility obligations?

    Private universities are typically covered by ADA Title III (public accommodations) and Section 504 if they receive federal financial assistance — which nearly all do. The functional standard is the same: WCAG 2.1/2.2 AA conformance.

  • Are lecture captions required?

    Live audio captioning is required under WCAG 1.2.4 and reinforced by Section 504 and Title II. Auto-generated captions alone often fail to meet accuracy thresholds; institutions are increasingly investing in human-corrected or hybrid captioning.

Stop guessing. Get the audit a Fortune 500 a11y team would have written.

Free audit on your live URL. No sign-up. IAAP-format report. Ready in hours.

Run a free auditBook a demo

founders@accessivepath.com · +977 9851094056