EU Accessibility Act vs ADA and Section 508 Scope, standards, and evidence
The EAA regulates selected products and consumer services in the EU. The ADA regulates disability access in US state and local government programs and public accommodations, while governs US federal agency ICT.
The regimes can cover the same website, app, terminal, or service, but their duty holders, technical baselines, exceptions, evidence, and enforcement routes are different.
Use three separate scope tests. Apply the European Accessibility Act to the products and consumer services listed in Directive (EU) 2019/882. Apply ADA Title II to US state and local government services, programs, and activities, including covered web content and mobile apps; assess ADA Title III separately for businesses that are public accommodations. Apply when a US federal agency develops, procures, maintains, or uses ICT. Shared accessibility testing can reduce duplicate work, but one regime's audit does not establish compliance with another.
Side-by-side comparison
EU Accessibility Act vs ADA and Section 508: practical differences
This matrix compares the regimes at the level needed to choose the correct scope analysis, standard, evidence file, exception process, and authority route.
This column supports cited EAA scope, operator duties, accessibility requirements, standards evidence, procurement effects, implementation dates, and enforcement records.
Second framework
ADA and Section 508
ADA Title II covers state and local government programs, services, and activities; ADA Title III covers public accommodations; covers federal agency ICT. Each has its own scope and evidence rules.
EU Accessibility Act vs ADA and Section 508: practical differences
The EAA applies to selected products and services, including consumer computer hardware and operating systems, self-service terminals, consumer terminal equipment, e-readers, electronic communications services, audiovisual-media access services, passenger transport service elements, consumer banking, e-books, e-commerce, and answering emergency communications to 112.
Commission overview listing covered product and service categories.
products and services covered
ADA Title II applies to state and local government services, programs, and activities, including covered web content and mobile apps. ADA Title III applies to public accommodations and their goods, services, privileges, and activities. applies when a federal agency develops, procures, maintains, or uses ICT.
Supports the Section 508 federal agency ICT boundary.
Create separate EAA, ADA Title II or III, and scope entries. A website, app, terminal, or digital service may fall under more than one regime because of the market, operator, government level, or customer.
EAA duties are role-specific. Product obligations can apply to manufacturers, authorised representatives, importers, and distributors. Service obligations apply to service providers offering covered services to consumers in the Union.
Binding source for EAA operator definitions and duties for products and services.
Obligations of economic operators
ADA Title II duties sit with the state or local government, including content or apps made available through contracts or licences. ADA Title III duties sit with the public accommodation. duties sit with the federal agency, although vendors supply evidence and accessible ICT.
Supports the federal department and agency duty-holder boundary.
Name accountable owners for EAA product conformity or service operation, ADA program or public-accommodation access, and federal acquisition and acceptance.
The EAA is concrete about product and service categories: it is not a universal accessibility statute for every digital asset. Confirm whether the item is a listed product, listed service, or emergency-communications activity before applying EAA requirements.
Supports the covered product and service category list used for practical scoping.
computers and operating systems
For ADA Title II, the trigger is a state or local government service, program, or activity. For ADA Title III, it is a covered public accommodation's goods, services, privileges, or activities. For , it is federal agency development, procurement, maintenance, or use of ICT.
Supports the federal ICT lifecycle trigger for Section 508.
Tag the artifact to the covered actor and activity before reusing an audit. A federal procurement report, state mobile app test, retail website audit, and EAA conformity file answer different questions.
Manufacturers must design and manufacture covered products in accordance with applicable EAA accessibility requirements, draw up technical documentation, carry out conformity assessment, draw up an EU declaration of conformity, affix CE marking where required, keep records, handle non-conformity, and cooperate with authorities. Service providers must design and provide covered services in accordance with the requirements and provide accessibility information.
Binding source for manufacturer, service-provider, non-conformity, authority-cooperation, and record duties.
When placing their products on the market
ADA Title II requires covered web content and mobile apps to meet WCAG 2.1 Level A and AA after the applicable compliance date, subject to the rule's provisions, and preserves duties such as effective communication and reasonable modifications. requires accessible federal ICT under the Revised 508 Standards. ADA Title III requires equal access and effective communication but DOJ has not set one detailed technical web standard for public accommodations.
Supports the Revised 508 technical baseline for covered federal ICT.
Do not collapse the work into one WCAG ticket. Assign EAA conformity, ADA service access, ICT acceptance, user requests, complaints, corrective action, and standard-specific testing.
EAA evidence should map Annex I requirements to technical documentation, service accessibility information, conformity assessment results, CE marking where applicable, EU declarations of conformity for covered products, and Article 14 records when an exception is used.
Supports use of EN 301 549 as an ICT accessibility standard for software, hardware, and combined ICT products and services.
ICT products and services
ADA Title II evidence should identify the covered web content or mobile app, WCAG 2.1 Level A and AA test scope, exceptions, fixes, and continuing access arrangements. evidence should map the ICT to the Revised 508 provisions, including applicable non-web, hardware, software, support, and functional-performance requirements. Title III evidence should show how the public accommodation provides access and effective communication without overstating WCAG as a binding DOJ technical baseline.
Supports WCAG 2.0 incorporation and the wider Section 508 ICT evidence boundary.
Keep a crosswalk with the EAA requirement, EN 301 549 or other EU route, ADA title and rule provision, provision, test result, exception, remediation status, and claim boundary.
The EAA required Member States to adopt and publish transposition measures by 28 June 2022 and apply them from 28 June 2025. It also includes transitional measures ending 28 June 2030 for certain service-provider products and limits for pre-existing service contracts and self-service terminals.
Commission source for public implementation context around the 28 June 2025 application date.
European Accessibility Act
The 2026 DOJ interim final rule extends ADA Title II web and mobile app compliance to 26 April 2027 for entities with populations of at least 50,000 and to 26 April 2028 for smaller entities and special district governments. has no EAA-style market application date; apply the current federal standards to the agency's covered ICT lifecycle activity.
Official DOJ guidance confirms the April 2026 interim final rule extended compliance to 26 April 2027 for entities with populations of 50,000 or more and 26 April 2028 for smaller entities and special district governments.
Maintain separate EAA, ADA Title II, and federal acquisition milestones. Recheck the DOJ rule and the agency's process when scheduling a release or procurement.
EAA assurance is handled through national measures, market surveillance for products, service-compliance procedures, complaint or report follow-up, corrective action, withdrawal or restriction for non-compliant products, and Member State penalties that must be effective, proportionate, and dissuasive.
Binding source for EAA product market surveillance, service compliance procedures, corrective action, withdrawal, and penalty principles.
effective, proportionate and dissuasive
ADA complaints and enforcement follow the applicable ADA title and DOJ procedures; contracts do not transfer a Title II public entity's responsibility. permits administrative complaints to the federal agency and provides statutory remedies for covered procurement, while agency acquisition and acceptance controls address defects operationally.
Official entry point for the separate ADA Title II and Title III regulations and enforcement context.
Create separate escalation paths for the EU market-surveillance or service-compliance authority, the ADA-covered entity and DOJ route, and the federal agency's program, complaint, acquisition, and remediation channels.
EAA controls can reuse design, testing, and remediation work only when the record shows the relevant EAA category, Annex I requirement, standard or technical specification, product or service owner, and release evidence.
Supports using standards as technical evidence while preserving the distinction between standards and mandatory legal requirements.
mandatory legal requirements
WCAG testing, accessible design, procurement questions, user feedback, and remediation can overlap across the US regimes. The binding version and coverage still differ: ADA Title II uses WCAG 2.1 Level A and AA, the Revised 508 Standards incorporate WCAG 2.0, and ADA Title III does not have one detailed DOJ web standard.
Supports treating WCAG as helpful guidance for Title III without claiming it is a detailed DOJ technical regulation for public accommodations.
Use shared accessibility engineering, but keep legal mappings separate. Each reused artifact should identify the tested scope, version, regime, exceptions, and unresolved requirements.
EAA accessibility requirements apply subject to Article 14. An operator must assess fundamental alteration or disproportionate burden; Annex VI criteria apply to the burden assessment. The assessment must be documented except for microenterprises dealing with products, which must provide relevant facts if requested by a market surveillance authority. Authorities can check the assessment. Microenterprises providing services are exempt from the relevant service accessibility requirements and related obligations.
Binding source for EAA fundamental alteration, disproportionate burden, Annex VI criteria, authority checks, and service microenterprise exemption.
fundamental alteration or impose a disproportionate burden
ADA and use different exceptions and safeguards. ADA Title II includes limited content exceptions, fundamental-alteration and undue-burden provisions, and continuing duties such as effective communication. Section 508 includes undue-burden, fundamental-alteration, and other ICT-specific exceptions with documentation requirements. None substitutes for an EAA Article 14 assessment.
Supports documented Section 508 exception decisions, including undue burden and fundamental alteration.
Keep each exception with its governing record and decision maker. Identify the affected requirement, written rationale, alternative access, approval, review date, and any continuing duty without importing one regime's language into another.
Supports retaining Article 14 assessments and identifying the requirements affected by an exception.
The assessment of disproportionate burden should be documented
Scope boundary
EU Accessibility Act
The EAA applies to selected products and services, including consumer computer hardware and operating systems, self-service terminals, consumer terminal equipment, e-readers, electronic communications services, audiovisual-media access services, passenger transport service elements, consumer banking, e-books, e-commerce, and answering emergency communications to 112.
Commission overview listing covered product and service categories.
products and services covered
ADA and Section 508
ADA Title II applies to state and local government services, programs, and activities, including covered web content and mobile apps. ADA Title III applies to public accommodations and their goods, services, privileges, and activities. applies when a federal agency develops, procures, maintains, or uses ICT.
Supports the Section 508 federal agency ICT boundary.
Operational implication
Create separate EAA, ADA Title II or III, and scope entries. A website, app, terminal, or digital service may fall under more than one regime because of the market, operator, government level, or customer.
Supports using EAA Article 2 and Annex I as the EU scope and requirement baseline.
accessibility requirements set out in Annex I
Covered actors
EU Accessibility Act
EAA duties are role-specific. Product obligations can apply to manufacturers, authorised representatives, importers, and distributors. Service obligations apply to service providers offering covered services to consumers in the Union.
Binding source for EAA operator definitions and duties for products and services.
Obligations of economic operators
ADA and Section 508
ADA Title II duties sit with the state or local government, including content or apps made available through contracts or licences. ADA Title III duties sit with the public accommodation. duties sit with the federal agency, although vendors supply evidence and accessible ICT.
Supports the federal department and agency duty-holder boundary.
Operational implication
Name accountable owners for EAA product conformity or service operation, ADA program or public-accommodation access, and federal acquisition and acceptance.
Supports separating manufacturer, importer, distributor, authorised-representative, and service-provider responsibilities.
service provider
Trigger
EU Accessibility Act
The EAA is concrete about product and service categories: it is not a universal accessibility statute for every digital asset. Confirm whether the item is a listed product, listed service, or emergency-communications activity before applying EAA requirements.
Supports the covered product and service category list used for practical scoping.
computers and operating systems
ADA and Section 508
For ADA Title II, the trigger is a state or local government service, program, or activity. For ADA Title III, it is a covered public accommodation's goods, services, privileges, or activities. For , it is federal agency development, procurement, maintenance, or use of ICT.
Supports the federal ICT lifecycle trigger for Section 508.
Operational implication
Tag the artifact to the covered actor and activity before reusing an audit. A federal procurement report, state mobile app test, retail website audit, and EAA conformity file answer different questions.
Supports mapping evidence to the EAA Article 2 product or service category.
products and services referred to in Article 2
Core obligations
EU Accessibility Act
Manufacturers must design and manufacture covered products in accordance with applicable EAA accessibility requirements, draw up technical documentation, carry out conformity assessment, draw up an EU declaration of conformity, affix CE marking where required, keep records, handle non-conformity, and cooperate with authorities. Service providers must design and provide covered services in accordance with the requirements and provide accessibility information.
Binding source for manufacturer, service-provider, non-conformity, authority-cooperation, and record duties.
When placing their products on the market
ADA and Section 508
ADA Title II requires covered web content and mobile apps to meet WCAG 2.1 Level A and AA after the applicable compliance date, subject to the rule's provisions, and preserves duties such as effective communication and reasonable modifications. requires accessible federal ICT under the Revised 508 Standards. ADA Title III requires equal access and effective communication but DOJ has not set one detailed technical web standard for public accommodations.
Supports the Revised 508 technical baseline for covered federal ICT.
Operational implication
Do not collapse the work into one WCAG ticket. Assign EAA conformity, ADA service access, ICT acceptance, user requests, complaints, corrective action, and standard-specific testing.
Supports separate EAA records for products, services, authorities, complaints, and corrective action.
provide it with all the information and documentation
Evidence record
EU Accessibility Act
EAA evidence should map Annex I requirements to technical documentation, service accessibility information, conformity assessment results, CE marking where applicable, EU declarations of conformity for covered products, and Article 14 records when an exception is used.
Supports use of EN 301 549 as an ICT accessibility standard for software, hardware, and combined ICT products and services.
ICT products and services
ADA and Section 508
ADA Title II evidence should identify the covered web content or mobile app, WCAG 2.1 Level A and AA test scope, exceptions, fixes, and continuing access arrangements. evidence should map the ICT to the Revised 508 provisions, including applicable non-web, hardware, software, support, and functional-performance requirements. Title III evidence should show how the public accommodation provides access and effective communication without overstating WCAG as a binding DOJ technical baseline.
Supports WCAG 2.0 incorporation and the wider Section 508 ICT evidence boundary.
Operational implication
Keep a crosswalk with the EAA requirement, EN 301 549 or other EU route, ADA title and rule provision, provision, test result, exception, remediation status, and claim boundary.
Supports documenting standards as voluntary routes used to demonstrate compliance with mandatory legal requirements.
demonstrate compliance
Timing and deadlines
EU Accessibility Act
The EAA required Member States to adopt and publish transposition measures by 28 June 2022 and apply them from 28 June 2025. It also includes transitional measures ending 28 June 2030 for certain service-provider products and limits for pre-existing service contracts and self-service terminals.
Commission source for public implementation context around the 28 June 2025 application date.
European Accessibility Act
ADA and Section 508
The 2026 DOJ interim final rule extends ADA Title II web and mobile app compliance to 26 April 2027 for entities with populations of at least 50,000 and to 26 April 2028 for smaller entities and special district governments. has no EAA-style market application date; apply the current federal standards to the agency's covered ICT lifecycle activity.
Official DOJ guidance confirms the April 2026 interim final rule extended compliance to 26 April 2027 for entities with populations of 50,000 or more and 26 April 2028 for smaller entities and special district governments.
Operational implication
Maintain separate EAA, ADA Title II, and federal acquisition milestones. Recheck the DOJ rule and the agency's process when scheduling a release or procurement.
Enforcement
EU Accessibility Act
EAA assurance is handled through national measures, market surveillance for products, service-compliance procedures, complaint or report follow-up, corrective action, withdrawal or restriction for non-compliant products, and Member State penalties that must be effective, proportionate, and dissuasive.
Binding source for EAA product market surveillance, service compliance procedures, corrective action, withdrawal, and penalty principles.
effective, proportionate and dissuasive
ADA and Section 508
ADA complaints and enforcement follow the applicable ADA title and DOJ procedures; contracts do not transfer a Title II public entity's responsibility. permits administrative complaints to the federal agency and provides statutory remedies for covered procurement, while agency acquisition and acceptance controls address defects operationally.
Official entry point for the separate ADA Title II and Title III regulations and enforcement context.
Operational implication
Create separate escalation paths for the EU market-surveillance or service-compliance authority, the ADA-covered entity and DOJ route, and the federal agency's program, complaint, acquisition, and remediation channels.
Overlap and reuse
EU Accessibility Act
EAA controls can reuse design, testing, and remediation work only when the record shows the relevant EAA category, Annex I requirement, standard or technical specification, product or service owner, and release evidence.
Supports using standards as technical evidence while preserving the distinction between standards and mandatory legal requirements.
mandatory legal requirements
ADA and Section 508
WCAG testing, accessible design, procurement questions, user feedback, and remediation can overlap across the US regimes. The binding version and coverage still differ: ADA Title II uses WCAG 2.1 Level A and AA, the Revised 508 Standards incorporate WCAG 2.0, and ADA Title III does not have one detailed DOJ web standard.
Supports treating WCAG as helpful guidance for Title III without claiming it is a detailed DOJ technical regulation for public accommodations.
Operational implication
Use shared accessibility engineering, but keep legal mappings separate. Each reused artifact should identify the tested scope, version, regime, exceptions, and unresolved requirements.
Practical decision rule
EU Accessibility Act
EAA accessibility requirements apply subject to Article 14. An operator must assess fundamental alteration or disproportionate burden; Annex VI criteria apply to the burden assessment. The assessment must be documented except for microenterprises dealing with products, which must provide relevant facts if requested by a market surveillance authority. Authorities can check the assessment. Microenterprises providing services are exempt from the relevant service accessibility requirements and related obligations.
Binding source for EAA fundamental alteration, disproportionate burden, Annex VI criteria, authority checks, and service microenterprise exemption.
fundamental alteration or impose a disproportionate burden
ADA and Section 508
ADA and use different exceptions and safeguards. ADA Title II includes limited content exceptions, fundamental-alteration and undue-burden provisions, and continuing duties such as effective communication. Section 508 includes undue-burden, fundamental-alteration, and other ICT-specific exceptions with documentation requirements. None substitutes for an EAA Article 14 assessment.
Supports documented Section 508 exception decisions, including undue burden and fundamental alteration.
Operational implication
Keep each exception with its governing record and decision maker. Identify the affected requirement, written rationale, alternative access, approval, review date, and any continuing duty without importing one regime's language into another.
Supports retaining Article 14 assessments and identifying the requirements affected by an exception.
The assessment of disproportionate burden should be documented
Practical decision rule
How should teams use this EAA vs ADA and Section 508 comparison?
Use the EAA column to build the EU scope, standards, procurement, evidence, and enforcement record.
Choose ADA Title II, ADA Title III, or from the actor and activity; do not treat them as one US standard.
Reuse accessibility tests only after mapping each result to an EAA requirement and to separately sourced US criteria.
State the exact WCAG or ICT standard version and tested boundary before a claim appears in a release, procurement, accessibility statement, or customer response.
Supports the Section 508 ICT boundary, WCAG 2.0 incorporation, and requirements beyond web content.
1
Section 1
Start with the actor and the regulated activity
For the EU side, start with Article 2 scope and the Commission's covered-products list: computers and operating systems, ATMs, ticketing and check-in machines, smartphones, TV equipment linked to digital television services, telephony services and equipment, audiovisual-media access services and equipment, passenger transport service elements, banking services, e-books, and e-commerce.
Then map the activity to the right EAA role. Product duties sit with economic operators such as manufacturers, importers, distributors, and authorised representatives. Service duties sit with service providers that provide services on the Union market or offer services to consumers in the Union.
For the US side, identify the entity before choosing a standard. ADA Title II covers state and local governments. ADA Title III covers businesses and nonprofit organisations that qualify as public accommodations. applies to federal departments and agencies when they develop, procure, maintain, or use ICT; it is not a general rule for every private website or every state government system.
This comparison is limited to EAA market duties, ADA Titles II and III, and federal ICT. It does not decide ADA Title I employment duties, ADA Title IV telecommunications relay duties, or separate state accessibility law. Add those regimes when the actor or activity brings them into scope.
Treat EAA scope as product-or-service specific, not as a general website-accessibility label.
Use the EU market fact pattern for the EAA: product placement, service provision, consumer-facing offer, and operator role.
For ADA Title II, identify the state or local government program, service, or activity and whether the web content or mobile app is provided directly or through a contractual or licensing arrangement.
For , identify the federal agency, the ICT lifecycle activity, the applicable Revised 508 provisions, and any properly approved exception.
Official DOJ summary of the Title II web and mobile app rule, its state and local government scope, WCAG 2.1 Level AA baseline, exceptions, and the compliance dates extended in 2026.
Official DOJ entry point distinguishing the ADA titles and their separate regulated activities.
2
Section 2
Evidence and standards should not be treated as interchangeable
EAA evidence for covered products should show the applicable Annex I requirements, technical documentation, conformity assessment, EU declaration of conformity, CE marking where required, and how product changes or harmonised-standard changes are handled. For covered services, the evidence should include the information explaining how the service meets applicable accessibility requirements, placed in general terms and conditions or an equivalent document.
EN 301 549 is relevant to ICT accessibility evidence because it covers software, hardware, and combinations of both. V3.2.1 is harmonised for the Web Accessibility Directive. ETSI now publishes EN 301 549 V4.1.1 (2026-09). Publication of an edition does not by itself establish an EAA presumption of conformity; verify the relevant Official Journal citation and the requirements it covers. Record the exact edition, clauses, citation, and legal effect being claimed.
The US regimes use different technical baselines. The 2024 ADA Title II web and mobile app rule uses WCAG 2.1 Level A and AA for covered state and local government content, subject to the rule's exceptions and other provisions. The Revised Standards incorporate WCAG 2.0 Level A and AA requirements for covered web content and apply specified WCAG criteria to non-web documents and software, while also covering ICT features beyond WCAG. DOJ's Title III web guidance describes WCAG as helpful technical guidance but does not set one detailed web standard for public accommodations.
Keep a crosswalk that names the regime, covered entity, regulated asset or activity, technical provision, tested scope, result, exception if any, remediation owner, and release or procurement decision. A test result can be reused only for requirements and system boundaries it actually covers.
For products, retain Annex I mapping, technical documentation, conformity assessment outputs, EU declaration of conformity, CE-marking decision, complaint and non-conformity records, and corrective-action logs.
For services, retain service accessibility information, accessibility test results, remediation logs, terms-and-conditions or equivalent publication evidence, and complaint follow-up records.
For standards, record the exact edition and legal route: an EU harmonised standard cited in the Official Journal, WCAG 2.1 under the ADA Title II rule, WCAG 2.0 as incorporated into the Revised 508 Standards, or non-binding guidance used for ADA Title III.
Supports the EAA evidence expectations for products, services, Annex I accessibility requirements, Article 14 exception assessments, and Annex IV conformity assessment.
The manufacturer shall establish the technical documentation.
Supports the description of EN 301 549 as an ICT accessibility standard and the limits of relying on it for EAA until the relevant support and version are confirmed.
Accessibility requirements for ICT products and services
Official standards and regulatory history for Section 508 ICT scope, WCAG 2.0 incorporation, non-web documents and software, hardware, support documentation, and functional performance criteria.
Official DOJ guidance distinguishing ADA Title II and Title III web duties and explaining the Title III technical-standard position; its Title II discussion predates the 2024 rule.
Official ETSI Human Factors page, retrieved 15 October 2026, listing published EN 301 549 V4.1.1 (2026-09). Publication is separate from Official Journal citation.
Recommended next step
Build separate EAA and US accessibility evidence records
Build separate EAA, ADA Title II or III, and Section 508 scope records, then cross-reference the tests that support more than one requirement.
Procurement and public-sector context differs from the US labels
The EAA has its own EU procurement effect. For products and services in Article 2, Annex I accessibility requirements constitute mandatory accessibility requirements for the procurement directives referenced in Article 24. That is not the same as proving coverage; it is an EU public-procurement consequence that should be recorded separately.
The EAA also has an implementation record that differs from US regimes: Member States had to adopt and publish transposition measures by 28 June 2022 and apply them from 28 June 2025, with specific transitional measures for certain service-provider products, pre-existing service contracts, and self-service terminals.
When one product or service is sold into both EU and US public-sector contexts, keep separate procurement questions. EAA Article 24 and Annex I govern the EU procurement consequence for covered products and services. governs federal agency ICT, including procurement, while ADA Title II can still apply to a state or local government's service or program even when a contractor supplies the technology.
Ask whether the procurement is for a product or service listed in EAA Article 2 before citing Article 24.
Record the Member State implementation measure and enforcement contact where the EU market is relevant.
Keep solicitation, accessibility conformance, exception, acceptance, and remediation records tied to the federal procurement; keep ADA Title II service-access records tied to the state or local government program.
Binding EAA source for scope, operator duties, Annex I accessibility requirements, Article 14 exceptions, CE marking, procurement effects, penalties framework, and dates.
Binding source for EAA scope, operator definitions, accessibility requirements, exceptions, conformity assessment, and enforcement mechanics.
Supports the EAA evidence expectations for products, services, Annex I accessibility requirements, Article 14 exception assessments, and Annex IV conformity assessment.
Show 15 more
Supports EAA procurement effects, transposition and application dates, transitional measures, and national enforcement structure.
Binding source for the EAA product, service, and emergency-communications scope.
Supports using EAA Article 2 and Annex I as the EU scope and requirement baseline.
Binding source for EAA operator definitions and duties for products and services.
Supports separating manufacturer, importer, distributor, authorised-representative, and service-provider responsibilities.
Supports mapping evidence to the EAA Article 2 product or service category.
Binding source for manufacturer, service-provider, non-conformity, authority-cooperation, and record duties.
Supports separate EAA records for products, services, authorities, complaints, and corrective action.
Supports EAA technical documentation, service information, EU declaration of conformity, CE marking, and Article 14 evidence references.
Binding source for EAA transposition, application, and transitional-measure dates.
Binding source for EAA product market surveillance, service compliance procedures, corrective action, withdrawal, and penalty principles.
Supports tying reused evidence to EAA categories, Annex I requirements, and conformity records.
Binding source for EAA fundamental alteration, disproportionate burden, Annex VI criteria, authority checks, and service microenterprise exemption.
Supports retaining Article 14 assessments and identifying the requirements affected by an exception.
Binding source for the EAA side of the comparison and the requirement to keep EAA evidence tied to EAA obligations.
"accessibility requirements for products and services"
More quoted passages
"The manufacturer shall establish the technical documentation."
"mandatory accessibility requirements"
"This Directive applies to"
"accessibility requirements set out in Annex I"
"Obligations of economic operators"
"service provider"
"products and services referred to in Article 2"
"When placing their products on the market"
"provide it with all the information and documentation"
"technical documentation"
"They shall apply those measures from 28 June 2025."
"effective, proportionate and dissuasive"
"the relevant accessibility requirements"
"fundamental alteration or impose a disproportionate burden"
"The assessment of disproportionate burden should be documented"
Official DOJ source for state and local government scope, WCAG 2.1 Level AA requirements, limited exceptions, continuing ADA duties, and the compliance dates extended to 26 April 2027 or 26 April 2028.
Official DOJ summary of the Title II web and mobile app rule, its state and local government scope, WCAG 2.1 Level AA baseline, exceptions, and the compliance dates extended in 2026.
Supports public-entity responsibility for content and apps made available directly or through contractual and licensing arrangements.
Show 6 more
Supports the WCAG 2.1 Level A and AA rule for covered state and local government web content and mobile apps and the continuing ADA duties.
Supports the Title II technical baseline, scope records, exceptions, and continuing access duties.
Supports the compliance dates extended in 2026 to 26 April 2027 or 26 April 2028.
Supports the WCAG 2.1 Level A and AA baseline for covered Title II web content and mobile apps.
Supports the limited Title II rule exceptions and continuing duties such as effective communication and reasonable modifications.
Supports the ADA Title II scope, WCAG 2.1 Level AA baseline, exceptions, continuing duties, and 2027 or 2028 compliance dates.
Official Section 508 technical standards for covered ICT, including WCAG 2.0 incorporation and requirements beyond web content.
Official standards and regulatory history for Section 508 ICT scope, WCAG 2.0 incorporation, non-web documents and software, hardware, support documentation, and functional performance criteria.
Supports the Revised 508 technical baseline for covered federal ICT.
Show 3 more
Supports WCAG 2.0 incorporation and the wider Section 508 ICT evidence boundary.
Supports the Revised 508 Standards' incorporation of WCAG 2.0 and wider ICT provisions.
Supports the Section 508 ICT boundary, WCAG 2.0 incorporation, and requirements beyond web content.
Official DOJ guidance for ADA Title III public-accommodation web duties and the absence of one detailed DOJ technical web standard for those businesses; the page's Title II discussion predates the 2024 rule.
Official DOJ guidance distinguishing ADA Title II and Title III web duties and explaining the Title III technical-standard position; its Title II discussion predates the 2024 rule.
Supports the ADA Title II state and local government boundary and the Title III public-accommodation boundary.
Show 3 more
Supports the ADA Title II and Title III activity-based triggers.
Supports Title III equal access and effective communication duties and the distinction between guidance and a detailed technical regulation.
Supports treating WCAG as helpful guidance for Title III without claiming it is a detailed DOJ technical regulation for public accommodations.
Official ETSI source for the ICT accessibility standard discussed in the standards and evidence section.
Supports the description of EN 301 549 as an ICT accessibility standard and the limits of relying on it for EAA until the relevant support and version are confirmed.
Supports use of EN 301 549 as an ICT accessibility standard for software, hardware, and combined ICT products and services.
Show 1 more
Supports use of ICT accessibility standards in evidence mapping while preserving source-specific legal conclusions.
"Accessibility requirements for ICT products and services"
Statutory text for federal agency duties when developing, procuring, maintaining, or using electronic and information technology, including comparable access and the undue-burden condition.
Supports the federal department and agency duty-holder boundary.
Supports the federal administrative complaint and civil-action framework for covered Section 508 procurement.
Published European standard. The cover identifies V4.1.1 (2026-09); its foreword distinguishes publication from Official Journal citation and the resulting legal presumption.
Official ETSI Human Factors page, retrieved 15 October 2026, listing published EN 301 549 V4.1.1 (2026-09). Publication is separate from Official Journal citation.
Official DOJ guidance confirms the April 2026 interim final rule extended compliance to 26 April 2027 for entities with populations of 50,000 or more and 26 April 2028 for smaller entities and special district governments.