What is WCAG and which version applies to my website?

WCAG (Web Content Accessibility Guidelines) is the international standard for web accessibility published by the W3C. WCAG 2.1 Level AA is the current legal benchmark in most jurisdictions, including ADA Title III litigation in the US and EAA compliance in the EU. WCAG 2.2, released in October 2023, is the recommended target for new projects and is increasingly cited in regulatory guidance.

What is the EAA compliance deadline?

The European Accessibility Act (EAA) main application date was June 28, 2025. Organisations covered by the EAA must have compliant digital products and services by this date or face regulatory penalties. Sector-specific transition periods extend to 2030–2035 for certain legacy services.

What is the difference between ADA Title II and ADA Title III?

ADA Title II applies to state and local government entities, requiring equal access to public services including websites and apps. ADA Title III applies to private businesses and commercial websites — it is the most common basis for accessibility lawsuits in the United States. Both laws are enforced without a specific technical deadline; WCAG 2.1 AA is the widely accepted compliance standard for both.

Do accessibility overlays make a website ADA or WCAG compliant?

No. Accessibility overlays are third-party scripts that claim to fix accessibility automatically, but they do not replace proper accessible design, development, and testing. Courts and regulators have not accepted overlays as a substitute for genuine WCAG conformance, and overlays frequently introduce new barriers for screen reader users.

What is a VPAT and when is it required?

A VPAT (Voluntary Product Accessibility Template) is a standardised document that describes how a product or service conforms to accessibility standards such as WCAG, Section 508, or EN 301 549. VPATs are commonly required during enterprise and government procurement. An outdated or inaccurate VPAT can expose vendors to legal and reputational risk.

What colour contrast ratio is required for WCAG AA compliance?

WCAG 2.1 Level AA requires a minimum contrast ratio of 4.5:1 between body text and its background. For large text (18pt regular or 14pt bold and above), the minimum ratio is 3:1. Colour contrast is one of the most frequently failed WCAG criteria and is measurable using free tools such as the WebAIM Contrast Checker.

Digital accessibility glossary

Accessibility terms every digital team should understand

A practical reference covering accessibility standards, compliance laws, technical specifications, and governance concepts used across websites, mobile apps, documents, and digital products — including WCAG, ADA, EAA, Section 508, AODA, ARIA, PDF accessibility, and operational accessibility programmes.

