CPACC - Module 12: applying standards and regulations to ICT
A study summary of how accessibility law applies to ICT for the CPACC exam — US Section 508 and the ADA, EU directives, and conformance reports.
- #accessibility
- #cpacc
- #study-notes
This is Module 12 of the CPACC (Certified Professional in Accessibility Core Competencies) Body of Knowledge — the third module of Domain 3, Standards, Laws, and Management Strategies. Module 11 surveyed the whole landscape of laws; this module zooms in on how they apply to information and communication technology (ICT) — websites, apps, documents — and, critically, who enforces each one.
Why ICT is a special case #
Most countries have long protected the civil rights of people with disabilities for homes, parks, businesses, and schools — the physical world. But ICT accessibility has lagged: not every country regulates websites, apps, and digital documents. This module covers the two jurisdictions the exam cares about: the United States and the European Union.
US laws and standards #
| Instrument | Applies to | Standard / enforcement | |---|---|---| | Section 508 | Federal, state & local government websites only | Uses WCAG 2.0 as its conformance standard; it is both a law and a technical standard | | ADA — Title II | State & local government spaces and websites | Enforced by the DOJ Civil Rights Division (Dept. of Education OCR for schools) | | ADA — Title III | Private places open to the public — businesses, schools, offices, medical buildings; e-commerce, org websites, mobile apps | Same enforcement; no built-in web standard, but orgs can be sued for inaccessibility |
EU laws and standards #
| Instrument | In force | Applies to | Standard | |---|---|---|---| | Web Accessibility Directive | Sept 2018 | Public sector ICT — websites, applications, mobile apps, and downloadable documents | EN 301 549, which aligns with WCAG 2.1 AA | | European Accessibility Act (EAA) | Full force 2025 | Both public and private sectors | Functional requirements for products/services most important to people with disabilities |
Accessibility statements #
An accessibility statement can be required by law or voluntary.
| Context | Who it affects | What it requires | |---|---|---| | Web Accessibility Directive | Public sector | A “detailed, comprehensive and clear” accessibility statement on the site/app, regularly updated | | European Accessibility Act | Private sector | Information assessing how the product/service meets accessibility requirements | | Voluntary | Anyone | Not required — but signals a commitment to accessibility and informs users |
Conformance reports and the VPAT #
A conformance report documents how a website or app measures up against a standard. Reports are used to demonstrate legal compliance, in ICT procurement, and for internal reporting and product development.
Common standards a report can measure against:
- WCAG — the international baseline
- EN 301 549 — specific to the European Union
- Section 508 — specific to public entities in the United States
Quick self-check #
- Which US instrument applies only to government websites, and which standard does it use?
- ADA Title II vs. Title III — who does each cover?
- Does the ADA include a legal standard for private-business websites? Can those businesses still be sued?
- What standard does the EU Web Accessibility Directive reference, and which WCAG version does it align with?
- Who does the European Accessibility Act apply to?
- What is a VPAT, and who uses it?
Knowledge check #
Answer each question, then check — the feedback explains every choice.
Study tip: build a two-column table in your head — US (Section 508 → gov sites, WCAG 2.0; ADA Title II → gov, Title III → private/e-commerce, no named standard but suable) and EU (Web Accessibility Directive → public sector, EN 301 549 / WCAG 2.1 AA; European Accessibility Act → public + private + non-profit, 2025). Then memorize the three artifacts: accessibility statement (a promise), conformance report (a measurement), and VPAT (the template for that measurement).