Mapping the Revised 508/255 ICT Accessibility Standards to the WCAG 2.2
Listen to this article
Your browser does not support text-to-speech.
I have this thing about connecting the dots between the current Web Content Accessibility Guidelines (WCAG) and other documents that relate to accessibility. That way, the relationships are easier to see, reference, and teach. Seeing as how there’s a lot of buz around making government sites accessible and agencies scrambling to make the new deadline, I wanted to highlight the similarities between the WCAG and the Revised 508/255 ICT Standards.
Table of contents
- How the ICT rule references WCAG
- ICT rules that align with the WCAG success criteria
- WCAG 2.0 A & AA criteria required by the ICT rule, mapped to WCAG 2.2
- WCAG 2.2 criteria not required by the ICT
- ICT rules with no WCAG equivalent
- Legacy cross-reference: original 2000 Section 508 Standards (§1194.22) to WCAG 1.0
How the ICT rule references WCAG
Being behind the ball a bit, the Information and communication technology (ICT) rule doesn’t point to the current version of the WCAG. It incorporates the WCAG 2.0 by reference 702.10.1 and requires Level A and Level AA conformance. Because the WCAG 2.2 is backward compatible, every 2.0 success criterion (SC) carries the same number, except for “SC 4.1.1 Parsing” which was deprecated. The WCAG 2.0 Levels along with the ICT rules map one-to-one onto a subset of today’s WCAG 2.2 Levels. The ICT rule’s text does not require the newer criteria added to the WCAG 2.2 however, it would be in the best interest for agencies to apply 2.2. That way, when the old requirements catch up to modern times, those who have been aiming for 2.2 will be ahead of the game.
ICT rules that align with the WCAG success criteria
| ICT rule | What it covers | WCAG Level | Exceptions |
|---|---|---|---|
| E205.4 (508, Electronic Content) | Public-facing and certain non-public agency electronic content | A and AA | Non-Web documents excused from 2.4.1, 2.4.5, 3.2.3, 3.2.4 |
| E207.2 (508, Software) | UI components and content of platforms/applications | A and AA | Non-Web software excused from the same four criteria, and from Conformance Requirement 3 (Complete Processes) |
| C203.1 (255, Electronic Content) | Content integral to telecom or Customer Premises Equipment use | A and AA | Non-Web documents excused from 2.4.1, 2.4.5, 3.2.3, 3.2.4 |
| C205.2 (255, Software) | UI components and content of telecom platforms/applications | A and AA | Same exceptions as E207.2 |
| 504.2 / 504.3 / 504.4 (Authoring Tools) | Content produced or edited by authoring tools, prompts, templates | A and AA | Applies “to the extent supported by the destination format”; not required for direct editing of plain text source code |
| 602.3 (Electronic Support Documentation) | Web-based/electronic help and self-service documentation | A and AA | None stated |
| 501.1 Exception (Software, general) | Web applications lacking platform accessibility service access | A and AA (in lieu of 502/503) | Applies only when the app has no access to platform accessibility services |
| 408.3 Exception (Hardware, Flashing) | Flashing on ICT display screens | General flash / red flash thresholds | Defined by reference to WCAG 2.0’s flash thresholds (see 2.3.1) |
Where a document or non-Web software substitution applies, the rule also swaps the term “Web page” or “page” for “document” or “software” in the SC text E205.4.1, E207.2.1, C203.1.1, C205.2.1.
WCAG 2.0 Level A & AA criteria required by the ICT rule, mapped to WCAG 2.2
The following 38 success criteria are the ones the ICT rule requires. Numbering and titles are unchanged, so each maps directly to the current WCAG 2.2 SC.
Level A
| SC | WCAG 2.2 Title | Status |
|---|---|---|
| 1.1.1 | Non-text Content | Unchanged |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | Unchanged |
| 1.2.2 | Captions (Prerecorded) | Unchanged |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | Unchanged |
| 1.3.1 | Info and Relationships | Unchanged |
| 1.3.2 | Meaningful Sequence | Unchanged |
| 1.3.3 | Sensory Characteristics | Unchanged |
| 1.4.1 | Use of Color | Unchanged |
| 1.4.2 | Audio Control | Unchanged |
| 2.1.1 | Keyboard | Unchanged |
| 2.1.2 | No Keyboard Trap | Unchanged |
| 2.2.1 | Timing Adjustable | Unchanged |
| 2.2.2 | Pause, Stop, Hide | Unchanged |
| 2.3.1 | Three Flashes or Below Threshold | Unchanged |
| 2.4.1 | Bypass Blocks | Unchanged (excepted for non-Web docs/software) |
| 2.4.2 | Page Titled | Unchanged |
| 2.4.3 | Focus Order | Unchanged |
| 2.4.4 | Link Purpose (In Context) | Unchanged |
| 3.1.1 | Language of Page | Unchanged |
| 3.2.1 | On Focus | Unchanged |
| 3.2.2 | On Input | Unchanged |
| 3.3.1 | Error Identification | Unchanged |
| 3.3.2 | Labels or Instructions | Unchanged |
| 4.1.1 | Parsing | Obsolete/removed in WCAG 2.2 — no longer testable; treat as satisfied |
| 4.1.2 | Name, Role, Value | Unchanged |
Level AA
| SC | WCAG 2.2 Title | Status |
|---|---|---|
| 1.2.4 | Captions (Live) | Unchanged |
| 1.2.5 | Audio Description (Prerecorded) | Unchanged |
| 1.4.3 | Contrast (Minimum) | Unchanged |
| 1.4.4 | Resize Text | Unchanged |
| 1.4.5 | Images of Text | Unchanged |
| 2.4.5 | Multiple Ways | Unchanged (excepted for non-Web docs/software) |
| 2.4.6 | Headings and Labels | Unchanged |
| 2.4.7 | Focus Visible | Unchanged |
| 3.1.2 | Language of Parts | Unchanged |
| 3.2.3 | Consistent Navigation | Unchanged (excepted for non-Web docs/software) |
| 3.2.4 | Consistent Identification | Unchanged (excepted for non-Web docs/software) |
| 3.3.3 | Error Suggestion | Unchanged |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | Unchanged |
WCAG 2.2 criteria not required by the ICT
As I mentioned above, since the ICT rule references the WCAG 2.0, the newer criteria (introduced in 2.1 or 2.2) are not required by 508/255. Though, that doesn’t mean they sould be ignored.
ICT rules with no WCAG equivalent
Because the WCAG governs electronic content, a large part of the ICT rules are out of the WCAG’s scope since they govern support services, hardware, platform-level software services.
- Chapter 3, Functional Performance Criteria (301–302) vision/hearing/speech/manipulation-based outcome criteria used as a fallback where Chapters 4–5 don’t address a function.
- Chapter 4, Hardware (401–415) physical device requirements, closed-functionality speech output, volume, reach ranges, key layouts, TTY connectivity, caption/audio-description decoder circuitry, etc.
- 502 Interoperability with Assistive Technology / 503.2–503.3 platform accessibility-services requirements (object role/state exposure, focus tracking, etc.) related to 4.1.2 Name, Role, Value, but scoped to platform software rather than Web content.
- Chapter 6, Support Documentation and Services (601–603) non-electronic alternate formats and help-desk and communication-accommodation requirements.
Legacy cross-reference: original 2000 Section 508 Standards (§1194.22) to WCAG 1.0
Going back this far is over kill, but hey, here we are. So for context, the Access Board’s preamble maps the original 2000-era §1194.22 paragraphs (a)-(k) to WCAG 1.0 Priority 1 guidelines or checkpoint. This mapping is is only relevant when evaluating legacy ICT under the safe-harbor provision (E202.2).
| §1194.22 Paragraph | WCAG 1.0 Checkpoint |
|---|---|
| (a) | 1.1 |
| (b) | 1.4 |
| (c) | 2.1 |
| (d) | 6.1 |
| (e) | 1.2 |
| (f) | 9.1 |
| (g) | 5.1 |
| (h) | 5.2 |
| (i) | 12.1 |
| (j) | 7.1 |
| (k) | 11.4 |
Not shown here, paragraphs (l)–(p), of the original §1194.22 have no WCAG 1.0 equivalent and were 508-specific additions. Full checkpoint text is available in the WCAG 1.0 specification.
References
U.S Access Board, Revised 508 Standards and 255 Guidelines
https://www.access-board.gov/ict/
Understanding WCAG 2.2
https://www.w3.org/WAI/WCAG21/quickref/