Accessible PDF: A PDF structured so people using assistive technology can understand and navigate it. It typically meets PDF/UA (ISO 14289-1) requirements: tagged structure, logical reading order, meaningful headings, document metadata, and alt text for all meaningful images.
ADA Title II: U.S. federal law requiring state and local governments to provide equal access to public services, including websites and mobile apps. There is no fixed technical deadline; the effective-now standard applies, and WCAG 2.1 AA is the widely accepted compliance benchmark.
ADA Title III: U.S. federal law prohibiting disability discrimination in places of public accommodation, including commercial websites, mobile apps, and digital services. ADA Title III is the most common basis for accessibility litigation in the United States. Organisations that fail to meet WCAG 2.1 AA face demand letters, class-action suits, and court-ordered remediation.
Alt Text: A text alternative for an image that communicates its purpose or meaningful information to users who cannot see it. Required by WCAG Success Criterion 1.1.1. Decorative images should use empty alt attributes so screen readers skip them entirely.
AODA: The Accessibility for Ontarians with Disabilities Act — a Canadian provincial law requiring many public and private sector organisations in Ontario to meet WCAG 2.0 Level AA. Enforcement is active; non-compliance can result in fines and legal liability.
ARIA: Accessible Rich Internet Applications — a technical specification that adds semantic meaning to dynamic web elements and custom widgets when native HTML alone is insufficient. ARIA attributes (roles, properties, states) allow screen readers to interpret interactive components such as modals, carousels, and custom dropdowns correctly.
Color Contrast Ratio: The measurable difference in luminance between foreground text and its background. WCAG 2.1 AA requires a minimum ratio of 4.5:1 for body text and 3:1 for large text (18pt regular or bold 14pt and above). Insufficient contrast is one of the most frequently failed WCAG criteria.
Conformance Level: WCAG's three-tier rating system: Level A (minimum), Level AA (industry standard and legal benchmark), and Level AAA (most rigorous, often impractical to achieve site-wide). Level AA is the target cited in ADA Title III litigation, EAA compliance, and most enterprise procurement standards.
EAA: The European Accessibility Act — an EU directive covering selected products and services, including many digital services offered to consumers. It applies to organisations with annual turnover exceeding €2 million. The main application date was June 28, 2025, with sector-specific transition periods extending to 2030–2035. See also: EAA Compliance Deadline.
EAA Compliance Deadline: June 28, 2025 — the date by which organisations covered by the European Accessibility Act must have compliant digital products and services. Enforcement transition periods extend to 2030–2035 for specific legacy cases. Non-compliant organisations face regulatory penalties and potential legal action across EU member states.
Focus Management: The practice of ensuring keyboard focus moves predictably, remains visible at all times, and does not become trapped or lost during interaction. Poor focus management is one of the most frequently cited issues in accessibility audits and ADA litigation.
Keyboard Navigation: The ability to use all interactive functionality without a mouse. Requires logical tab order, visible focus states, and keyboard-accessible controls. Defined in WCAG criterion 2.1.1 and essential for users with motor disabilities or those relying on assistive technology such as screen readers.
Operational Accessibility: The governance structures, processes, staffing, training, QA testing, vendor management, and maintenance practices that keep accessibility sustainable over time. Organisations with mature operational accessibility programmes are better positioned in audits, litigation defence, and large-scale remediation efforts.
Overlay (Accessibility): A third-party script or widget that claims to improve accessibility automatically. Overlays do not replace proper accessible design, development, testing, and remediation. They are not accepted as a substitute for genuine WCAG conformance in most litigation or regulatory contexts, and frequently introduce new barriers for screen reader users.
PDF/UA: An ISO standard (ISO 14289-1) for accessible PDFs. Requires structured tags, meaningful reading order, document metadata, proper headings, and alternatives for all non-text content. Failure to meet PDF/UA is a common basis for ADA Title III claims against organisations that distribute inaccessible documents. See also: Accessible PDF, Tagged PDF.
Remediation: The process of identifying and fixing accessibility barriers in code, content, design, documents, or user flows. Strategic remediation typically prioritises high-impact issues first — such as keyboard navigation failures, missing alt text, and colour contrast deficiencies.
Screen Reader: Assistive technology that reads digital content aloud and helps users with visual impairments navigate pages, apps, and documents through keyboard or gesture commands. Widely used screen readers include NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android. Screen readers rely on correct HTML structure and ARIA markup to provide meaningful output.
Section 508: U.S. federal accessibility requirements for information and communications technology (ICT) used by federal agencies and contractors. Section 508 formally references WCAG 2.0 AA as its technical standard and applies to government websites, software, documents, and any ICT procured with federal funds.
Tagged PDF: A PDF with embedded structural markup that communicates reading order, headings, lists, tables, links, and image alternatives to assistive technology. Untagged or poorly tagged PDFs are inaccessible to screen reader users and fail PDF/UA requirements.
VPAT: A Voluntary Product Accessibility Template describing how a product or service conforms to accessibility standards such as WCAG, Section 508, or EN 301 549. VPATs are required by many enterprise and government procurement processes. Outdated or inaccurate VPATs expose vendors to legal and reputational risk.
WCAG: Web Content Accessibility Guidelines — the international standard for web accessibility, published by the W3C. Organised around four principles: Perceivable, Operable, Understandable, and Robust. WCAG is the primary technical benchmark cited in ADA litigation, EAA compliance, Section 508, and most global accessibility laws. See also: WCAG 2.1 AA, WCAG 2.2.
WCAG 2.1 AA: The most widely adopted accessibility conformance target for websites, apps, and digital documents. Legally recognised in ADA Title III litigation and European accessibility law, and the benchmark referenced in most enterprise procurement and government contracts. Organisations meeting WCAG 2.1 AA satisfy the core requirements of EAA, Section 508, and AODA.
WCAG 2.2: The latest version of the Web Content Accessibility Guidelines, released in October 2023. Adds criteria for focus appearance, dragging movements, minimum target size, and redundant entry. WCAG 2.2 is increasingly cited in regulatory guidance and litigation, with broad industry adoption expected through 2025–2026. It is the recommended planning target for new and updated digital products.

Need to turn accessibility terms into action?

AIOPSGROUP helps teams assess, remediate, and maintain accessible digital experiences across websites, mobile apps, eCommerce platforms, and documents — from WCAG 2.2 audits to full EAA and ADA compliance programmes.

Request an accessibility audit