# EqualWeb - Hybrid Accessibility Platform

EqualWeb is a next-generation digital accessibility platform, combining AI-powered remediation, certified IAAP/CPWA experts, continuous monitoring, and managed compliance to help organizations build, maintain, and prove accessibility at scale.

Legal name: EqualWeb Ltd.. Founded: 2014. Website: https://www.equalweb.com.
Category: Hybrid Accessibility Platform (also: Digital Accessibility Compliance Platform).
Audience: Enterprise & ecommerce brands; Government & public sector; Agencies; SMBs needing fast WCAG & ADA compliance.
Markets: United States, Canada, United Kingdom, European Union, Israel, Australia.
Certifications: IAAP CPACC/CPWA certified experts, ISO/IEC 27001:2022, GDPR, CCPA.
Differentiators:
- AI remediation paired with certified IAAP/CPWA human experts in one platform
- Continuous monitoring with a live 0-100 compliance score
- PDF / document accessibility automation
- Litigation support - expert evidence and documentation for accessibility claims
Contact: info@equalweb.com, +1 (646) 713-1717, 447 Broadway, 2nd FL #239, New York, NY 10013, US.
Contact page: https://www.equalweb.com/platform/contact.html - Book a meeting: https://www.equalweb.com/platform/book.html

## About / platform FAQ

Q: What is EqualWeb?
A: EqualWeb is a hybrid accessibility platform that combines AI-powered remediation, certified IAAP/CPWA accessibility experts, continuous monitoring, and managed compliance to help organizations build, maintain and prove digital accessibility compliance for WCAG 2.2, ADA, Section 508, AODA, EN 301 549 and the European Accessibility Act.

Q: Which accessibility standards and laws does EqualWeb support?
A: EqualWeb helps you meet WCAG 2.2 AA, the ADA, Section 508, AODA, EN 301 549 and the European Accessibility Act (EAA), and provides documentation to prove conformance.

Q: Is an automated accessibility widget enough for full ADA and WCAG compliance?
A: No. Automated tools resolve many issues instantly, but conformance also requires human review. EqualWeb pairs AI remediation with certified IAAP/CPWA experts and continuous monitoring for defensible compliance.

Q: How quickly can EqualWeb make my site accessible?
A: EqualWeb's AI widget adds accessibility in minutes, while its Managed Compliance service brings a site to certified conformance - typically up to 30 business days.

## Products

### Accessibility Widget
URL: https://www.equalweb.com/platform/accessibility_widget/

EqualWeb's Accessibility Widget is an AI-powered accessibility solution that automatically remediates WCAG 2.2, ADA and EAA issues on any website and adds a profile-based accessibility menu - installed with one line of code.

What it is: An AI accessibility widget (accessibility menu / Auto AI interface) that installs in one line of code and remediates accessibility issues in real time.
Who it's for: Content and ecommerce websites, SMBs and agencies that need WCAG and ADA compliance fast, without developers.
What it solves: Automatically fixes 80+ common WCAG 2.2 issues and gives users 9 accessibility profiles and 13+ assistive tools - without touching your source code.

Features:
- AI remediation of 80+ WCAG 2.2 issues
- 9 accessibility profiles
- 13+ assistive tools
- 100+ languages
- One-line install on any CMS
- Built-in accessibility statement

Page: AI Widget Assistant - https://www.equalweb.com/platform/accessibility_widget/ai-assistant.html
  The AI Widget Assistant answers visitors' accessibility questions in natural language, right inside the EqualWeb widget - in 100+ languages.
Page: Accessibility profiles & assistive tools - https://www.equalweb.com/platform/accessibility_widget/profiles.html
  Accessibility profiles for blind, motor-impaired, epileptic and elderly users - one click adapts the whole site to each visitor's needs.
Page: Make it yours - https://www.equalweb.com/platform/accessibility_widget/customization.html
  Customize the EqualWeb accessibility widget: colors, position, trigger icon, languages and profiles - match your brand without touching code.
Page: Install in one line of code - https://www.equalweb.com/platform/accessibility_widget/install.html
  Install the EqualWeb accessibility widget with one line of code - or follow platform guides for WordPress, Shopify, Wix and 40+ more. Live in minutes.
Page: Accessibility Widget Integrations - Install EqualWeb on Any Platform - https://www.equalweb.com/platform/accessibility_widget/integrations.html
  Step-by-step guides for installing the EqualWeb accessibility widget on WordPress, Shopify, Wix, Squarespace, Magento, Drupal and 35+ more platforms - each with screenshots.
Page: Accessibility Widget Pricing & Plans - https://www.equalweb.com/platform/accessibility_widget/pricing.html
  EqualWeb widget plans from $39/month with unlimited pageviews, WCAG 2.2 AA / ADA / Section 508 support, a 7-day free trial and 2 months free on annual.

Q: Is an accessibility widget enough for ADA compliance?
A: An accessibility widget alone is not guaranteed to make a website fully ADA compliant. EqualWeb's AI widget automatically remediates 80+ common WCAG 2.2 issues in real time, but full ADA and WCAG conformance often also needs human-verified fixes - which EqualWeb provides through its Managed Compliance service with certified IAAP/CPWA experts.

Q: How do I install the EqualWeb accessibility widget?
A: You add one line of JavaScript to your site's <head> section (or through your CMS). It works on WordPress, Shopify, Wix, Magento, Drupal and custom stacks, and the accessibility menu appears immediately. Every plan includes a 7-day free trial.

Q: How is the EqualWeb widget different from basic accessibility widgets?
A: Basic accessibility widgets only add user-side tools such as contrast and text resize. The EqualWeb Auto AI interface also performs real-time code remediation of WCAG 2.2 issues through the browser DOM - without changing your source files - and offers 9 accessibility profiles and 100+ languages.

Q: How many languages and profiles does the EqualWeb widget support?
A: The EqualWeb Accessibility Widget supports 100+ languages and includes 9 accessibility profiles (such as blindness, motor impairment, color-blind, epilepsy, ADHD, dyslexia and elderly) plus 13+ assistive tools.

Q: Does the EqualWeb widget change my website's source code?
A: No. The EqualWeb widget runs as an external layer and applies fixes in real time through the browser DOM, so your original source files are never modified.

Q: What is the EqualWeb AI Widget Assistant?
A: The AI Widget Assistant is an AI assistant built into the EqualWeb accessibility widget. Instead of hunting through the menu, visitors describe what they need in plain language - by text or voice - and the assistant applies the right accessibility adjustments and answers questions about the page.

Q: How is the AI assistant different from the accessibility menu?
A: The menu offers dozens of individual options to choose from. The assistant lets someone simply say what they need - for example 'the text is hard to read' - and it turns on the right profile and tools for them, so they don't have to know which setting to pick.

Q: Can people use voice as well as text?
A: Yes. Visitors can type a request or speak it, and the assistant responds and adjusts the page accordingly, in the widget's 100+ languages.

Q: Does the AI assistant replace the profiles and tools?
A: No - it's a faster way to reach them. Every change the assistant makes is one a visitor could also set manually in the accessibility menu; the assistant just removes the guesswork.

Q: How do the accessibility profiles in the EqualWeb widget help real users?
A: Each of the 9 profiles in EqualWeb's Accessibility Widget bundles the adjustments a real need requires, so visitors do not have to know which settings to change. The Blind profile optimizes structure and landmarks for screen readers, Motor impaired adds full keyboard navigation and larger targets, Visually impaired enlarges text and strengthens contrast, and Dyslexia applies a dyslexia-friendly typeface with adjustable letter and line spacing - all from one tap.

Q: What is the difference between an accessibility profile and an assistive tool in the EqualWeb widget?
A: In EqualWeb's Accessibility Widget, a profile reconfigures the whole page at once for a specific way of browsing - one tap turns on a bundled set of adjustments, so users do not need to pick individual settings. Assistive tools are the individual controls, such as the text reader, magnifier, reading guide or keyboard navigation, that any visitor can switch on separately to fine-tune the experience.

Q: What does the Seizure Safe profile in the EqualWeb widget do?
A: The Seizure Safe profile stops animations and dampens flashing and high-risk colors, making pages safer for visitors with epilepsy. Like every profile in EqualWeb's Accessibility Widget, it applies with one tap from the widget menu, with no page reload. In the dashboard's Menu Functions list it appears as the Epilepsy profile, which is included in paid widget plans rather than the free version.

Q: Can I turn off specific profiles or tools in the widget menu?
A: Yes. In the EqualWeb dashboard, go to Accessibility Widget, then Menu Functions. Every profile and tool has separate toggles for mobile and desktop, so you can disable any function on either platform; changes save automatically, and a Restore to default button re-enables everything. EqualWeb recommends keeping all functions enabled so visitors get the full set of options.

Q: Which assistive tools are included in the EqualWeb widget?
A: EqualWeb's Accessibility Widget includes 13+ assistive tools: a text reader, keyboard navigation, voice commands, a magnifier, bigger text, a readable font, link and header highlighting, a big cursor, a reading guide, stop animations, a dictionary, a virtual keyboard, and a page structure view. Each tool works independently, so visitors switch on exactly what they need.

Q: Can I change the EqualWeb widget's colors and icon to match my brand?
A: Yes. EqualWeb's Accessibility Widget offers 11+ button and menu colors, 14+ icons ranging from the standard access symbol to custom marks, and 5 button shapes from circle to square. Everything is set in the EqualWeb dashboard with a live preview and no coding, so the widget looks like a native part of your site rather than a plugin bolted on top.

Q: How do I change the position of the accessibility button on my website?
A: In the EqualWeb dashboard, open Accessibility Widget, then Customize Design, then the Icon design tab, and choose from 6 screen positions. You can also let visitors drag the button to a different spot, and for precise placement the widget code accepts a vPosition property with separate mobile and desktop values from 0 to 100 percent. After any position change, reinstall the updated widget code so it goes live.

Q: Do I need to reinstall the EqualWeb widget code after changing its design?
A: Yes, one extra step is needed. You design everything in the EqualWeb dashboard without coding, but the generated widget code carries your design configuration, so dashboard changes do not automatically update the live widget. After changing colors, icon, shape, size or position, open Install Widget Code, copy the newly generated snippet, and replace the old code on your website.

Q: Does the EqualWeb widget support right-to-left languages like Arabic and Hebrew?
A: Yes. The EqualWeb Accessibility Widget menu localizes itself in 100+ languages, including right-to-left languages such as Arabic and Hebrew, out of the box, so a single widget serves visitors in every market. You can change the menu language at any time in the dashboard, under General Info or in the Customize Design Advanced settings tab.

Q: Can I style the accessibility menu itself, not just the button?
A: Yes. Beyond the button, the menu has its own design settings. In the EqualWeb dashboard under Customize Design, the Menu design tab lets you set the menu's lead color, active color, and hover and focus colors, with a live preview as you work, so the open accessibility menu matches your site's palette as closely as the button does.

Q: Where does the EqualWeb widget code go on my website?
A: Paste the one-line JavaScript snippet just above the closing body tag, on every page of your site. You get the snippet from the EqualWeb dashboard's Install Widget Code page, where you can copy it, download it as a file, or email it with instructions to your developer. Once the page loads, the accessibility menu appears immediately.

Q: Do I need a developer to install the EqualWeb accessibility widget?
A: No. Installation is three steps: copy your one-line snippet from the EqualWeb dashboard, paste it before the closing body tag in your theme, template or tag manager, and publish. There is no build step, and the accessibility button is live for every visitor the moment the page loads. The whole process typically takes about a minute.

Q: Does the EqualWeb widget work on Shopify?
A: Yes. On Shopify you add the EqualWeb snippet to your theme.liquid template and the accessibility menu runs across your storefront. The one exception is checkout: Shopify blocks all third-party scripts on checkout pages, but Shopify's checkout pages are designed to be accessible, so accessibility is maintained there even without the widget.

Q: Can I use the same widget code on more than one website?
A: No. Each EqualWeb widget code is generated for one specific domain, and every domain and subdomain needs its own license and snippet. Using the same code on a different domain causes the widget to stop working or show a domain error. To cover another site, add it as a new site in the EqualWeb dashboard and install its own code.

Q: Why is the EqualWeb widget button not appearing after I installed the code?
A: The most common causes are an incorrectly embedded or modified snippet, an EqualWeb code issued for a different domain, JavaScript conflicts or security settings blocking the script, or placement that does not load on every page. Check that the full, unmodified code for your exact domain is embedded as provided, and contact support@equalweb.com if the issue persists.

### Accessibility Monitor
URL: https://www.equalweb.com/platform/Accessibility_Monitor/

EqualWeb's Accessibility Monitor is an enterprise accessibility monitoring tool that continuously scans your site against WCAG 2.2, tracks a live 0-100 compliance score, and flags lawsuit risk before it becomes a problem.

What it is: A continuous accessibility monitoring and scanning platform for WCAG 2.2 and Section 508.
Who it's for: Developers, QA teams and accessibility officers who need ongoing, demonstrable proof of compliance.
What it solves: Automatically detects new accessibility issues introduced by content and design changes, scores compliance 0-100, and exports issues to JIRA.

Features:
- Continuous WCAG 2.2 A/AA/AAA & Section 508 scanning
- 0-100 compliance score
- Lawsuit-risk rating
- XML sitemap & custom-URL scans
- Device & region simulation
- JIRA issue export
- Scheduled email reports


Q: What is accessibility monitoring?
A: Accessibility monitoring is the continuous, automated scanning of a website for accessibility issues over time. EqualWeb's Accessibility Monitor scans against WCAG 2.2 (Level A/AA/AAA) and Section 508, scores compliance 0-100, and alerts you when new issues appear after content or design changes.

Q: How much does the Accessibility Monitor cost?
A: The Monitor is priced by the number of pages monitored, with unlimited scans at a fixed yearly price: Basic - up to 100 pages - $790/year; Standard - up to 500 pages - $990/year; Advanced - up to 1,000 pages - $2,990/year; Enterprise - up to 5,000 pages - $9,990/year. A Premium plan tailored to your needs is available by quote, and every plan starts with a free 7-day trial.

Q: Does a 100% monitor score mean I'm fully ADA compliant?
A: No. A 100% score means no automated errors were detected at that time, but ADA and WCAG also include criteria that require human verification. EqualWeb recommends combining the Monitor with its Managed Compliance service for full coverage.

Q: Can EqualWeb scan password-protected or specific pages?
A: Yes. The Monitor can scan from your XML sitemap or custom URLs and simulate desktop and specific mobile devices, and EqualWeb's Crawler extension can scan authenticated, password-protected pages across a full domain.

Q: Can I send accessibility issues to JIRA?
A: Yes. Each issue in an EqualWeb scan report can be pushed to your JIRA board with a description, location, screenshot and a recommended fix.

Q: How often does EqualWeb scan my site?
A: You choose the schedule - weekly, monthly, quarterly or on demand - and reports are emailed automatically and saved in your dashboard.

### Managed Compliance
URL: https://www.equalweb.com/platform/managed_compliance/

EqualWeb Managed Compliance is a fully managed accessibility service where certified IAAP/CPWA experts audit, remediate, monitor and certify your site to full WCAG, ADA and EAA compliance - typically up to 30 business days.

What it is: An expert-led managed accessibility and compliance service: audit, manual remediation, certification and litigation support.
Who it's for: Enterprises, government bodies and regulated organizations that need full compliance and litigation support.
What it solves: Closes the gap automation can't - human-verified WCAG remediation, an Accessibility Compliance Certificate, and litigation support.

Features:
- Full accessibility audit by IAAP/CPWA experts
- Client-side code remediation
- Accessibility Compliance Certificate
- Continuous monitoring & re-scans
- Litigation support - expert evidence & documentation
- Delivered up to 30 business days

Page: Web Accessibility Audit, Testing & Compliance Validation Services - https://www.equalweb.com/platform/managed_compliance/audit.html
  Manual accessibility audits by certified IAAP/CPWA experts. Fixed-price packages by complexity, validation rounds, and a VPAT included at no extra charge.
Page: Website Accessibility Remediation Services - https://www.equalweb.com/platform/managed_compliance/remediation.html
  Website accessibility remediation: AI fixes up to 95% of common WCAG 2.2 issues, certified IAAP/CPWA experts remediate the rest in code - ADA and EAA.
Page: How Managed Compliance works - https://www.equalweb.com/platform/managed_compliance/how-it-works.html
  How EqualWeb Managed Compliance works: audit, expert remediation, monitoring and certification - a clear four-stage path to WCAG 2.2 AA.
Page: ADA Compliance Services: Make Your Website ADA Compliant - https://www.equalweb.com/platform/managed_compliance/ada-compliance.html
  ADA compliance for websites: free instant check, AI remediation of 80+ WCAG issues, and certified IAAP/CPWA experts who audit, fix and certify your site.
Page: EAA Compliance Services: Meet the European Accessibility Act - https://www.equalweb.com/platform/managed_compliance/eaa-compliance.html
  European Accessibility Act (EAA) compliance services: free instant check, AI remediation, and certified IAAP/CPWA experts who audit, remediate and document EN 301 549 / WCAG conformance - for any business serving EU consumers.
Page: AODA Compliance Services: Make Your Website AODA Compliant - https://www.equalweb.com/platform/managed_compliance/aoda-compliance.html
  AODA compliance services for Ontario websites: free instant check, AI remediation of common WCAG issues, and certified IAAP/CPWA experts who audit, remediate and document WCAG 2.0 AA conformance ahead of the 2026 compliance report.
Page: Accessibility Conformance Report (VPAT 2.2) - https://www.equalweb.com/platform/managed_compliance/vpat.html
  Get an expert-prepared VPAT / Accessibility Conformance Report (ACR) documenting your product's WCAG 2.2 conformance for procurement.
Page: Litigation support & documentation - https://www.equalweb.com/platform/managed_compliance/litigation.html
  Received a web accessibility demand letter or lawsuit? EqualWeb provides expert evidence, rapid remediation and documentation for your legal response.
Page: Standards & regulations we cover - https://www.equalweb.com/platform/managed_compliance/standards.html
  The accessibility standards EqualWeb covers: WCAG 2.2, ADA, Section 508, EN 301 549, EAA, AODA and more - one platform, global compliance.

Q: What is managed accessibility compliance?
A: Managed compliance is an expert-led service that takes a website to full accessibility conformance. EqualWeb's certified IAAP/CPWA specialists audit, manually remediate, monitor and certify your site for WCAG 2.2, ADA, Section 508 and the European Accessibility Act, typically up to 30 business days.

Q: What is the difference between the AI widget and Managed Compliance?
A: EqualWeb's Auto AI widget delivers automated coverage instantly - up to 95%, depending on how your site is built - while Managed Compliance adds manual expert audit and remediation, a signed Accessibility Compliance Certificate and litigation support for conformance. EqualWeb recommends combining both.

Q: Does EqualWeb provide proof of compliance or certification?
A: Yes. Managed Compliance clients receive an official Accessibility Compliance Certificate signed by a CPWA-certified expert, plus documentation suitable for a legal response.

Q: I received an accessibility lawsuit - can EqualWeb help?
A: Yes. EqualWeb provides standards-based remediation, an official certificate from a CPWA-certified specialist, a professional expert opinion, and technical evidence of compliance - documentation you can use in a legal response.

Q: How long does full accessibility remediation take?
A: EqualWeb's Managed Compliance is delivered up to 30 business days across four phases - audit & kickoff, remediation, QA & testing, and final review & delivery.

Q: What are the four stages of EqualWeb's Managed Compliance process?
A: EqualWeb Managed Compliance runs in four stages: Audit, Remediate, Monitor and Certify. Experts first benchmark your site against WCAG 2.2 and prioritize issues, then apply fixes and re-test each batch, continuous scanning tracks your live compliance score, and finally a signed Accessibility Compliance Certificate and full evidence pack are issued. Certification is delivered in up to 30 business days; monitoring is ongoing.

Q: What happens during the accessibility audit at the start of Managed Compliance?
A: The audit combines an automated WCAG 2.2 scan with a manual review by certified IAAP/CPWA auditors, who examine the templates, flows and documents that automated scanners cannot judge on their own. Scheduled for days 1-5 of the engagement, it produces a prioritized issue list ranked by severity and legal risk, plus your baseline 0-100 compliance score.

Q: Do I need my own developers for EqualWeb's Managed Compliance remediation?
A: No. EqualWeb's accessibility engineers apply expert fixes on the client side and layer in AI remediation, so assistive technology works without changes to your source code and without developer time on your side. In 99% of cases EqualWeb's team handles all issues, re-testing after each batch of fixes; you may only be asked for minor adjustments near the end.

Q: Does EqualWeb keep monitoring my website after remediation is finished?
A: Yes. Monitoring is a built-in stage of Managed Compliance and continues after delivery. Continuous scanning checks your site against WCAG 2.2, tracks a live 0-100 compliance score in your dashboard, and flags regressions the moment new content or code is published, with alerts on new issues and lawsuit-risk changes - so you stay compliant rather than compliant once.

Q: Who actually performs the work in EqualWeb's Managed Compliance service?
A: Each stage has a named owner. Certified IAAP/CPWA auditors run the audit alongside EqualWeb's AI scanning engine; accessibility engineers carry out remediation supported by an AI remediation layer; automated monitoring feeds your live dashboard; and a CPWA-certified compliance specialist verifies conformance and signs the final Accessibility Compliance Certificate.

Q: What documentation does EqualWeb provide if I receive an accessibility demand letter?
A: EqualWeb Managed Compliance produces a complete documentation pack you can hand to your own legal team: an Accessibility Compliance Certificate signed by a CPWA-certified specialist, a written professional expert opinion, an Accessibility Conformance Report (VPAT), technical evidence of the remediation performed, an audit trail with re-scan history, and a published accessibility statement. The pack is kept current while your site stays under management.

Q: Does EqualWeb provide legal advice or represent me in an accessibility lawsuit?
A: No. EqualWeb is not a law firm and does not provide legal advice or legal representation. What Managed Compliance provides is accessibility remediation, monitoring and expert documentation - reports prepared by certified specialists that support your own legal team's response. The documentation is evidence of your accessibility work, not a promise of any particular legal outcome.

Q: Can EqualWeb guarantee my website will never face an accessibility claim?
A: No, and EqualWeb does not make that promise. Accessibility conformance depends on your ongoing content and configuration, so it cannot be absolutely guaranteed. What Managed Compliance provides is expert remediation, continuous monitoring and documentation - a signed Accessibility Compliance Certificate, a professional expert opinion and an audit trail - so that if a claim arrives, you respond from a documented position rather than empty-handed.

Q: What happens if something EqualWeb remediated is later found non-conformant?
A: While your Managed Compliance plan is active and used in line with EqualWeb's Terms of Service, EqualWeb re-remediates the item at no additional charge. You may also be eligible for a partial refund where the conditions set out in the Terms of Service are met. Both are service remedies defined by the Terms, not legal guarantees of any outcome.

Q: Which accessibility standards and regulations does EqualWeb's Managed Compliance cover?
A: Managed Compliance certifies websites against the standards of every market you operate in: WCAG 2.2 (the globally recognized technical standard), the ADA and Section 508 in the United States, the AODA in Ontario, Canada, and the European Accessibility Act and EN 301 549 in the European Union. EqualWeb's standards library documents 14 standards and regulations in total, with a plain-English guide for each.

Q: How do laws like the ADA and the European Accessibility Act relate to WCAG?
A: Nearly every accessibility regulation points back to WCAG, the technical standard that specifies how to make digital content accessible. Laws such as the ADA, Section 508, the AODA, the EAA and EN 301 549 set the legal obligation by region, while WCAG success criteria define how to meet it. EqualWeb's certified experts audit, remediate and monitor your site against the exact standards your markets require.

Q: How do I know which accessibility standards apply to my website?
A: It depends on where you operate and who your customers are. US businesses generally face the ADA, US federal agencies and their vendors face Section 508, organizations in Ontario face the AODA, and companies selling into the EU face the European Accessibility Act and EN 301 549. EqualWeb maps your site to every standard for your markets, and a certified specialist can walk you through which laws apply.

Q: Does EqualWeb's Managed Compliance cover the European Accessibility Act?
A: Yes. The European Accessibility Act (EAA) and EN 301 549, the EU's accessibility requirements standard for ICT, are both covered by Managed Compliance. Because EU regulation points back to WCAG, EqualWeb's certified experts audit and remediate your site against the relevant WCAG criteria, then issue the Accessibility Compliance Certificate and conformance report (VPAT) that document your conformance for the EU market.

Q: What is a VPAT and what does an Accessibility Conformance Report include?
A: A VPAT (Voluntary Product Accessibility Template) is the standard format for documenting how a digital product conforms to accessibility requirements; the completed document is an Accessibility Conformance Report. EqualWeb prepares VPAT 2.2 (WCAG Edition) reports to the ITI template, rating every applicable criterion as Supports, Partially Supports, Does Not Support or Not Applicable, with remarks explaining how each is met.

Q: Who needs a VPAT or Accessibility Conformance Report?
A: Any vendor whose buyers ask for proof of accessibility. Enterprise and public-sector procurement teams request a VPAT before they will sign, and US federal agencies require an Accessibility Conformance Report for ICT procurement under Section 508. In the EU, the same report documents conformance with EN 301 549. Without one, RFP responses often stall - no report frequently means no deal.

Q: Which standards does EqualWeb's VPAT 2.2 report cover?
A: EqualWeb's VPAT 2.2 (WCAG Edition) report evaluates conformance with WCAG 2.0, 2.1 and 2.2 at Levels A and AA, the Revised Section 508 standards (the 2017 US refresh) and EN 301 549 for the European Union. The full report covers every applicable criterion, and each one receives a conformance rating plus a remark describing how it is met.

Q: How does EqualWeb prepare and verify a VPAT?
A: EqualWeb's accessibility engineers test your product manually with screen readers and run automated scans using EqualWeb's in-house WCAG monitor. They write per-criterion remarks explaining how each requirement is met, and a CPWA-certified specialist reviews and signs off on the finished Accessibility Conformance Report - a documented, expert-prepared evaluation rather than a checkbox exercise.

Q: Is a VPAT included in EqualWeb's Managed Compliance service?
A: Yes. EqualWeb prepares the Accessibility Conformance Report as part of Managed Compliance: while your site is audited, remediated and certified, experts complete the VPAT and include it in your evidence pack alongside the Accessibility Compliance Certificate and expert opinion - ready for procurement, legal and your customers. Managed Compliance is quote-based, so request a demo to scope your report.

Q: How do I check if my website is ADA compliant?
A: Start with EqualWeb's free Accessibility Checker: enter your URL and get an instant WCAG 2.2 score from 0 to 100 with a prioritized issue list, no installation required. For a fuller picture, the Accessibility Monitor offers a free 100-page scan across your site. Because some WCAG criteria require human judgment, a certified expert audit is the only way to confirm conformance.

Q: How much does ADA compliance cost?
A: It depends on the size and complexity of your site - EqualWeb prices full Managed Compliance (audit + expert remediation + certification) by scope, so that proposal is quote-based. If you want a fixed price, the standalone Accessibility Audit has published packages: $4,800, $13,500 or $24,440 per project depending on complexity, with a VPAT included. The sensible sequence: run the free Accessibility Checker first, try the Accessibility Widget with its 7-day free trial, then pick the audit package or request a Managed Compliance quote.

Q: Is an accessibility widget enough to make my website ADA compliant?
A: No, and you should be skeptical of anyone who says otherwise. EqualWeb's Accessibility Widget automatically fixes 80+ common WCAG 2.2 issues - up to 95% of typical problems, depending on how your site is built - which is a strong start and a meaningful risk reduction. But WCAG criteria involving context and judgment require human review. Full compliance is the goal of EqualWeb's expert-led Managed Compliance service, which combines the widget with certified manual remediation.

Q: Is there a deadline for ADA website compliance?
A: For state and local governments under ADA Title II, yes: the DOJ rule requires WCAG 2.1 Level AA by April 26, 2027 for entities serving populations of 50,000 or more, and by April 26, 2028 for smaller entities and special districts. For private businesses under Title III there is no fixed deadline - the obligation applies now, and lawsuits are already being filed. EqualWeb's free Accessibility Checker shows where you stand today.

Q: How long does it take to make a website ADA compliant?
A: The free Accessibility Checker scores any page in seconds, and the Accessibility Widget starts fixing 80+ common WCAG 2.2 issues within minutes of installing one line of code. Full, certified conformance through EqualWeb's Managed Compliance takes up to 30 business days across four stages: audit, remediation, monitoring and certification. After delivery, continuous monitoring keeps your compliance score current as your site changes.

Q: Does my small business website really need to be ADA compliant?
A: Yes. ADA Title III covers virtually every business open to the public, including online-only businesses, with no small-business or revenue-based exemption for digital content. Serial plaintiffs file thousands of website accessibility cases annually, and settlements typically run $5,000 to $75,000 plus legal fees. EqualWeb's free Accessibility Checker shows where your site stands in seconds, and the widget's 7-day free trial is a low-risk first step.

Q: What is the European Accessibility Act and what does it require?
A: The European Accessibility Act (EAA) is Directive (EU) 2019/882, an EU law that mandates accessible design for key consumer-facing products and services - including e-commerce, banking, telecoms, and digital media - across all 27 Member States. It requires businesses to meet the technical requirements in EN 301 549, which incorporates WCAG 2.1 Level AA for digital content. Compliance has been legally required for new products and services since June 28, 2025.

Q: Who has to comply with the European Accessibility Act?
A: Any business that sells or provides in-scope products or services to consumers in the EU must comply, regardless of where the business is based. This includes non-EU companies with EU customers. The only blanket exemption is for microenterprises (fewer than 10 employees and annual turnover of no more than 2 million euros) that provide services; microenterprises manufacturing or distributing covered products still have obligations.

Q: What is the EAA compliance deadline?
A: The primary enforcement date was June 28, 2025, from which all new covered products placed on the market and new services launched must comply. Existing services and products already on the market before that date have a transitional period until June 28, 2030. Self-service terminals already in use may continue operating until the end of their economic life, up to a maximum of 20 years from deployment.

Q: What are the penalties for not complying with the EAA?
A: Penalties are set by each EU Member State and vary considerably. Spain and Sweden can impose fines up to 1,000,000 euros for serious violations. Germany provides fines up to 100,000 euros for non-compliant products. France can reach 250,000 euros for systemic non-compliance. Enforcement authorities may also order market withdrawal of non-compliant products, prohibit services, or mandate audits. Ireland additionally allows criminal penalties including imprisonment, and some countries impose daily fines until compliance is achieved.

Q: Does the EAA require WCAG 2.1 AA or WCAG 2.2?
A: The EAA's current presumed conformance standard, EN 301 549, incorporates WCAG 2.1 Level AA for web and software content - not WCAG 2.2. A forthcoming revision is planned to incorporate WCAG 2.2 AA, but it is not yet the required standard. Organizations that have already implemented WCAG 2.2 AA will satisfy and exceed the WCAG-related requirements of EN 301 549 today.

Q: How does EqualWeb help with EAA compliance?
A: EqualWeb combines a free instant accessibility check, an AI widget that automatically fixes 80+ common WCAG issues, and Managed Compliance - certified IAAP/CPWA experts who audit, remediate and document conformance to EN 301 549, delivering a signed certificate, a conformance report and an evidence pack for market surveillance authorities, plus continuous monitoring and PDF remediation for electronic documents.

Q: What is the AODA and what does it require?
A: The Accessibility for Ontarians with Disabilities Act (AODA) is an Ontario law that obligates organizations operating in the province to remove barriers for people with disabilities across customer service, employment, information and communications, transportation, and public spaces. For digital properties, the Integrated Accessibility Standards Regulation requires covered organizations to make public websites and web content conform to WCAG 2.0 Level AA. The Act also mandates written accessibility plans, accessible employment practices, and regular compliance reporting.

Q: Who must comply with the AODA?
A: The AODA applies to any person or organization with at least one employee in Ontario that provides goods, services, or facilities to the public. Website accessibility obligations specifically apply to public-sector organizations of any size and to private businesses or non-profits with 50 or more employees in Ontario. Smaller private-sector organizations remain subject to other AODA standards such as accessible customer service.

Q: What is the AODA web accessibility deadline?
A: The primary web accessibility deadline passed on January 1, 2021, by which all public-sector organizations and private/non-profit organizations with 50 or more employees were required to meet WCAG 2.0 Level AA. Looking ahead, private-sector businesses and non-profits with 20 or more employees must file their next Accessibility Compliance Report by December 31, 2026.

Q: What are the AODA penalties for non-compliance?
A: The AODA imposes significant financial penalties: up to $100,000 per day for corporations and up to $50,000 per day for individuals, unincorporated organizations, or corporate directors and officers. Enforcement by the Accessibility Directorate of Ontario is progressive - a notice of non-compliance, then a Director's Order, then administrative monetary penalties or prosecution. Failure to file a required Accessibility Compliance Report is itself a violation.

Q: Does the AODA require WCAG 2.1 or WCAG 2.2?
A: No - the AODA's Integrated Accessibility Standards Regulation currently requires WCAG 2.0 Level AA. However, adopting WCAG 2.1 or 2.2 Level AA is strongly recommended as a forward-looking best practice, and Canada's federal Accessible Canada Act references EN 301 549, which incorporates WCAG 2.1 - suggesting an upward trajectory for Canadian requirements.

Q: How does EqualWeb help with AODA compliance?
A: EqualWeb combines a free instant accessibility check, an AI widget that automatically fixes 80+ common WCAG issues, and Managed Compliance - certified IAAP/CPWA experts who audit, remediate and document WCAG conformance, delivering a signed certificate and the evidence to support your Accessibility Compliance Report filing, plus continuous monitoring between reporting cycles.

### PDF Tools
URL: https://www.equalweb.com/platform/pdf_tools/

EqualWeb PDF Tools make documents accessible automatically - checking, AI-remediating and serving accessible PDFs that meet WCAG 2.2, PDF/UA-1 and PDF/UA-2 (ISO 14289-1 and ISO 14289-2:2024) and Section 508.

What it is: A suite of PDF accessibility tools: a checker, AI auto-remediation, expert manual remediation, and an accessible in-browser PDF viewer.
Who it's for: Government, finance and education teams that publish high volumes of PDF documents.
What it solves: Audits PDFs with 80+ automated checks, then remediates the whole document - structure and reading order, alt text, tables, forms, fonts and text encoding, color contrast, language and metadata - and publishes accessible documents at scale.

Features:
- PDF Accessibility Checker (8 categories + score)
- AI auto-tagging to WCAG 2.2 & PDF/UA
- Expert manual remediation
- Accessible in-browser PDF viewer
- Uploads up to 400 pages / 100 MB per file
- Batch upload up to 1,000 PDFs

Page: PDF Accessibility Checker - https://www.equalweb.com/platform/pdf_tools/checker.html
  Check PDF accessibility online free: 80+ automated checks in 8 categories, a 0-100 WCAG 2.2 / PDF/UA score, and AI alt text for every image - in seconds.
Page: AI Auto-Remediation - https://www.equalweb.com/platform/pdf_tools/auto-remediation.html
  AI auto-remediation makes PDFs accessible in minutes: tagging, reading order and alt text to PDF/UA and WCAG standards - at batch scale.
Page: Expert Manual Remediation - https://www.equalweb.com/platform/pdf_tools/manual.html
  Certified experts manually remediate complex PDFs - forms, tables, scanned files - to PDF/UA-1, PDF/UA-2 and WCAG 2.2 standards.
Page: Accessible PDF Viewer - https://www.equalweb.com/platform/pdf_tools/viewer.html
  The Accessible PDF Viewer lets every visitor read PDFs with a screen reader directly in the browser - no downloads, no plugins.
Page: PDF Audit API - https://www.equalweb.com/platform/pdf_tools/api.html
  The EqualWeb PDF Audit API automates PDF accessibility from your own system: REST endpoints that audit, AI-remediate and score documents against WCAG 2.2, PDF/UA (ISO 14289), ADA, Section 508, EN 301 549 and the EAA.
Page: Free PDF Checker & AI Accessibility Remediation - 7 Platforms - https://www.equalweb.com/platform/pdf_tools/integrations.html
  EqualWeb PDF Accessibility scans every PDF in the systems you already use - WordPress, Drupal, Moodle, Shopify and Canvas LMS as installed apps, plus Cloud Connect for SharePoint, Google Drive, OneDrive, Dropbox, Box and S3-compatible storage - scores each document, prioritizes by legal exposure, and remediates in place without breaking a single link.
Page: PDF Tools Pricing - Simple Credit-Based Pricing for PDF Accessibility - https://www.equalweb.com/platform/pdf_tools/pricing.html
  EqualWeb PDF Tools pricing: one wallet of credits, fixed per-page rates - 0.05 credits to check a document, 1 credit per page for AI remediation, 0.2 credits per page for accessible HTML. The more credits you buy, the less each one costs.
Page: PDF Accessibility Security & Data Privacy - How EqualWeb Protects Your Documents - https://www.equalweb.com/platform/pdf_tools/security.html
  How EqualWeb protects your documents during PDF accessibility remediation: minimal data exposure, retention you control (0/90/360 days or never), no AI training on your files ever, human review, TLS encryption, AES-256 and ISO/IEC 27001.

Q: How do I make a PDF accessible?
A: Upload the PDF to EqualWeb PDF Tools. The AI audits it with 80+ checks, then remediates every layer of the document: it builds the tag structure where none exists and repairs it where it's broken - headings, tables and lists, reading order - writes image alt text, labels form fields and links and sets tab order, embeds fonts and fixes text encoding so screen readers read the real text, corrects color contrast, and sets document language, title and metadata. You get an accessible PDF compliant with WCAG 2.2, PDF/UA-1 & PDF/UA-2 and Section 508 - automatically re-audited, with a report and a numerical score. Complex files can be finished by EqualWeb's certified experts.

Q: What standards do accessible PDFs need to meet?
A: Accessible PDFs are typically required to meet WCAG 2.2, PDF/UA-1 and PDF/UA-2 (ISO 14289-1 and ISO 14289-2:2024), Section 508 and EN 301 549. EqualWeb PDF Tools remediate and validate documents against all of these - including PDF/UA-2, the 2024 revision of the standard.

Q: Can EqualWeb remediate scanned (image-only) PDFs?
A: Yes. Digitally created PDFs with live text go straight through AI remediation. Scanned, image-only PDFs are first converted with OCR - turning the page images into tagged, readable text - then remediated like any other document. Unusually complex scans can be finished by EqualWeb's certified experts.

Q: What are the file limits?
A: Upload non-scanned PDFs up to 100 MB and 400 pages per file, and up to 1,000 PDFs at a time. Standard page sizes from 6&quot; to 17.5&quot; in either dimension are supported. Audit operations process documents up to 400 pages - larger PDFs upload but are flagged when audited. Remove hidden content such as JavaScript from a PDF before processing, and for InDesign PDFs address any missing fonts by adding the font files to the fonts folder. The Auto AI Tag is currently optimized for remediating English and Latin languages.

Q: What do I receive after PDF remediation?
A: You receive an accessible PDF compliant with WCAG 2.2 / PDF/UA / Section 508, a detailed report of what was fixed and what remains, and a numerical accessibility score; Managed clients also get a formal conformance validation.

Q: How do I check if a PDF is accessible?
A: Upload the document to EqualWeb's PDF Accessibility Checker. It audits the file with 80+ automated checks across 8 categories - Document, Page Content, Forms, Alternate Text, Tables, Lists and Headings - and returns a 0-100 accessibility score. Each rule is marked Passed, Needs Review or Failed, so you can see exactly where the document stands before deciding whether to fix it with AI or experts.

Q: What does EqualWeb's PDF Accessibility Checker actually check?
A: EqualWeb's PDF Accessibility Checker inspects the structures screen readers rely on: document language, title and tags, a logical tagged reading order, heading hierarchy, correctly marked-up lists, alternative text on every image, table header associations, and labeled form fields. It also flags items like color contrast for review, then rolls everything into a single 0-100 score you can share with your team.

Q: What do Passed, Needs Review and Failed mean in the PDF Checker report?
A: Passed means the rule is satisfied. Needs Review means EqualWeb's AI could not fully verify the rule - items like logical reading order and color contrast - so a manual check is recommended. Failed means the rule is violated and the document needs fixing. The report totals each status per category, so you know how many issues were resolved and how many still need attention.

Q: Does the PDF Checker write alt text for images?
A: Yes. EqualWeb's PDF Accessibility Checker reads every image in the document and generates a suggested alternative text description for each one. The report lists each image with its page number and the AI-written description, and you can review, edit and apply the suggestions instead of writing alt text from scratch. Missing alt text is the most common PDF accessibility failure.

Q: Does the PDF Accessibility Checker fix the issues it finds?
A: No. The Checker is an audit-only tool: it reports issues and scores the document without changing the file. To apply fixes, pair it with EqualWeb's AI Auto-Remediation, which tags headings, tables, alt text and reading order automatically, or with Expert Manual Remediation for complex documents. A Checker report also ships with every remediation, so you get a before and after comparison.

Q: How does AI auto-remediation for PDFs work?
A: You upload a PDF to EqualWeb's AI Auto-Remediation and the engine remediates the document in one pass: it builds the tag tree where none exists, sets heading levels, table headers, image alt text, lists and a logical reading order, repairs font embedding and text encoding so screen readers speak the real text, corrects color contrast, and sets the document language, title and metadata - aligned to WCAG 2.2 and PDF/UA. The output is a tagged, accessible PDF you download, together with a Checker report and an accessibility score showing what was fixed.

Q: What does the AI actually fix in a PDF?
A: EqualWeb's AI Auto-Remediation adds the semantic structure assistive technology needs - heading levels, a corrected logical reading order, table markup with row and column headers, properly structured lists, descriptive link tagging, AI-generated alternative text for images and tagged form fields - and then goes below the surface: font embedding and Unicode repair so text is read aloud correctly and stays searchable, WCAG AA color contrast, navigation bookmarks, and document metadata such as title and language. Accessible PDFs are about structure rather than looks, and this is the layer screen readers read.

Q: How many PDFs can I remediate at once?
A: EqualWeb's AI Auto-Remediation accepts batch uploads of up to 1,000 PDFs in a single job. You can drag and drop files, browse, or upload from a URL, and the system flags scanned, image-only documents automatically, running an extra OCR step that handles files up to 400 pages. Every file in the batch is tagged and comes back with its own accessibility score and Checker report.

Q: What languages does AI PDF remediation support?
A: EqualWeb's automatic AI tagging is currently optimized for English and Latin-script languages. PDFs in other languages can be uploaded, but automated tagging support may be limited. For documents the AI cannot fully handle, EqualWeb's IAAP/CPWA-certified experts can remediate the file by hand through Expert Manual Remediation and verify it with real screen readers.

Q: Can I upgrade an AI-remediated PDF to expert remediation?
A: Yes. Every file processed by EqualWeb's AI Auto-Remediation can be sent on to certified experts using the Upgrade to Manual option in the dashboard. IAAP and CPWA-certified accessibility specialists then review and re-tag the document by hand, delivering a higher-quality, human-verified remediation. Use it when an AI-remediated file needs deeper quality work or formal verification.

Q: Is AI trained on my documents?
A: No - never. EqualWeb does not train or fine-tune AI models on client documents, and does not retain documents, text fragments or images for training. Most structural fixes are performed by EqualWeb's own deterministic remediation engine; AI is applied only at defined points, such as image descriptions and form labels, under minimal-exposure rules. File retention is under your control - 0, 90, 360 days or never - and the Security and Data Privacy page details the full commitments.

Q: When does a PDF need manual remediation instead of AI?
A: Automation handles most PDFs, but some documents need expert judgement to be truly usable. EqualWeb recommends Expert Manual Remediation for complex tables with merged cells or nested headers, multi-step interactive forms with calculated or conditional fields, legal and financial documents such as contracts and disclosures, and scanned originals where OCR alone is not enough. Certified specialists remediate these files page by page.

Q: Who performs EqualWeb's manual PDF remediation?
A: EqualWeb's Expert Manual Remediation is performed by certified IAAP and CPWA accessibility specialists. They manually review every page and hand-tag the document structure, reading order and table markup rather than relying on automated tagging. It reflects EqualWeb's hybrid model: AI handles documents at scale, while certified experts take over the files automation cannot finish.

Q: How are manually remediated PDFs tested and verified?
A: EqualWeb tests every manually remediated PDF with real screen readers - NVDA, JAWS and VoiceOver - not just automated checks. Experts also perform contrast checking and a visual accessibility review, then formally validate conformance against WCAG 2.2, PDF/UA and Section 508. The result is a remediated document verified by a certified IAAP/CPWA expert rather than inferred from a software scan.

Q: What documentation do I get with expert manual remediation?
A: Each PDF remediated by EqualWeb's experts is delivered with validation documents: a formal record of conformance against WCAG 2.2, PDF/UA and Section 508 that you can show auditors and stakeholders, plus a detailed Checker report. For organizations on EqualWeb's Managed Compliance program, this formal conformance validation folds into the wider compliance documentation.

Q: How does the Accessible PDF Viewer work on my website?
A: EqualWeb's Accessible PDF Viewer is added with a single line of JavaScript. The script automatically detects every PDF link on your site, with no per-document markup, and when a visitor clicks one, the document opens in an accessible in-browser viewer instead of downloading. Content is presented as semantically structured, keyboard-navigable, screen-reader-friendly HTML, with the original file still available alongside.

Q: What reading tools are built into the viewer?
A: EqualWeb's Accessible PDF Viewer includes a navigable document outline, a read-aloud Text Reader that highlights text as it reads, an AI-generated summary, a click-to-define dictionary, an Ask-a-Question tool for the document's content, translation into 100+ languages, and display settings covering dark mode, font size, line height and letter spacing. No plugin, separate app or download is required.

Q: Can I customize the PDF viewer to match my brand?
A: Yes. EqualWeb's Design Your Viewer panel lets you set the viewer's colors - including the accent, header and menu colors - and choose which menu tools appear, so the reading experience matches your site. Once configured, you copy a single embed line and every PDF you link opens in your branded, accessible viewer with no per-document work.

Q: Can visitors still download the original PDF?
A: Yes. The original PDF always remains available alongside the accessible web version, so readers choose the format they prefer. From EqualWeb's Accessible PDF Viewer they can switch between the web view and the PDF, download either the original file or the accessible HTML version, and print directly from the viewer.

Q: Do my PDFs need to be converted before the viewer can show them?
A: Yes. Documents are processed through EqualWeb's web view conversion, which turns each PDF into semantically structured, accessible HTML that the viewer serves in the browser, with proper headings, tables, reading order and ARIA markup. You upload PDFs or import them from your site, select web view conversion, and once processed your linked PDFs open in the accessible viewer.

### Accessibility Checker
URL: https://www.equalweb.com/platform/accessibility_checker/

EqualWeb's Accessibility Checker is a free web accessibility checker that scans any URL against WCAG 2.2 and returns an instant accessibility score with a prioritized list of issues to fix.

What it is: An instant, free web accessibility checker that audits a page against WCAG 2.2.
Who it's for: Marketers, developers and site owners who want a quick accessibility check before going deeper.
What it solves: Gives an immediate WCAG 2.2 score and a clear, prioritized list of accessibility issues for any URL - the fastest way to see where a site stands.

Features:
- Instant single-page WCAG 2.2 scan
- 0-100 accessibility score
- Prioritized issue list
- No installation required
- Shareable report

Page: Color Contrast Checker - https://www.equalweb.com/platform/accessibility_checker/color-checker.html
  Free color contrast checker: test any color pair against WCAG 2.2 ratios (4.5:1, 3:1, 7:1) and find every contrast failure on a page, domain or PDF.

Q: How do I check if my website is accessible?
A: Enter your URL in EqualWeb's Accessibility Checker and it scans the page against WCAG 2.2, returning an accessibility score and a prioritized list of issues in seconds - no installation needed.

Q: Is the EqualWeb Accessibility Checker free?
A: Yes - the instant single-page check is free. For full-domain scans use the EqualWeb Accessibility Crawler, and for ongoing tracking use the Accessibility Monitor.

Q: What does the accessibility score mean?
A: The 0-100 score reflects how well the page meets WCAG 2.2 success criteria; the report lists each issue by severity with guidance on how to fix it.

Q: Does a passing checker score guarantee ADA compliance?
A: No. Automated checks catch many issues but not all - some WCAG criteria require human review. EqualWeb's Managed Compliance adds certified expert audit for conformance.

Q: How do I check if my website colors are accessible?
A: Run a free instant check with EqualWeb's Accessibility Checker: enter your URL and it scans the page against WCAG 2.2, flagging every element below the required contrast ratio, mapped to the exact success criterion such as 1.4.3, alongside a 0-100 score. For broader coverage, the Accessibility Crawler scans entire domains and the Accessibility Monitor rescans continuously as your site changes.

Q: What contrast ratio does WCAG require?
A: WCAG 2.2 Level AA requires at least 4.5:1 between normal text and its background, and at least 3:1 for large text, defined as 18pt or 14pt bold (SC 1.4.3). Non-text elements such as buttons, form borders and meaningful icons need at least 3:1 under SC 1.4.11. At the stricter Level AAA, SC 1.4.6 raises the text requirements to 7:1 for normal text and 4.5:1 for large text.

Q: Does EqualWeb have a color contrast checker?
A: Yes - contrast checking is built into every EqualWeb testing tool rather than offered as a separate picker. The free Accessibility Checker flags low-contrast text on any URL in seconds, the Accessibility Crawler checks contrast across your whole domain including protected pages, the Accessibility Monitor rechecks it continuously, and the PDF Checker covers documents. Every failure is mapped to the exact WCAG 2.2 criterion with guidance on fixing it.

Q: What is the most common color accessibility mistake?
A: Low-contrast text. The WebAIM Million 2026 report found text below WCAG 2 AA contrast thresholds on 83.9% of the top 1,000,000 home pages, making it the most commonly detected accessibility issue, with an average of 34 distinct instances per page. Typical causes are light gray text, placeholder text, and text over images. An automated scan such as EqualWeb's free Accessibility Checker finds these in seconds.

Q: Can the EqualWeb widget fix color contrast problems?
A: Partly. The Accessibility Widget's AI remediation automatically fixes 80+ common WCAG 2.2 issues through the browser, and its menu gives visitors user-side color options: the Visually Impaired profile strengthens contrast and enlarges text, and the Color-blind profile adjusts palettes so meaning never relies on color alone. Brand-level color decisions and issues automation cannot verify still need human work, which certified IAAP/CPWA experts handle through EqualWeb's Managed Compliance service.

Q: Does WCAG allow using color alone to show links or errors?
A: No. SC 1.4.1 Use of Color, Level A, requires that color is never the only visual means of conveying information. A link distinguished from body text only by color, or a form error indicated only by turning a field red, fails even when contrast ratios pass. Add a second cue such as an underline, icon or text label. EqualWeb's testing tools flag color-related failures as part of every WCAG 2.2 scan.

### Accessibility Crawler
URL: https://www.equalweb.com/platform/accessibility_crawler/

EqualWeb's Accessibility Crawler is a cloud-based Chrome extension that scans entire websites in real time for WCAG 2.2 AA - including password-protected pages, forms and multimedia - with results streamed to your dashboard.

What it is: A cloud-based Chrome extension for full-domain, real-time accessibility crawling.
Who it's for: Dev and QA teams that need to scan whole sites, including authenticated areas single-page tools can't reach.
What it solves: Performs domain-wide WCAG 2.2 scans - including password-protected pages, forms and media - with no setup or coding, and feeds results into the EqualWeb dashboard.

Features:
- Full domain-wide WCAG 2.2 AA crawl
- Scans password-protected pages, forms & media
- Cloud-based Chrome extension
- Real-time results in your dashboard
- No setup or coding


Q: What is a web accessibility crawler?
A: A crawler scans an entire website - not just one page - for accessibility issues. EqualWeb's Accessibility Crawler is a cloud-based Chrome extension that crawls full domains in real time against WCAG 2.2 AA, including password-protected pages.

Q: Can it scan password-protected or logged-in pages?
A: Yes. Because it runs as a Chrome extension in your authenticated session, EqualWeb's Crawler can scan password-protected pages, forms and multimedia that single-page tools can't reach.

Q: Do I need to install or code anything?
A: Just add the EqualWeb Accessibility Crawler extension to Chrome and log in - no code or setup. Results stream into your EqualWeb dashboard automatically.

Q: How is the Crawler different from the Monitor?
A: The Crawler runs on-demand, full-domain scans from your browser; the Monitor runs scheduled, continuous cloud scans with a live compliance score. Many teams use both.

## Accessibility Widget integrations - install guides

The EqualWeb accessibility widget installs with one line of JavaScript on any platform. Step-by-step guides:

### Install EqualWeb on WordPress
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/wordpress.html

Install the EqualWeb accessibility widget on WordPress in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any WordPress site.

1. On the menu, choose "Plugins" -> "Add New"
2. Search for the plugin - "Insert Headers and Footers", and install it, wait until the installation is completed, and an "Activate" button will appear, click it.
3. On the Plugin, simply copy paste your accessibility code to the footer area and save the changes.

### Install EqualWeb on Shopify
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/shopify.html

Install the EqualWeb accessibility widget on Shopify in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Shopify site.

1. At the bottom sidebar, choose "Online store", and then click on "Themes".
2. Next, click "Action" -> "Edit Code".
3. Choose "Theme.liquid", scroll down to the end of the code, and paste the EqualWeb implementation code above the </body> tag.

### Install EqualWeb on Wix
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/wix.html

Install the EqualWeb accessibility widget on Wix in minutes - 7 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Wix site.

1. Go to "Settings" in your site's dashboard.
2. Click the "Custom Code" tab under "Advanced Settings".
3. Click + "Add Custom Code" at the top right.
4. Paste the code snippet in the text field.
5. Choose a name for your code.
6. Choose the "Load Code Once" option from the select box.
7. Place the code at the body end.

### Install EqualWeb on WooCommerce
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/woocommerce.html

Install the EqualWeb accessibility widget on WooCommerce in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any WooCommerce site.

1. Get the Script - Sign up at EqualWeb.com and copy your unique JavaScript embed code.
2. Add Script to Site - Install and activate the plugin "Insert Headers and Footers", go to Settings -> Insert Headers and Footers, paste the script into the Footer section, and save changes.
3. Done! Visit your site to see the EqualWeb widget.

### Install EqualWeb on Squarespace
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/squarespace.html

Install the EqualWeb accessibility widget on Squarespace in minutes - 2 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Squarespace site.

1. Enter your Squarespace admin page and open: Settings > Advanced > Code Injection
2. Paste your EqualWeb code into the "FOOTER" space in Squarespace Code Injection

### Install EqualWeb on Webflow
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/webflow.html

Install the EqualWeb accessibility widget on Webflow in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Webflow site.

1. Go to "Project settings"
2. Press on the "Custom code" button
3. Place the code in the Footer code section, and save the changes.

### Install EqualWeb on HubSpot
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/hubspot.html

Install the EqualWeb accessibility widget on HubSpot in minutes - 4 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any HubSpot site.

1. Access your HubSpot dashboard and navigate to the "Marketing" section in the upper menu. Click on "Website Pages" from the available options.
2. In the list of sites, find the site you want to update, and then click on the "Settings" icon located in the upper right menu.
3. Within the "Settings" section, locate the "Templates" tab and proceed to the "Site Footer HTML" block. Here, paste the code snippet you downloaded from EqualWeb's platform.
4. After pasting the code, click on "Save," and the EqualWeb accessibility script will now be integrated into your chosen website.

### Install EqualWeb on Google Tag Manager
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/google-tag-manager.html

Install the EqualWeb accessibility widget on Google Tag Manager in minutes - 10 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any site via Google Tag Manager.

1. Login to your user at Google Tag Manager.
2. In the side menu, click the option "Tags".
3. Click on the "New" button, and choose the first option - "Tag configuration".
4. Select the option "Custom HTML" that's located at the bottom of the tags section.
5. Edit the tag name to - "EqualWeb".
6. Paste our accessibility code inside.
7. Click the "Triggering" button that's located below the code area. In the new window that appears, select the option "All pages". This selection will bring you back to the previous screen.
8. Click the "Save" button and save your tag.
9. After the tag has been saved, go to the main page of your user, and click the "Submit" button (top right of the screen).
10. At the new screen that's loaded, in the "Version name" section, enter "EqualWeb Added", and click the "Publish" button at the top right corner.

### Install EqualWeb on BigCommerce
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/bigcommerce.html

Install the EqualWeb accessibility widget on BigCommerce in minutes - 9 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any BigCommerce site.

1. At your BigCommerce dashboard, click on "Storefront".
2. Click on "Script Manager".
3. At the page opened, press on "Create a script".
4. Add a name to the script - "EqualWeb".
5. Mark the "Footer" option under the "Location on page" section.
6. Mark "All pages" under "Select pages where scripts will be added".
7. Change "Script type" to "Script".
8. Paste our code.
9. Click "Save".

### Install EqualWeb on Duda
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/duda.html

Install the EqualWeb accessibility widget on Duda in minutes - 4 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Duda site.

1. Click "Settings" in the left side menu.
2. Select "Header HTML".
3. Paste EqualWeb script inside of the text area.
4. Click "Save" button.

### Install EqualWeb on Joomla
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/joomla.html

Install the EqualWeb accessibility widget on Joomla in minutes - 8 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Joomla site.

1. Click here to download our plugin (https://login.equalweb.com/plugin/equalwebForJoomla.zip)
2. In order to implement the plugin, on the menu, click on - Extensions -> Extension Manager -> Install.
3. Inside the Component installation page, click on "Upload Package File".
4. Click "Install", and choose our plugin from stage one.
5. After the plugin is installed, click once again on the top menu, click on - Extensions -> Plugins, and search for "equalwebForJoomla".
6. Enter the result that you received, change the status to - "Enabled".
7. Paste EqualWeb code that was sent to you inside the code area that opened up.
8. Click - "Save" to save your changes.

### Install EqualWeb on Drupal
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/drupal.html

Install the EqualWeb accessibility widget on Drupal in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Drupal site.

1. Copy your EqualWeb installation code from your account.
2. Add the code to your theme so it loads on every page - paste it just before the closing body tag in your theme's html.html.twig template, or use a script-injector module such as Asset Injector and paste the code there.
3. Clear Drupal's caches (Configuration -> Performance -> Clear all caches) and reload your site - the widget appears on every page.

### Install EqualWeb on Magento
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/magento.html

Install the EqualWeb accessibility widget on Magento in minutes - 7 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Magento site.

1. Go to the left-hand menu on your Magento dashboard and select "Content." Then, under the "Design" submenu header, click on "Configuration."
2. Once you're on the configuration page, find the store you want to make changes to and click on the "Edit" link.
3. Scroll down the page to the "Other Settings" menu, and open the "Footer" section, then paste EqualWeb's accessibility code into the "Miscellaneous HTML" text box.
4. Press "Save Configuration" at the top right corner.
5. Many times you will be required to clear your store cache; you can do so easily by selecting the "System" button from the left menu, and then, under "Tools", press the "Cache Management" button.
6. In the new page, press the "Flush Magento Cache" button at the top right corner of the page.
7. That's it, EqualWeb is now implemented on your website! Don't forget to publish.

### Install EqualWeb on PrestaShop
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/prestashop.html

Install the EqualWeb accessibility widget on PrestaShop in minutes - 7 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any PrestaShop site.

1. Obtain the EqualWeb Script - Visit EqualWeb's official website and sign up for their accessibility widget service. After registration, you will receive a JavaScript code snippet that is unique to your website.
2. Access Your PrestaShop Admin Panel - Log in to your PrestaShop Admin Panel. From the admin dashboard, navigate to the Themes section.
3. Edit Your Theme - In the Themes section, click on Advanced Settings or find the Theme Editor option. Access the theme's files, specifically the header.tpl or footer.tpl file, depending on where you want to insert the script.
4. Insert the EqualWeb Script - Open the header.tpl (or footer.tpl) file in the theme editor. Inside the <head> section of the template file, paste the EqualWeb JavaScript snippet just before the closing </head> tag.
5. Save and Publish the Changes - After pasting the script, click Save to save your changes. Clear the cache in PrestaShop (under Advanced Parameters > Performance) to ensure the changes take effect on the live website.
6. Verify the Installation - Visit your website in a browser. Check for the EqualWeb accessibility widget (typically appearing as an icon in the corner of the page). Click on the widget to test the accessibility features, ensuring everything works properly.
7. Maintain Accessibility Compliance - Keep the EqualWeb widget updated to comply with accessibility standards like WCAG, ADA, and Section 508. Monitor feedback from users to ensure the accessibility features are effective.

### Install EqualWeb on OpenCart
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/opencart.html

Install the EqualWeb accessibility widget on OpenCart in minutes - 4 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any OpenCart site.

1. Get the Script - Sign up at EqualWeb.com and copy your unique JavaScript code.
2. Edit Footer File - Open catalog/view/theme/YOUR_THEME/template/common/footer.twig and paste the script just before </body>.
3. Clear Cache - In admin, go to Dashboard -> Developer Settings, then click Refresh and Clear cache.
4. Check Site - Reload your site to see the EqualWeb widget.

### Install EqualWeb on GoDaddy
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/godaddy.html

Install the EqualWeb accessibility widget on GoDaddy in minutes - 7 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any GoDaddy site.

1. Enter to your website builder
2. Navigate to "Edit Site"
3. Click on the hamburger menu and choose "Site Settings"
4. Click the "Site-wide Code" tab in the new window opened.
5. Paste your EqualWeb script into "Code to put before closing tag (all pages)"
6. Click "OK".
7. Click the "Publish" button at the top of the page

### Install EqualWeb on Weebly
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/weebly.html

Install the EqualWeb accessibility widget on Weebly in minutes - 6 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Weebly site.

1. Log in to your Weebly account and choose the wanted site from your site list.
2. Click "Edit site".
3. Under the "Theme" tab, press "Edit HTML / CSS", on the bottom left.
4. Under "Header Type" click on the first page layout, and scroll all the way down, until you find the </body> tag.
5. Paste the EqualWeb code just above it.
6. Repeat this process for the rest of the pages in your site, under "Header Type".

### Install EqualWeb on Jimdo
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/jimdo.html

Install the EqualWeb accessibility widget on Jimdo in minutes - 4 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Jimdo site.

1. Go to your Jimdo site management.
2. Navigate to: Menu -> Settings -> Edit Head
3. Paste EqualWeb's code inside.
4. And we are done, EqualWeb system should now be implemented on your website.

### Install EqualWeb on Lightspeed
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/lightspeed.html

Install the EqualWeb accessibility widget on Lightspeed in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Lightspeed site.

1. Go to your shop, and navigate in to - Design -> Theme Editor -> custom.rain file inside of the layout section.
2. Scroll down until the </body> tag, and paste EqualWeb's code right above it.
3. Repeat the 2nd step inside of the fixed.rain file.

### Install EqualWeb on SharePoint
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/sharepoint.html

Install the EqualWeb accessibility widget on SharePoint in minutes - 5 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any SharePoint site.

1. Add a Content Editor web part to the page.
2. (Click on the link to add new content, if you are using a web part page.)
3. Click on the Edit Source button in the ribbon.
4. Paste your JavaScript code in the HTML source.
5. Apply and save the page.

### Install EqualWeb on Strikingly
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/strikingly.html

Install the EqualWeb accessibility widget on Strikingly in minutes - 6 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Strikingly site.

1. Go to your site editor.
2. Add a new section.
3. Select "App Store & HTML" from the section list.
4. Once a new section is created - click "Edit".
5. Select from the app list "HTML" app.
6. Copy and paste EqualWeb implementation code, hit "Save" when you're done!

### Install EqualWeb on Ning
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/ning.html

Install the EqualWeb accessibility widget on Ning in minutes - 4 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Ning site.

1. Go to your site editor.
2. Open Custom Code in the Social Site Manager.
3. Copy and paste EqualWeb implementation code.
4. Click Save, then click Publish to save your changes and publish them on your live site.

### Install EqualWeb on Webs
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/webs.html

Install the EqualWeb accessibility widget on Webs in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Webs site.

1. Get the Script - Sign up at EqualWeb.com and copy your unique JavaScript embed code.
2. Add Script to Webs - Log into Webs and open your site editor. Add a new Custom HTML module to your page or site footer. Paste the EqualWeb script into the box. Save and publish your site.
3. Done! - Visit your site to see the EqualWeb widget.

### Install EqualWeb on Zen Cart
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/zen-cart.html

Install the EqualWeb accessibility widget on Zen Cart in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Zen Cart site.

1. Copy your EqualWeb installation code from your account.
2. Create a file named jscript_equalweb.php inside includes/templates/YOUR_TEMPLATE/jscript/ and paste the code into it - Zen Cart automatically loads every jscript_ file in that folder on all pages of your shop.
3. Upload the file to your server and reload your shop - the widget appears on every page.

### Install EqualWeb on osCommerce
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/oscommerce.html

Install the EqualWeb accessibility widget on osCommerce in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any osCommerce site.

1. Get the Script - Sign up at EqualWeb.com and copy your unique JavaScript embed code.
2. Edit Footer File - Open includes/footer.php in your osCommerce theme. Paste the script just before the </body> tag in your main template file (e.g., index.php). Save the file.
3. Done! - Reload your site to see the EqualWeb widget.

### Install EqualWeb on Contao
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/contao.html

Install the EqualWeb accessibility widget on Contao in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Contao site.

1. Get the Script - Sign up at EqualWeb.com and copy your unique JavaScript embed code.
2. Add Script in Template - Go to Templates in the Contao backend, edit fe_page.html5 (or your custom layout template), paste the script just before </body>, then save and apply the template.
3. Done! - Clear cache and reload your site to see the widget.

### Install EqualWeb on Concrete5
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/concrete5.html

Install the EqualWeb accessibility widget on Concrete5 in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Concrete5 site.

1. Get the Script: Sign up at EqualWeb.com and copy your unique JavaScript embed code.
2. Add Script to Theme: Go to application/themes/YOUR_THEME/elements/footer.php, paste the script just before </body>, and save the file.
3. Clear Cache & Check: In Dashboard -> System & Settings -> Optimization -> Clear Cache, then visit your site to see the widget.

### Install EqualWeb on X-Cart
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/x-cart.html

Install the EqualWeb accessibility widget on X-Cart in minutes - 4 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any X-Cart site.

1. Get the Script - Sign up at EqualWeb.com and copy your unique JavaScript embed code.
2. Edit Template - Go to skins/YOUR_SKIN/customer/header.twig or footer.twig and paste the script just before </body>.
3. Clear Cache - In Admin Panel -> Tools -> Cache Management, click Re-deploy the store.
4. Done! Reload your site to see the EqualWeb widget.

### Install EqualWeb on Ubercart
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/ubercart.html

Install the EqualWeb accessibility widget on Ubercart in minutes - 4 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Ubercart site.

1. Get the Script - Sign up at EqualWeb.com and copy your unique JavaScript embed code.
2. Add Script to Drupal - Go to Appearance -> Theme -> Edit, edit page.tpl.php or html.tpl.php, and paste the script just before </body>.
3. Clear Cache - Go to Configuration -> Performance and click Clear all caches.
4. Done! Reload your site to see the EqualWeb widget.

### Install EqualWeb on VirtueMart
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/virtuemart.html

Install the EqualWeb accessibility widget on VirtueMart in minutes - 4 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any VirtueMart site.

1. Get the Script from EqualWeb - Sign up at EqualWeb.com and copy your personal JavaScript embed code.
2. Log into Joomla Admin - Go to System -> Site Template Styles, open your active template -> Edit index.php.
3. Paste the Script - Add the EqualWeb code just before the closing </body> tag and save the file.
4. Clear Cache & Check Site - Refresh your site; the EqualWeb widget should appear.

### Install EqualWeb on 1&1 IONOS
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/ionos.html

Install the EqualWeb accessibility widget on 1&1 IONOS in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any 1&1 IONOS site.

1. Get the Script - Sign up at EqualWeb.com and copy your unique JavaScript embed code.
2. Add Script to Website - Log in to IONOS and open your site in the editor. Add a Custom HTML element to the footer or global section, paste the script inside the HTML box, then save and publish your site.
3. Done! Refresh your site to see the EqualWeb widget.

### Install EqualWeb on Ucraft
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/ucraft.html

Install the EqualWeb accessibility widget on Ucraft in minutes - 6 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Ucraft site.

1. Obtain the EqualWeb Script - Visit EqualWeb's official website and sign up for their accessibility widget service. After registration, you will receive a JavaScript code snippet unique to your website.
2. Access Your Ucraft Admin Panel - Log in to your Ucraft Admin Panel. Navigate to Settings from the left-hand sidebar.
3. Add the EqualWeb Script - Under Settings, select Tracking & Analytics. Scroll down to the Custom Code section. Paste the EqualWeb JavaScript snippet into the Header Code box (see example image).
4. Save and Publish the Changes - After pasting the script, click on Save to save the changes. Publish your site to make the accessibility widget visible on the live site.
5. Verify the Installation - Visit your website in a browser. Look for the EqualWeb accessibility widget (usually appearing as an icon in the corner of the page). Click on the widget to test the accessibility features.
6. Maintain Accessibility Compliance - Keep the EqualWeb widget updated to comply with accessibility standards like WCAG, ADA, and Section 508. Monitor feedback from users to ensure the accessibility features are working as intended.

### Install EqualWeb on HostGator
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/hostgator.html

Install the EqualWeb accessibility widget on HostGator in minutes - 8 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any HostGator site.

1. Obtain the EqualWeb Script - Visit EqualWeb's official website and sign up for their accessibility widget service. After registration, you will receive a JavaScript code snippet that is unique to your website.
2. Log in to Your HostGator Account - Go to HostGator's cPanel and log in using your account credentials.
3. Access Your Website's Files - In the cPanel, open the File Manager under the "Files" section. Navigate to the root directory of your website (usually public_html or a subfolder depending on your setup).
4. Edit Your Website's HTML or Template File - Find the index.html or header.php file, or the template file that loads the common HTML <head> section for your site. Right-click on the file and choose Edit.
5. Insert the EqualWeb Script - Inside the <head> section of your HTML code or template, paste the EqualWeb JavaScript snippet just before the closing </head> tag (see example screenshot).
6. Save and Publish the Changes - After pasting the script, click Save Changes to save the file. If using a CMS, you may need to update or publish your changes depending on the platform.
7. Verify the Installation - Visit your website in a browser. Look for the EqualWeb accessibility widget (usually appearing as an icon in the corner of the page) and click on it to test the accessibility features.
8. Maintain Accessibility Compliance - Keep the EqualWeb widget updated to comply with accessibility standards like WCAG, ADA, and Section 508. Monitor feedback from users to ensure the accessibility features are working as intended.

### Install EqualWeb on PHP
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/php.html

Install the EqualWeb accessibility widget on PHP in minutes - 6 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any PHP site.

1. Obtain the EqualWeb Script - Visit EqualWeb's official website and sign up for their accessibility widget. After registration, you will receive a JavaScript code snippet unique to your website.
2. Access Your PHP Website's Files - Open your PHP website files using your preferred code editor (e.g., VS Code, Sublime Text, or PHPStorm). Locate the header.php or index.php file, or any other file that loads the common HTML header for your pages.
3. Insert the EqualWeb Script - Inside the <head> section of your HTML code, paste the EqualWeb JavaScript snippet just before the closing </head> tag.
4. Save and Upload the Changes - After pasting the script, save the changes to the file(s). If your website is live, upload the updated files to your web server using an FTP client or through your hosting control panel.
5. Verify the Installation - Visit your website in a browser. Look for the EqualWeb accessibility widget (usually appearing as an icon in the corner of the page). Click on the widget to test the accessibility features, ensuring everything is working properly.
6. Maintain Accessibility Compliance - Keep the EqualWeb widget updated to comply with accessibility standards such as WCAG, ADA, and Section 508. Collect feedback from users with disabilities to ensure the accessibility features are effective.

### Install EqualWeb on Microsoft .NET
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/dotnet.html

Install the EqualWeb accessibility widget on Microsoft .NET in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Microsoft .NET site.

1. Sign up for EqualWeb (or log in) and copy your one-line installation code.
2. Open your site's master layout - for example _Layout.cshtml (ASP.NET Core / MVC) or Site.Master (Web Forms).
3. Paste the code just before the closing body tag, save and deploy - the widget appears on every page that uses the layout.

### Install EqualWeb on HTML
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/html.html

Install the EqualWeb accessibility widget on HTML in minutes - 3 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any HTML site.

1. In order to embed our code in a system that doesn't have an installation guide, all you need to look for is the place where you put your JavaScript code.
2. Embed the EqualWeb code above the closing </body> tag on all of the site pages.
3. In case you have inner iFrames on your website, you should implement the code in there as well.

### Install EqualWeb on bbPress
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/bbpress.html

Install the EqualWeb accessibility widget on bbPress in minutes - 6 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any bbPress site.

1. Obtain the EqualWeb Script - Once registered, you will receive a JavaScript code snippet unique to your website.
2. Log in to Your WordPress Admin Panel - Go to yourwebsite.com/wp-admin and log in. In the Dashboard, ensure bbPress is installed and active.
3. Add the EqualWeb Script to Your Theme - Navigate to Appearance > Theme File Editor. In the Theme Editor, locate and open the header.php file. Paste the EqualWeb JavaScript snippet just before the closing </head> tag. Click Update File to save the changes.
4. Add the Script Using a Plugin (Alternative Method) - If you prefer not to edit theme files: Go to Plugins > Add New and install a plugin like Insert Headers and Footers. Activate the plugin and navigate to Settings > Insert Headers and Footers. Paste the EqualWeb JavaScript snippet in the Scripts in Header section. Click Save to apply the changes.
5. Verify the Installation - Visit your bbPress forum and refresh the page. The EqualWeb accessibility widget should appear in the corner of your site. Click the widget to test the accessibility features.
6. Maintain Accessibility Compliance - Regularly update the widget to meet WCAG, ADA, and Section 508 standards. Monitor user feedback to ensure accessibility improvements.

### Install EqualWeb on Blogger
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/blogger.html

Install the EqualWeb accessibility widget on Blogger in minutes - 6 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Blogger site.

1. Obtain the EqualWeb Script: Visit EqualWeb's official website and sign up for their accessibility widget service. Once registered, you will receive a unique JavaScript code snippet for your website.
2. Log in to Your Blogger Account: Go to Blogger (blogger.com) and log in with your Google account. In the Dashboard, select the blog where you want to add the accessibility widget.
3. Access the Theme Editor: In the left-hand menu, click on Theme. Click on the Customize dropdown and choose Edit HTML.
4. Insert the EqualWeb Script: Inside the HTML editor, locate the <head> section. Paste the EqualWeb JavaScript snippet just before the closing </head> tag.
5. Save and Apply Changes: Click on Save in the top-right corner. Return to your blog's homepage and refresh the page.
6. Verify the Installation: Check for the EqualWeb accessibility widget on your blog. The widget should appear as an icon in the corner of the page. Click on it to test the accessibility features.

### Install EqualWeb on Tumblr
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/tumblr.html

Install the EqualWeb accessibility widget on Tumblr in minutes - 7 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Tumblr site.

1. Obtain the EqualWeb Script - Sign up for their service to receive the unique JavaScript code snippet tailored for your website.
2. Access Your Tumblr Account - Log in to your Tumblr account. Click on the Account icon (shaped like a person) at the top right corner. Select Settings from the dropdown menu.
3. Select Your Blog - Under the Blogs section on the right, choose the specific blog where you want to add the accessibility widget.
4. Edit Your Theme - In the selected blog's settings, click on Edit theme. This will open the theme editor, allowing you to customize your blog's appearance and functionality.
5. Insert the EqualWeb Script - Click on Edit HTML to access your theme's HTML code. Locate the <head> section of the HTML, typically near the top of the code. Paste the EqualWeb JavaScript code snippet you obtained earlier just before the closing </head> tag.
6. Save Your Changes - After pasting the script, click on Update Preview to see a preview of the changes. If everything looks good, click on Save to apply the changes to your live site.
7. Verify the Installation - Navigate to your Tumblr blog's main page. You should now see the EqualWeb accessibility widget icon, typically positioned at the corner of the screen. Clicking on this icon will reveal various accessibility tools and features for your visitors.

### Install EqualWeb on Volusion
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/volusion.html

Install the EqualWeb accessibility widget on Volusion in minutes - 5 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Volusion site.

1. Log in to your Admin area.
2. Go to the "Marketing" tab - and choose SEO
3. On the left, select the "Default values tab".
4. Paste EqualWeb code into the "Globally Appended Meta Tags Fields"
5. Press "Save".

### Install EqualWeb on Konimbo
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/konimbo.html

Install the EqualWeb accessibility widget on Konimbo in minutes - 4 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any Konimbo site.

1. Log in to the store interface, click on Hybrid.
2. Paste the JS code in body_html. When done, click on the "Save" button.
3. Once the code is saved you will see the accessibility button in mobile and desktop.
4. That's it - EqualWeb is now implemented on your website; allow up to 10 minutes for it to appear on the main domain.

### Install EqualWeb on AppDrag
URL: https://www.equalweb.com/platform/accessibility_widget/integrations/appdrag.html

Install the EqualWeb accessibility widget on AppDrag in minutes - 5 short steps add AI-powered WCAG 2.2, ADA and EAA remediation and 9 accessibility profiles to any AppDrag site.

1. Go to the EqualWeb Website, follow the guide there and obtain your free integration code, copy it, we will use it later in this tutorial.
2. Go to the dashboard and edit your project in the PageBuilder.
3. Click on Add Component and select a Source Code > Javascript Source Code embedded. From here you should drag & drop the Javascript source code element on your page; you should drop it in the footer area of your site - this way it will be replicated on all pages of your website!
4. Double click the component to open the source code editor and paste the EqualWeb integration code you copied in step 1.
5. Save your page and publish your website.

## PDF Accessibility Integrations - Free PDF Checker & AI remediation

EqualWeb PDF Accessibility scans every PDF in the systems organizations already use, scores each document 0-100 against 80+ PDF/UA and WCAG rules, prioritizes by legal exposure (required for service / public / internal / archive), and remediates in place - same URL, same sharing, no broken links. Accessibility checks are free within a daily quota; remediation is a paid action.

### Free PDF Checker for WordPress
URL: https://www.equalweb.com/platform/pdf_tools/integrations/wordpress.html

EqualWeb PDF Accessibility for WordPress - plugin that installs in your site. Automatic discovery of every PDF, a 0-100 accessibility score with a permanent report link, legal prioritization, and one-click AI remediation in place.

### Free PDF Checker for Drupal
URL: https://www.equalweb.com/platform/pdf_tools/integrations/drupal.html

EqualWeb PDF Accessibility for Drupal - module that installs in your site. Automatic discovery of every PDF, a 0-100 accessibility score with a permanent report link, legal prioritization, and one-click AI remediation in place.

### Free PDF Checker for Moodle & Open LMS
URL: https://www.equalweb.com/platform/pdf_tools/integrations/moodle.html

EqualWeb PDF Accessibility for Moodle & Open LMS - one admin plugin for both - supports Moodle 4.5 (LTS), 5.0, 5.1 and 5.2 including the 5.1 directory structure, and Open LMS which runs on Moodle. Automatic discovery of every PDF, a 0-100 accessibility score with a permanent report link, legal prioritization, and one-click AI remediation in place.

### Free PDF Checker for Shopify
URL: https://www.equalweb.com/platform/pdf_tools/integrations/shopify.html

EqualWeb PDF Accessibility for Shopify - embedded app in the store admin. Automatic discovery of every PDF, a 0-100 accessibility score with a permanent report link, legal prioritization, and one-click AI remediation in place.

### Free PDF Checker for SharePoint / Microsoft 365
URL: https://www.equalweb.com/platform/pdf_tools/integrations/sharepoint.html

EqualWeb PDF Accessibility for SharePoint / Microsoft 365 - Cloud Connect with a one-time admin consent - files appear in the EqualWeb dashboard. Automatic discovery of every PDF, a 0-100 accessibility score with a permanent report link, legal prioritization, and one-click AI remediation in place.

### Free PDF Checker for Google Drive / Workspace
URL: https://www.equalweb.com/platform/pdf_tools/integrations/google-drive.html

EqualWeb PDF Accessibility for Google Drive / Workspace - Cloud Connect via Google OAuth sign-in - files appear in the EqualWeb dashboard. Automatic discovery of every PDF, a 0-100 accessibility score with a permanent report link, legal prioritization, and one-click AI remediation in place.

### Free PDF Checker for Box
URL: https://www.equalweb.com/platform/pdf_tools/integrations/box.html

EqualWeb PDF Accessibility for Box - Cloud Connect via Box OAuth sign-in - files appear in the EqualWeb dashboard. Automatic discovery of every PDF, a 0-100 accessibility score with a permanent report link, legal prioritization, and one-click AI remediation in place.

### Free PDF Checker for Canvas LMS
URL: https://www.equalweb.com/platform/pdf_tools/integrations/canvas.html

EqualWeb PDF Accessibility for Canvas LMS - LTI 1.3 app registered in your Canvas admin, early access - nothing runs on your servers; the accessible copy is saved next to the original. Automatic discovery of every PDF, a 0-100 accessibility score with a permanent report link, legal prioritization, and one-click AI remediation in place.

### Cloud Connect
SharePoint / Microsoft 365 connects with a one-time admin consent; Google Drive / Workspace, OneDrive, Dropbox and Box connect with a two-click OAuth sign-in; S3-compatible storage (AWS S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Google Cloud Storage) connects with bucket-scoped access keys. Connected files appear in the EqualWeb dashboard (PDF Remediation - Cloud files) with the full pipeline; step-by-step connection instructions are built into the dashboard. [Shopify setup guide](https://www.equalweb.com/platform/pdf_tools/integrations/shopify-setup.html) covers the one-click app install with files-only scopes.

## Accessibility standards & regulations

### Web Content Accessibility Guidelines (WCAG) 2.2
URL: https://www.equalweb.com/platform/standards/wcag-2-2.html
Region: Global. Governing body: World Wide Web Consortium (W3C), through its Web Accessibility Initiative (WAI) and the Accessibility Guidelines Working Group (AG WG) In effect: October 5, 2023 (original W3C Recommendation); minor editorial update published December 12, 2024 (success criteria unchanged); also published as ISO/IEC 40500:2025 on October 21, 2025.

Web Content Accessibility Guidelines (WCAG) 2.2 is the current W3C Recommendation for making web content accessible to people with disabilities, first published on October 5, 2023, and subsequently adopted as ISO/IEC 40500:2025 on October 21, 2025. It defines 86 testable success criteria across three conformance levels (A, AA, AAA) organized under four core principles: Perceivable, Operable, Understandable, and Robust.

What it is: Web Content Accessibility Guidelines (WCAG) 2.2 is a globally recognized technical standard published by the World Wide Web Consortium (W3C) on October 5, 2023 (with a minor editorial update on December 12, 2024 that did not change any success criteria), specifying how to make digital content accessible to people with a wide range of disabilities, including visual, auditory, physical, cognitive, and neurological impairments. Building on WCAG 2.1, it adds nine new success criteria - with a focus on users with cognitive disabilities, low vision, and limited mobility - while removing one obsolete criterion (4.1.1 Parsing) and remaining fully backward compatible. In October 2025, WCAG 2.2 was formally adopted as the international standard ISO/IEC 40500:2025, reinforcing its status as the definitive global benchmark for web accessibility. The standard is organized around four principles - content must be Perceivable, Operable, Understandable, and Robust (POUR) - and offers 86 testable success criteria at Levels A, AA, and AAA.

Who must comply: WCAG 2.2 is a voluntary technical standard, but it is incorporated by reference into laws and regulations worldwide, making it effectively mandatory for broad categories of organizations. In the United States, the DOJ's ADA Title II final rule requires state and local governments to meet WCAG 2.1 Level AA (with WCAG 2.2 representing current best practice), while Section 508 of the Rehabilitation Act mandates WCAG 2.0 Level AA for federal agencies and their contractors and vendors. In the European Union, the European Accessibility Act (EAA), enforceable from June 28, 2025, and EN 301 549 reference WCAG 2.1 AA - and WCAG 2.2 is increasingly cited as the expected standard by regulators and courts. Private-sector businesses of all sizes face growing litigation risk under the ADA and comparable laws globally if their websites do not meet WCAG 2.2 Level AA.

Key requirements:
- Focus Not Obscured: When a user interface component receives keyboard focus, it must not be entirely hidden by author-created content such as sticky headers or cookie banners (SC 2.4.11, Level AA).
- Focus Appearance: Keyboard focus indicators must meet minimum size and contrast requirements so they are clearly visible to users with low vision (SC 2.4.13, Level AAA; SC 2.4.11 at AA).
- Dragging Movements: Any functionality that relies on a dragging gesture (e.g., sliders, drag-and-drop) must also be operable with a single pointer without dragging, unless dragging is essential (SC 2.5.7, Level AA).
- Target Size (Minimum): Interactive targets such as buttons and links must be at least 24x24 CSS pixels, or adequate spacing must exist between smaller targets to prevent accidental activation (SC 2.5.8, Level AA).
- Consistent Help: If a web page provides a help mechanism - such as a phone number, chat, or contact link - it must appear in the same relative location across pages (SC 3.2.6, Level A).
- Redundant Entry: Information users have previously entered in a process must not be requested again in the same session, unless re-entry is essential or required for security (SC 3.3.7, Level A).
- Accessible Authentication: Authentication processes must not require users to solve a cognitive function test, such as a CAPTCHA, unless an alternative is provided or the test involves object recognition and not memorization (SC 3.3.8, Level AA).

Key dates:
- October 5, 2023: WCAG 2.2 published as a W3C Recommendation - the definitive effective date of the standard globally.
- June 28, 2025: European Accessibility Act (EAA) enforcement begins in EU member states; EN 301 549 (which references WCAG 2.1 AA, with 2.2 as best practice) becomes mandatory for covered digital products and services.
- April 26, 2027: Extended DOJ Title II ADA compliance deadline for U.S. state and local governments serving a population of 50,000 or more (WCAG 2.1 AA required; extended from the original April 24, 2026 deadline by an April 2026 Interim Final Rule).
- April 26, 2028: Extended DOJ Title II ADA compliance deadline for U.S. state and local governments serving fewer than 50,000 people and for special district governments (WCAG 2.1 AA required).

Penalties & enforcement: WCAG 2.2 itself carries no direct penalties - enforcement flows through the laws that incorporate it. In the United States, ADA non-compliance can result in federal civil rights lawsuits, DOJ investigations, consent decrees, and damages; federal web accessibility lawsuits number in the thousands annually (approximately 2,452 federal filings were recorded in 2024, according to ADA Title III tracking data), with courts increasingly citing WCAG 2.2 as the de facto standard. In the European Union, the EAA empowers national regulators to impose country-specific fines for non-compliant digital products and services; penalty structures vary by member state - Germany's maximum is €100,000 per violation, Italy's ranges from €30,000 to €1,000,000 depending on severity, and Spain also reaches €1,000,000 for the most serious violations - plus potential market withdrawal orders. Organizations procuring ICT for the U.S. federal government that violate Section 508 face contract disputes, agency complaints to the U.S. Access Board, and reputational harm.

Relation to WCAG: WCAG 2.2 is the standard itself - the current version of the Web Content Accessibility Guidelines, superseding WCAG 2.1 (published 2018) and WCAG 2.0 (published 2008). It is fully backward compatible: a site conforming to WCAG 2.2 Level AA also satisfies WCAG 2.1 and 2.0 at the same level. Many regulations still formally reference WCAG 2.1 or 2.0 (e.g., ADA Title II final rule at WCAG 2.1 AA; Section 508 at WCAG 2.0 AA), but WCAG 2.2 Level AA is widely treated by legal counsel, courts, and accessibility professionals as the current minimum best practice for defensible compliance.

How EqualWeb helps: EqualWeb's AI Accessibility Widget can be deployed with a single line of code and automatically remediates up to 95% of common WCAG 2.2 issues - depending on how the site is built - in real time on the client side - including focus management, color contrast adjustments, and accessible interaction profiles - helping organizations make measurable progress toward Level AA conformance. The widget alone does not make a site conformant; issues requiring code-level or structural remediation (such as full Accessible Authentication or Focus Appearance compliance) need expert intervention. For those remaining issues, EqualWeb's Managed Compliance service pairs clients with IAAP/CPWA-certified experts who audit, remediate, monitor, and certify toward full WCAG 2.2 Level AA conformance, delivering a signed Accessibility Compliance Certificate, a VPAT/Accessibility Conformance Report, and a supporting evidence pack. EqualWeb's Continuous Monitoring provides a live 0-100 compliance score with regression alerts, so organizations can track conformance against WCAG 2.2 success criteria over time and catch regressions before they create legal exposure. The Accessibility Testing suite - including an automated checker, site crawler, and ongoing monitor - maps findings directly to WCAG 2.2 success criteria, giving development and compliance teams actionable remediation priorities. For organizations with PDF-heavy workflows, EqualWeb's PDF Tools check and remediate documents against PDF/UA and Section 508 standards, addressing a category of content that WCAG 2.2 explicitly extends to through WCAG2ICT guidance.

Q: What is WCAG 2.2 and why does it matter?
A: WCAG 2.2 is the October 2023 W3C Recommendation defining technical requirements for accessible web content, now also published as ISO/IEC 40500:2025. It matters because it is the benchmark referenced in ADA litigation, EU accessibility law (via EN 301 549 and the EAA), and procurement requirements globally. Failing to meet WCAG 2.2 Level AA exposes organizations to lawsuits, regulatory action, and exclusion from government contracts.

Q: Who is required to comply with WCAG 2.2?
A: No law currently mandates WCAG 2.2 by version number, but it is the de facto compliance target. U.S. state and local governments must meet WCAG 2.1 AA under the DOJ's ADA Title II rule; federal agencies and contractors must meet WCAG 2.0 AA under Section 508. In the EU, digital products and services covered by the EAA must meet EN 301 549, which references WCAG 2.1 AA. Private-sector businesses face ADA litigation risk if their sites do not meet WCAG 2.2 Level AA.

Q: What are the new success criteria in WCAG 2.2 compared to 2.1?
A: WCAG 2.2 adds nine new success criteria: Focus Not Obscured (Minimum and Enhanced), Focus Appearance, Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry, and Accessible Authentication (Minimum and Enhanced). It also removes SC 4.1.1 Parsing, which had become redundant due to modern browser behavior. These additions particularly benefit users with cognitive disabilities, low vision, and motor impairments.

Q: What conformance level should organizations target in WCAG 2.2?
A: Level AA is the universally expected conformance target for legal compliance and best practice. Level A represents the minimum baseline but is insufficient for most regulatory purposes. Level AAA is aspirational - it includes criteria that cannot be met for all content types and is not required by any major law. Organizations aiming for defensible compliance under the ADA, EAA, or Section 508 should target WCAG 2.2 Level AA.

Q: What is the deadline for WCAG 2.2 compliance?
A: WCAG 2.2 itself does not set deadlines - compliance timelines are set by the laws that reference it. For U.S. state and local governments under the DOJ's revised ADA Title II rule, entities serving populations of 50,000 or more must comply by April 26, 2027, and smaller entities and special districts by April 26, 2028. The EAA became enforceable across EU member states from June 28, 2025. Private-sector organizations under the ADA face no fixed statutory deadline but are exposed to litigation at any time.

### PDF/UA (ISO 14289)
URL: https://www.equalweb.com/platform/standards/pdf-ua.html
Region: Global. Governing body: International Organization for Standardization (ISO), under Technical Committee ISO TC171 SC2 WG9, with active participation from the PDF Association's PDF/UA Technical Working Group In effect: ISO 14289-1 first published July 2012; current revision ISO 14289-1:2014; ISO 14289-2 (PDF/UA-2) published March 2024.

PDF/UA (ISO 14289) is the international standard that defines the technical requirements for creating universally accessible PDF documents, specifying how tagging, structure, reading order, and metadata must be implemented so that PDF files can be reliably navigated and consumed by assistive technologies. Published by ISO under the designation ISO 14289, it is the only formal, file-format-specific accessibility standard for PDF and exists in two active versions: PDF/UA-1 (ISO 14289-1:2014, based on PDF 1.7) and PDF/UA-2 (ISO 14289-2:2024, based on PDF 2.0).

What it is: PDF/UA - short for PDF/Universal Accessibility - is an ISO international standard (ISO 14289) that prescribes the exact technical requirements a PDF file, a PDF processor, and assistive technology must each meet to ensure that people with disabilities can access and navigate PDF content. Unlike WCAG, which defines accessibility principles at a content level across all digital formats, PDF/UA translates those principles into precise, file-format-specific rules: mandatory tagged structure trees, logical reading order, Unicode font mapping, and machine-readable metadata. The current family includes PDF/UA-1 (ISO 14289-1:2014, built on PDF 1.7 / ISO 32000-1) and PDF/UA-2 (ISO 14289-2:2024, built on PDF 2.0 / ISO 32000-2), with the latter adding MathML support, expanded annotation requirements, and new structure element types. PDF/UA is maintained by ISO TC171 SC2 WG9 and the PDF Association's PDF/UA Technical Working Group.

Who must comply: PDF/UA applies in practice to any organization that creates, publishes, or distributes PDF documents to the public or to employees - including government agencies, educational institutions, financial services firms, healthcare providers, retailers, and technology vendors. In the United States, federal agencies and their contractors must produce accessible PDFs under Section 508 of the Rehabilitation Act, and state and local governments must meet WCAG 2.1 Level AA under ADA Title II (deadlines vary by entity size following a DOJ Interim Final Rule issued April 2026). In the European Union, the European Accessibility Act (EAA), enforceable from June 28, 2025 for new products and services, requires businesses operating in the EU market to ensure customer-facing digital content - including PDFs such as invoices, contracts, statements, and manuals - meets accessibility standards harmonized through EN 301 549; existing services have a transition period until June 28, 2030. Privately-held organizations subject to ADA Title III, and any company with a federal nexus through contracts or grants, also face exposure when publishing inaccessible PDFs.

Key requirements:
- All meaningful content must be fully tagged using a logical structure tree that correctly represents semantic roles - headings, paragraphs, lists, tables, figures, and form fields.
- Content must be presented in a logical reading order defined by the structure tree, independent of the visual layout order on the page.
- All non-text content (images, charts, diagrams) must carry descriptive alternative text; purely decorative elements must be marked as artifacts to be ignored by screen readers.
- All fonts must be embedded in the file and mapped to Unicode character codes so that text can be reliably extracted and rendered by assistive technologies.
- Document security settings must not block assistive technology from accessing text, structure, or metadata.
- The document's natural language must be declared in the document metadata (XMP), enabling screen readers to apply correct pronunciation and language rules.
- Conforming PDF processors must fully process tags and artifacts, support document navigation (bookmarks, headings), and expose document metadata to assistive technologies.

Key dates:
- April 26, 2027: U.S. state and local governments serving populations of 50,000 or more must meet WCAG 2.1 Level AA under ADA Title II - covering all web and electronic document content including PDFs. This deadline was extended from April 24, 2026 by a DOJ Interim Final Rule effective April 20, 2026.
- April 26, 2028: U.S. smaller public entities (populations under 50,000) and special district governments must achieve the same ADA Title II WCAG 2.1 Level AA compliance, including PDFs. This deadline was extended from April 26, 2027 by the same DOJ Interim Final Rule.
- June 28, 2025: European Accessibility Act (EAA) became enforceable across all 27 EU Member States for new products and newly launched or updated services, requiring accessible digital content including customer-facing PDFs. Existing services already on the market before this date have a transition period until June 28, 2030.

Penalties & enforcement: PDF/UA itself carries no direct penalties - it is a technical standard, not a law - but inaccessible PDFs create significant legal exposure under the laws that reference or incorporate its principles. In the United States, ADA violations can result in DOJ enforcement actions with civil penalties up to $118,225 for a first violation and $236,451 for subsequent violations (2025 inflation-adjusted figures under 28 CFR Part 85), as well as private lawsuits and settlements that have reached six figures; under Section 508, federal agencies and contractors face contractual consequences including payment withholding, contract termination, and exclusion from future procurement. In the European Union, the EAA authorizes member-state regulators to impose fines; penalty amounts vary by country and can reach €100,000 or more depending on jurisdiction. California's Unruh Civil Rights Act allows $4,000 per inaccessible instance for state-law violations.

Relation to WCAG: PDF/UA is designed as a companion standard to WCAG and explicitly provides a means of making PDF files that conform to the W3C's Web Content Accessibility Guidelines. PDF/UA-1 (ISO 14289-1:2014) aligns with and operationalizes WCAG 2.0 principles within the PDF format, while PDF/UA-2 (ISO 14289-2:2024) states it "may be used in conjunction with WCAG 2.x" - covering WCAG 2.0, 2.1, and 2.2. Where WCAG sets outcome-based success criteria (such as "provide text alternatives" at Level A, or sufficient color contrast at Level AA), PDF/UA specifies the exact technical mechanism within the PDF file format to satisfy those criteria - for instance, requiring alt text in the /Alt dictionary entry and structure tags in a logical tree. Conformance to PDF/UA alone does not constitute full WCAG conformance, as WCAG also addresses color contrast, cognitive accessibility, and other concerns that fall outside PDF/UA's scope.

How EqualWeb helps: EqualWeb's PDF Tools service directly addresses PDF/UA and Section 508 compliance by checking, remediating, and serving accessible PDFs - helping organizations work toward ISO 14289 conformance without rebuilding their document workflows from scratch. For organizations with large PDF libraries, EqualWeb's Managed Compliance service pairs certified IAAP/CPWA experts with systematic auditing and remediation, producing a signed Accessibility Compliance Certificate and an Accessibility Conformance Report (VPAT) that document progress toward full PDF/UA and WCAG conformance. Continuous Monitoring provides a live 0-100 compliance score and regression alerts, ensuring that newly published PDFs do not silently re-introduce barriers after remediation efforts. EqualWeb's Accessibility Testing tools - including a checker and crawler - can identify inaccessible PDFs across an entire domain, helping prioritize remediation efforts ahead of regulatory deadlines such as the April 2027 ADA Title II enforcement date for larger public entities. While no automated tool can independently resolve every accessibility issue in complex documents, EqualWeb's combination of AI-assisted remediation and certified expert oversight provides a structured, defensible path toward PDF/UA and broader digital accessibility conformance.

Q: What is PDF/UA and why does it matter?
A: PDF/UA (PDF/Universal Accessibility), formally ISO 14289, is the international standard defining the technical requirements for accessible PDF documents. It specifies how PDF files must be tagged, structured, and formatted so that screen readers and other assistive technologies can reliably navigate and read them. It matters because inaccessible PDFs create legal exposure under laws such as the ADA, Section 508, and the European Accessibility Act, and because millions of users with visual, motor, or cognitive disabilities depend on accessible documents to participate in education, employment, and public life.

Q: Who is required to comply with PDF/UA?
A: There is no single law that mandates PDF/UA by name globally, but its requirements overlap substantially with those of legally binding frameworks. In the U.S., federal agencies and contractors must produce accessible PDFs under Section 508, and public entities must meet WCAG 2.1 Level AA (which PDF/UA helps satisfy) under ADA Title II - with updated deadlines of April 26, 2027 for larger entities and April 26, 2028 for smaller ones, following a DOJ Interim Final Rule issued in April 2026. In the EU, businesses subject to the European Accessibility Act must produce accessible customer-facing PDFs for new and updated services from June 28, 2025, with a transition period to June 28, 2030 for existing services. Any organization - public or private - that publishes PDFs as part of its digital services benefits from adopting PDF/UA to demonstrate due diligence and reduce legal risk.

Q: What is the difference between PDF/UA-1 and PDF/UA-2?
A: PDF/UA-1 (ISO 14289-1:2014) is based on PDF 1.7 (ISO 32000-1) and defines foundational requirements for tagged structure, reading order, alt text, Unicode fonts, and security settings. PDF/UA-2 (ISO 14289-2:2024) is built on PDF 2.0 (ISO 32000-2) and adds expanded requirements for structure element attributes and annotations, MathML support for mathematical content, new PDF 2.0 structure element types, and richer metadata integration. Organizations creating new documents should consider PDF/UA-2 for maximum long-term alignment with the standard; PDF/UA-1 remains valid and widely deployed.

Q: What are the penalties for publishing inaccessible PDFs?
A: PDF/UA is a technical standard with no penalties of its own, but the laws it helps satisfy carry significant sanctions. Under the ADA in the U.S., DOJ civil penalties reach $118,225 for a first enforcement action and $236,451 for subsequent violations (2025 inflation-adjusted figures), and private lawsuits routinely result in settlements reaching tens of thousands to hundreds of thousands of dollars. Under Section 508, federal contractors face contract termination, payment withholding, and exclusion from future procurement. Under the European Accessibility Act, EU member states can impose fines that vary by country and can exceed €100,000. Under California's Unruh Act, each inaccessible instance can cost $4,000.

Q: Does PDF/UA compliance satisfy WCAG requirements for PDFs?
A: PDF/UA conformance substantially supports WCAG compliance for PDFs because the two standards are designed to work together: PDF/UA translates WCAG's outcome-based success criteria into precise PDF technical requirements. However, PDF/UA conformance alone is not sufficient for full WCAG compliance, as WCAG additionally covers color contrast (Success Criterion 1.4.3 at Level AA), cognitive accessibility requirements, and certain interaction criteria that PDF/UA does not address. Organizations aiming for documented WCAG 2.1 or 2.2 Level AA conformance should use PDF/UA as a technical baseline while also addressing WCAG criteria that fall outside PDF/UA's scope.

### Americans with Disabilities Act (ADA)
URL: https://www.equalweb.com/platform/standards/ada.html
Region: United States. Governing body: U.S. Department of Justice (DOJ), Civil Rights Division - the primary enforcer of Titles II and III. The Equal Employment Opportunity Commission (EEOC) enforces Title I (employment). The Federal Communications Commission (FCC) enforces Title IV (telecommunications). In effect: July 26, 1990 (signed into law); ADA Amendments Act effective January 1, 2009; DOJ Title II web accessibility final rule effective June 24, 2024; DOJ Title II compliance deadline extension (Interim Final Rule) effective April 20, 2026.

The Americans with Disabilities Act (ADA) is a landmark U.S. federal civil rights law, enacted July 26, 1990, that prohibits discrimination against individuals with disabilities in employment, state and local government services, public accommodations, transportation, and telecommunications. It is enforced primarily by the U.S. Department of Justice and the Equal Employment Opportunity Commission.

What it is: The Americans with Disabilities Act (ADA) is a comprehensive federal civil rights statute, codified at 42 U.S.C. § 12101 et seq., that prohibits discrimination on the basis of disability across five major areas of public life, structured as five titled sections. Signed by President George H.W. Bush on July 26, 1990, and significantly strengthened by the ADA Amendments Act of 2008 (effective January 1, 2009), the ADA defines disability as a physical or mental impairment that substantially limits one or more major life activities. The law requires covered entities to provide equal access, effective communication, and reasonable accommodations or modifications to people with disabilities. As digital services have become central to civic and commercial life, the DOJ has extended ADA obligations explicitly to websites, mobile apps, and other digital content.

Who must comply: Title I covers private employers, state and local governments, employment agencies, and labor unions with 15 or more employees, prohibiting disability discrimination in all aspects of employment. Title II applies to all state and local government entities - regardless of size or federal funding - requiring equal access to every program, service, and activity they offer, including digital services and websites. Title III covers nearly all private businesses open to the public (public accommodations), including retail, hospitality, healthcare, education, and financial services - with no small-business exemption for digital content. Title IV applies to telecommunications carriers and requires relay services for people with hearing or speech disabilities.

Key requirements:
- Provide effective communication to people with disabilities, including through accessible digital formats and auxiliary aids.
- Ensure websites and mobile applications meet WCAG 2.1 Level AA - now codified by rule for Title II entities and widely applied by courts to Title III businesses.
- Make reasonable modifications to policies, practices, and procedures to avoid discrimination, unless doing so would fundamentally alter the service.
- Ensure that new and altered facilities meet ADA Standards for Accessible Design (physical and, by extension, digital).
- Provide accessible documents, PDFs, and other digital content as part of programs and services.
- Title I employers must provide reasonable accommodations to qualified employees or job applicants with disabilities, absent undue hardship.
- Maintain ongoing accessibility - compliance is not a one-time event but a continuous obligation as websites and apps are updated.

Key dates:
- July 26, 1990: ADA signed into law; Titles II and III broadly effective with phased employment provisions
- January 1, 2009: ADA Amendments Act of 2008 takes effect, broadening the definition of disability
- June 24, 2024: DOJ Title II final rule on web and mobile app accessibility (WCAG 2.1 AA) takes effect
- April 26, 2027: Title II WCAG 2.1 AA web compliance deadline for state/local governments serving populations of 50,000 or more (extended from April 24, 2026 by DOJ Interim Final Rule, effective April 20, 2026)
- April 26, 2028: Title II WCAG 2.1 AA web compliance deadline for state/local governments serving populations under 50,000 and special district governments (extended from April 26, 2027 by the same DOJ Interim Final Rule)

Penalties & enforcement: Under Title III, the DOJ may seek civil monetary penalties of up to $75,000 for a first violation and up to $150,000 for subsequent violations (2014 statutory caps, subject to annual inflation adjustment under 28 CFR Part 85 - current adjusted amounts may be higher), in addition to injunctive relief; private plaintiffs can obtain injunctive relief and attorney's fees, and serial litigants file thousands of cases annually - 3,117 federal website-accessibility lawsuits were filed in 2025 alone (a 27% increase over 2024), with settlements typically ranging from $5,000 to $75,000 plus legal fees and remediation costs. Under Title II, the DOJ can file suit to enforce the law; federal funding recipients may also face loss of federal financial assistance through coordinated agency enforcement. The absence of a formal WCAG rule for Title III businesses has not shielded them from litigation: courts across multiple circuits have consistently held that websites constitute places of public accommodation subject to ADA obligations.

Relation to WCAG: The DOJ's April 2024 Title II final rule explicitly codifies WCAG 2.1 Level AA as the binding technical standard for state and local government websites and mobile apps, with compliance required by the extended 2027-2028 deadlines. For Title III (private businesses), no equivalent federal rule has been finalized, but DOJ guidance, multiple federal circuit courts, and the Department's settlement agreements consistently treat WCAG 2.1 Level AA as the de facto benchmark for assessing whether a website is accessible under the ADA. WCAG 2.1 builds on and is fully backward-compatible with WCAG 2.0 - the standard already incorporated by reference in the Revised Section 508 Standards - adding 17 new success criteria addressing mobile, low vision, and cognitive accessibility.

How EqualWeb helps: EqualWeb's AI Accessibility Widget can be deployed with a single line of code and automatically remediates up to 95% of common WCAG 2.1 Level AA issues - depending on how the site is built - in real time, helping organizations working toward ADA compliance demonstrate a good-faith effort to make their digital content accessible. Achieving conformance requires expert remediation beyond what the widget alone provides. For organizations - including state and local governments, universities, healthcare providers, and private businesses - that need to reach and maintain full ADA conformance, EqualWeb's Managed Compliance service pairs certified IAAP/CPWA experts with client-side remediation, continuous monitoring, and a signed Accessibility Compliance Certificate plus a VPAT/Accessibility Conformance Report to support legal defensibility. EqualWeb's Continuous Monitoring provides a live 0-100 compliance score and regression alerts so that accessibility does not degrade as websites are updated - critical given that ADA compliance is an ongoing obligation, not a one-time fix. For organizations that must also provide accessible PDFs as part of their programs and services, EqualWeb's PDF Tools help check, remediate, and serve documents meeting PDF/UA and Section 508 standards. Together, these services give covered entities a structured, evidence-backed pathway toward the WCAG 2.1 AA conformance that the ADA now expressly demands.

Q: Does the ADA apply to websites and mobile apps?
A: Yes. For state and local governments (Title II), the DOJ's April 2024 final rule explicitly requires websites and mobile apps to conform to WCAG 2.1 Level AA. For private businesses (Title III), no equivalent federal rule is currently in force, but federal courts across multiple circuits have ruled that websites are places of public accommodation subject to the ADA, and thousands of digital accessibility lawsuits are filed each year. Businesses of all sizes should treat WCAG 2.1 Level AA as the operative standard.

Q: Who must comply with the ADA?
A: Title I applies to employers with 15 or more employees. Title II covers all state and local government entities regardless of size. Title III covers virtually every private business open to the public - including online-only businesses - with no small-business or revenue-based exemption. Title IV covers telecommunications carriers.

Q: What is the ADA web accessibility compliance deadline for government entities?
A: Under the DOJ's 2024 final rule, as extended by the DOJ Interim Final Rule (effective April 20, 2026), state and local governments serving populations of 50,000 or more must comply with WCAG 2.1 Level AA by April 26, 2027. Those serving populations under 50,000, or any special district government, must comply by April 26, 2028.

Q: What are the penalties for ADA non-compliance?
A: The DOJ can seek civil monetary penalties up to $75,000 for a first ADA violation and up to $150,000 for repeat violations (2014 statutory caps, subject to annual inflation adjustment). Private plaintiffs under Title III can obtain injunctive relief and attorney's fees. In practice, most cases settle for $5,000-$75,000 plus legal fees, remediation costs, and ongoing monitoring requirements. Title II enforcement can also result in loss of federal financial assistance for non-compliant recipients.

Q: What WCAG level does the ADA require?
A: The DOJ's Title II rule requires WCAG 2.1 Level AA for state and local government digital content. For private businesses under Title III, WCAG 2.1 Level AA is the widely recognized and court-accepted benchmark, used in DOJ settlement agreements and judicial decisions. Meeting Level AA - which includes all Level A criteria - is the standard organizations should target to demonstrate ADA good-faith compliance.

Q: How do I check if my website is ADA compliant?
A: Start with an automated scan: EqualWeb's free Accessibility Checker scores any URL against WCAG 2.2 in seconds and lists the issues it finds, with no installation. Automated tools catch most common failures, but several WCAG criteria require human judgment, so conformance is confirmed through an expert audit - which EqualWeb's certified IAAP/CPWA specialists provide through Managed Compliance.

Q: How much does ADA compliance cost for a website?
A: It scales with the size and complexity of your site rather than a flat fee. A sensible sequence: run a free automated check to see where you stand, use AI remediation for the bulk of common issues (7-day free widget trial), then scope expert remediation and certification for what automation cannot verify - EqualWeb quotes Managed Compliance by scope.

### ADA Title II (web & mobile rule)
URL: https://www.equalweb.com/platform/standards/ada-title-ii.html
Region: United States. Governing body: U.S. Department of Justice (DOJ), Civil Rights Division, enforcing Title II of the Americans with Disabilities Act (42 U.S.C. § 12131 et seq.). In effect: Rule effective June 24, 2024; compliance deadlines April 26, 2027 (large entities) and April 26, 2028 (small entities and special districts), as extended by DOJ interim final rule effective April 20, 2026..

ADA Title II (web and mobile rule) is a 2024 U.S. Department of Justice regulation requiring all state and local government entities to make their websites and mobile applications conform to WCAG 2.1 Level AA, ensuring people with disabilities have equal access to public programs and services online. Published in the Federal Register on April 24, 2024, it codifies specific technical accessibility standards under Title II of the Americans with Disabilities Act for the first time.

What it is: ADA Title II prohibits discrimination on the basis of disability by state and local government entities. The 2024 DOJ final rule (28 C.F.R. Part 35) extends those nondiscrimination obligations explicitly to digital environments by requiring that web content and mobile apps meet Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Published April 24, 2024 and effective June 24, 2024, it provides a uniform federal technical standard for digital accessibility in the public sector for the first time. Compliance deadlines were subsequently extended by an April 2026 interim final rule, giving entities additional time to implement required changes without altering the substantive WCAG 2.1 AA standard.

Who must comply: The rule applies to all "public entities" under Title II of the ADA - every state government, local government, and any department, agency, special-purpose district, or instrumentality thereof. It also covers Amtrak and commuter rail authorities, as well as contractors and vendors delivering programs or services on behalf of a covered public entity. Public colleges and universities, public K-12 school districts, public libraries, courts, transit agencies, and health departments are all within scope. Private organizations are not directly covered by Title II, though Title III of the ADA imposes parallel obligations on places of public accommodation.

Key requirements:
- Web content and mobile apps must conform to WCAG 2.1, Level AA in full.
- The standard applies to all public-facing content needed to access government services, programs, or activities - including PDFs, online forms, videos, maps, and third-party widgets embedded on government sites.
- Content provided through contractors or vendors on behalf of a public entity must also meet the standard.
- Governments must update procurement and vendor contracts to require WCAG 2.1 AA conformance from technology and content suppliers.
- Five narrow exceptions exist: archived web content, preexisting conventional electronic documents not used for active services, third-party posted content (from truly unaffiliated users), individualized password-protected account documents, and preexisting social media posts.
- Even where an exception applies, public entities retain the broader ADA obligation to provide accessible alternatives upon request to ensure effective communication.
- Entities must designate responsible staff, train personnel, inventory digital assets, and establish formal accessibility policies as part of ongoing compliance.

Key dates:
- June 24, 2024: Rule effective date - DOJ final rule (28 C.F.R. Part 35) takes legal effect.
- April 26, 2027: Compliance deadline for state and local government entities serving a jurisdiction with a total population of 50,000 or more (extended from April 24, 2026 by DOJ interim final rule effective April 20, 2026).
- April 26, 2028: Compliance deadline for public entities serving a jurisdiction with a total population of fewer than 50,000, and all special district governments (extended from April 26, 2027 by DOJ interim final rule effective April 20, 2026).

Penalties & enforcement: The DOJ enforces Title II through complaint investigations, compliance reviews, mediation, and federal litigation; private individuals may also sue directly without first filing an administrative complaint. As of the most recent inflation adjustment (effective July 3, 2025, with no further adjustment for 2026), civil monetary penalties for ADA violations in DOJ-initiated actions reach $118,225 for a first violation and $236,451 for subsequent violations. Courts may also award injunctive relief compelling remediation, and plaintiffs in private suits may recover compensatory damages, attorneys' fees, and costs - making non-compliance a significant financial and reputational risk even before the formal compliance deadlines arrive.

Relation to WCAG: The 2024 DOJ final rule explicitly adopts Web Content Accessibility Guidelines (WCAG) version 2.1, Level AA as the sole technical standard for ADA Title II digital compliance - the first time a specific WCAG version has been written into binding federal regulation for the public sector. WCAG 2.1 AA encompasses all 50 success criteria of WCAG 2.0 AA plus 17 additional criteria, with particular attention to mobile accessibility and users with cognitive and low-vision disabilities. Entities that already meet WCAG 2.1 AA satisfy the technical requirements of the rule, though DOJ guidance encourages voluntary adoption of WCAG 2.2 as best practice.

How EqualWeb helps: EqualWeb's AI Accessibility Widget gives public-sector teams an immediate head start: a single line of JavaScript automatically remediates up to 95% of common WCAG 2.1 AA issues - depending on how the site is built - in real time on the client side, helping agencies move toward the technical standard required by the DOJ rule while a longer-term remediation roadmap is developed. For entities that need to reach certified conformance before the April 2027 or April 2028 compliance deadlines, EqualWeb's Managed Compliance service pairs IAAP/CPWA-certified experts with ongoing audit, client-side remediation, and continuous monitoring to support WCAG 2.1 AA conformance - and delivers a signed Accessibility Compliance Certificate, a VPAT/Accessibility Conformance Report, and a full evidence pack suitable for DOJ inquiries or procurement requirements. EqualWeb's Continuous Monitoring dashboard provides a live 0-100 compliance score and regression alerts, giving agencies the visibility needed to detect and address new accessibility issues as content changes over time. For governments that publish large volumes of official documents, EqualWeb's PDF Tools can check, remediate, and serve accessible PDFs meeting PDF/UA and Section 508 standards - directly addressing the rule's requirement that conventional electronic documents used to access government services be accessible. Together, these capabilities provide a layered, documented approach to working toward ADA Title II digital compliance rather than a single point-in-time fix.

Q: What does ADA Title II require for websites?
A: The 2024 DOJ final rule requires all state and local government entities to make their websites and mobile apps conform to WCAG 2.1, Level AA. This covers all web content needed to access government services, including PDFs, online forms, video content, and embedded third-party tools. Five narrow exceptions apply for archived content, preexisting documents not used for active services, unaffiliated third-party posts, individualized account documents, and preexisting social media posts. Even where an exception applies, governments must still provide accessible alternatives upon request.

Q: Who must comply with ADA Title II web accessibility requirements?
A: All state and local government entities in the United States must comply, including agencies, departments, special-purpose districts, commuter rail authorities, public universities, public schools, libraries, and courts. Contractors and vendors that provide services or content on behalf of those governments are also covered. Private businesses are governed by ADA Title III rather than Title II. Federal agencies have a separate framework under Section 508 of the Rehabilitation Act.

Q: What is the compliance deadline for the ADA Title II web accessibility rule?
A: Following a DOJ interim final rule issued April 20, 2026, the deadlines were extended by one year. Entities serving jurisdictions with populations of 50,000 or more must comply by April 26, 2027. Entities serving populations under 50,000 and all special district governments have until April 26, 2028. Population is determined using U.S. Census Bureau data. The substantive WCAG 2.1 AA technical standard was not changed by the extension.

Q: What are the penalties for violating ADA Title II web accessibility requirements?
A: As of the most recent inflation adjustment (effective July 3, 2025), DOJ can impose civil monetary penalties of up to $118,225 for a first violation and up to $236,451 for subsequent violations in federal enforcement actions. Private individuals may also file lawsuits directly seeking injunctive relief, compensatory damages, and attorneys' fees without exhausting administrative remedies first. The DOJ typically attempts mediation and remediation agreements before litigation, but enforcement activity and private litigation have both increased since the 2024 final rule.

Q: Does ADA Title II require WCAG 2.1 or WCAG 2.2?
A: The 2024 final rule legally requires WCAG 2.1, Level AA as the minimum technical standard. The DOJ acknowledged WCAG 2.2 in its rulemaking but chose WCAG 2.1 AA to provide consistency with existing state laws and procurement standards. DOJ guidance encourages entities to voluntarily adopt WCAG 2.2 as best practice, and doing so will also satisfy the WCAG 2.1 AA requirement since WCAG 2.2 is a superset of WCAG 2.1.

Q: How can a government agency check if its website is ADA Title II compliant?
A: Begin with automated coverage: EqualWeb's free Accessibility Checker scans any page against WCAG 2.2 instantly, and the Accessibility Monitor offers a free 100-page scan with a 0-100 compliance score for tracking progress toward the rule's deadlines. Because WCAG conformance also involves criteria that need human review, agencies typically pair scanning with a certified expert audit and documentation such as a VPAT 2.2 report.

### Section 508 of the Rehabilitation Act
URL: https://www.equalweb.com/platform/standards/section-508.html
Region: United States. Governing body: U.S. Access Board (standards development) and U.S. General Services Administration (GSA) Government-wide IT Accessibility Program (implementation guidance and annual congressional reporting), with enforcement oversight shared by the U.S. Department of Justice (DOJ) Civil Rights Division (biennial reporting to Congress and enforcement actions) and the Office of Management and Budget (OMB) (compliance coordination). In effect: January 18, 2018 (Revised ICT Standards compliance required); original standards effective June 21, 2001; underlying 1998 statutory amendment signed August 7, 1998.

Section 508 of the Rehabilitation Act (29 U.S.C. § 794d) is a U.S. federal law requiring all federal agencies to develop, procure, maintain, and use information and communication technology (ICT) that is accessible to people with disabilities. Amended in 1998 and substantially updated by final rule in January 2017, it mandates conformance with WCAG 2.0 Level A and AA success criteria for web content and electronic documents, codified at 36 CFR Part 1194, with agency compliance required from January 18, 2018.

What it is: Section 508 of the Rehabilitation Act is a U.S. federal accessibility law, codified at 29 U.S.C. § 794d, that requires federal agencies to ensure their information and communication technology (ICT) is accessible to employees and members of the public with disabilities. Originally added to the Rehabilitation Act of 1973 in 1986 and significantly amended by Congress on August 7, 1998, the law was further strengthened by the U.S. Access Board's January 2017 final rule, which updated the technical standards and incorporated WCAG 2.0 Level A and AA success criteria by reference (36 CFR Part 1194), with agency compliance required from January 18, 2018. Covered ICT includes websites, web applications, software, electronic documents, hardware, telecommunications equipment, public-use kiosks, and any digital product developed, procured, maintained, or used by a federal agency. The GSA's Government-wide IT Accessibility Program administers implementation guidance through Section508.gov and submits annual compliance assessments to Congress under the Consolidated Appropriations Act of 2023 (Section 752); the DOJ Civil Rights Division submits separate biennial compliance reports to the President and Congress and can bring enforcement actions.

Who must comply: Section 508 applies directly to every U.S. federal executive branch department and agency - including the U.S. Postal Service - whenever they develop, procure, maintain, or use ICT. Private-sector vendors and contractors must also comply: any company selling software, hardware, websites, electronic documents, or other digital products or services to the federal government must demonstrate that its offerings meet the Revised 508 Standards, typically through a completed Voluntary Product Accessibility Template (VPAT) / Accessibility Conformance Report (ACR). Organizations that receive federal grants or funding - including state and local agencies, universities, nonprofits, and hospitals - may be subject to Section 508 obligations depending on the terms of their funding agreements. Coverage extends to employee-facing internal systems, not just public-facing websites, making it one of the broadest ICT accessibility requirements in the world.

Key requirements:
- Web content and electronic documents must conform to WCAG 2.0 Level A and Level AA success criteria (36 CFR Part 1194, Appendix A). Agencies and vendors targeting WCAG 2.1 AA satisfy and exceed this mandatory floor.
- Software applications, including non-web software, must meet the functional performance criteria and applicable technical standards in the Revised 508 Standards (36 CFR Part 1194, Appendix C).
- Hardware ICT - computers, multifunction printers, telecommunications equipment, and public-use kiosks - must meet hardware-specific accessibility requirements including operable controls and support for assistive technology.
- Agencies must provide equivalent access to employees and members of the public with disabilities when an undue burden or fundamental alteration exception is claimed, and must document that determination in writing.
- Federal procurement requires agencies to identify applicable Section 508 standards before solicitation, include 508 requirements in contracts, and evaluate vendor VPATs/ACRs prior to award.
- Electronic documents (PDFs, Word files, spreadsheets, presentations) disseminated by agencies or provided under contract must conform to WCAG 2.0 Level AA and, where applicable, PDF/UA standards.
- Agencies must maintain a formal Section 508 complaint process and designate a Section 508 Program Manager responsible for training, reporting, and ongoing conformance.

Key dates:
- June 21, 2001: Original Section 508 standards (promulgated December 21, 2000) became enforceable for federal agencies.
- January 18, 2018: Revised ICT Standards (incorporating WCAG 2.0 Level A and AA) became mandatory for all new federal ICT development, procurement, maintenance, and use.
- Ongoing (annual): GSA must submit a governmentwide Section 508 compliance assessment to Congress annually under the Consolidated Appropriations Act of 2023 (Section 752); the DOJ submits a separate biennial report to the President and Congress on agency compliance.

Penalties & enforcement: Individuals with disabilities who are denied accessible ICT by a federal agency may file an administrative complaint directly with that agency, and - after exhausting administrative remedies - may bring a civil lawsuit in federal court. Available remedies mirror those under Section 504 of the Rehabilitation Act and include declaratory relief, injunctive relief (requiring the agency to remediate), and attorneys' fees; however, compensatory and punitive damages are generally not recoverable against federal agencies. For vendors and contractors, non-compliance can result in contract termination for cause, reprocurement costs charged back to the vendor, exclusion from future federal procurement opportunities, and referral for suspension or debarment. Federal agencies themselves face congressional oversight through annual GSA and biennial DOJ compliance reports, DOJ enforcement actions, and reputational damage; recent DOJ enforcement settlements have required agencies to undertake multi-year remediation programs at significant cost.

Relation to WCAG: The Revised 508 Standards, effective January 18, 2018, formally incorporate WCAG 2.0 Level A and Level AA success criteria by reference for all web content and electronic documents covered by Section 508 (36 CFR Part 1194, Appendix A). As of mid-2026, WCAG 2.1 and WCAG 2.2 have not been formally adopted into the binding regulatory text of Section 508 - any update to incorporate newer WCAG versions would require new rulemaking by the U.S. Access Board. However, the Access Board and GSA actively encourage agencies to adopt WCAG 2.1 AA and WCAG 2.2 AA as best practice, and Section508.gov has published guidance on the additional requirements those versions introduce. In practice, agencies and vendors that target WCAG 2.1 Level AA conformance - the widely adopted international baseline - satisfy and exceed the current mandatory Section 508 web content standard.

How EqualWeb helps: EqualWeb's AI Accessibility Widget - deployed with a single line of code - automatically remediates up to 95% of common WCAG 2.0 and WCAG 2.1 Level AA issues - depending on how the site is built - in real time on the client side, giving federal contractors, vendors, and funded organizations a meaningful head-start toward Section 508 web content conformance. The widget alone does not produce conformance; it is one layer of a broader compliance program. For agencies and vendors that need documented conformance, EqualWeb's Managed Compliance service pairs certified IAAP/CPWA accessibility experts with ongoing client-side remediation, continuous monitoring, and a signed Accessibility Compliance Certificate alongside a completed VPAT/Accessibility Conformance Report - the precise documentation federal procurement requires. EqualWeb's PDF Tools address one of the most commonly cited Section 508 gaps: inaccessible electronic documents. They check and remediate PDFs to both PDF/UA and Section 508 standards so agencies can confidently distribute accessible content. The Continuous Monitoring dashboard tracks a live 0-100 compliance score with regression alerts, enabling program managers to demonstrate ongoing conformance and respond quickly to accessibility regressions before they trigger complaints. Together, the widget, managed expert service, and monitoring tools support a layered Section 508 compliance program - working toward conformance rather than relying on any single automated fix.

Q: What is Section 508 and who does it apply to?
A: Section 508 of the Rehabilitation Act (29 U.S.C. § 794d) is a U.S. federal law requiring federal agencies to make their ICT accessible to people with disabilities. It applies to every federal executive branch agency, as well as contractors and vendors who develop, sell, or provide digital products and services to the federal government. Organizations receiving federal funding may also have Section 508 obligations under their grant or funding terms.

Q: What WCAG level does Section 508 require?
A: The Revised 508 Standards, effective January 18, 2018, require conformance with WCAG 2.0 Level A and Level AA success criteria for web content and electronic documents. WCAG 2.1 and 2.2 have not yet been formally written into the binding regulation, but government guidance strongly recommends targeting WCAG 2.1 AA as a practical compliance floor. Agencies and vendors that meet WCAG 2.1 AA satisfy and exceed the current mandatory Section 508 web content requirement.

Q: Does Section 508 apply to private companies?
A: Section 508 does not apply to private companies in general, but it does apply to any private-sector vendor, contractor, or supplier that develops, sells, or provides ICT products or services to a federal agency. Such companies must demonstrate conformance through a Voluntary Product Accessibility Template (VPAT) / Accessibility Conformance Report (ACR) before and during the procurement process. Companies that receive federal grants or operate under federal funding agreements may also have Section 508 obligations.

Q: What are the penalties for Section 508 non-compliance?
A: Individuals can file administrative complaints with the relevant agency and, after exhausting those remedies, sue in federal court for injunctive relief and attorneys' fees - but not compensatory or punitive damages against federal agencies. For federal contractors, non-compliance can lead to contract termination, reprocurement costs, and suspension or debarment from future federal work. Agencies face congressional oversight through annual GSA and biennial DOJ compliance reports, and DOJ enforcement actions have required agencies to undertake significant, multi-year remediation programs.

Q: What is a VPAT and is it required for Section 508?
A: A VPAT (Voluntary Product Accessibility Template) is a standardized document in which a vendor self-reports how its ICT product conforms to the Revised 508 Standards; the completed document is called an Accessibility Conformance Report (ACR). While the VPAT is technically voluntary, federal agencies typically require a current ACR as part of the procurement evaluation process, and GSA recommends that all vendors marketing ICT to the federal government produce one. An incomplete or inaccurate VPAT can disqualify a product from federal consideration.

### Section 504 of the Rehabilitation Act
URL: https://www.equalweb.com/platform/standards/section-504.html
Region: United States. Governing body: U.S. Department of Health and Human Services (HHS) Office for Civil Rights (OCR) is the primary federal enforcer for HHS-funded entities. Each federal agency issues and enforces its own Section 504 regulations for its funded programs; for example, the Department of Education enforces 34 C.F.R. Part 104 for educational recipients, and the Department of Labor's Civil Rights Center enforces compliance for DOL-funded entities. The statute (29 U.S.C. § 794) itself is administered government-wide under coordination authority granted to the Attorney General under Executive Order 12250 (1980), with the Department of Justice handling civil litigation referrals. In effect: Enacted September 26, 1973; implementing regulations first enforced April 28, 1977; HHS digital accessibility final rule (45 C.F.R. Part 84) effective July 8, 2024; WCAG 2.1 AA technical compliance deadlines extended to May 11, 2027 (entities with 15 or more employees) and May 10, 2028 (entities with fewer than 15 employees) by HHS Interim Final Rule published May 11, 2026.

Section 504 of the Rehabilitation Act (29 U.S.C. § 794) is a federal civil rights law that prohibits discrimination on the basis of disability in any program or activity receiving federal financial assistance or conducted by a federal executive agency. It requires covered entities to provide individuals with disabilities equal access to their programs, services, and-under a 2024 HHS final rule-digital content including websites and mobile applications conforming to WCAG 2.1 Level AA.

What it is: Section 504 of the Rehabilitation Act of 1973 (codified at 29 U.S.C. § 794) prohibits any program or activity receiving federal financial assistance from excluding, denying benefits to, or discriminating against an otherwise qualified individual solely on the basis of disability. The statute covers a broad range of entities-from hospitals and health plans to universities, state agencies, and nonprofit organizations-that receive funding from any federal department or agency. In May 2024, HHS issued a final rule that for the first time established explicit digital accessibility standards under Section 504, mandating that covered websites, mobile apps, patient portals, telehealth platforms, and social media accounts conform to WCAG 2.1 Level AA. The underlying nondiscrimination obligation has been in effect since 1973; the digital technical standard carries phased compliance deadlines through 2027-2028 (following a one-year extension granted by HHS in May 2026).

Who must comply: Section 504 applies to every program or activity that receives federal financial assistance, regardless of sector. This includes hospitals, physician practices, health insurers, managed care organizations, state Medicaid agencies, nursing homes, telehealth providers, medical and nursing schools, public K-12 schools and universities, federally funded housing agencies, and any other organization that accepts federal grants, contracts, or reimbursements such as Medicare or Medicaid. The 15-employee threshold in the 2024 HHS rule determines only which compliance deadline applies, not whether an entity is covered-even a small clinic accepting Medicaid is subject to Section 504. Federal executive agencies and the U.S. Postal Service are also directly covered, regardless of whether they receive external funding.

Key requirements:
- Provide equal access to programs, services, and benefits: no qualified individual with a disability may be excluded or denied benefits solely on the basis of disability.
- Ensure websites and mobile applications conform to WCAG 2.1 Level A and Level AA success criteria (HHS-funded entities under the 2024 final rule; conformance to a stricter standard such as WCAG 2.2 AA is also acceptable).
- Ensure program accessibility across all digital channels, including patient portals, telehealth systems, social media accounts, and third-party platforms used to deliver services.
- Hold third-party vendors accountable: organizations remain legally responsible for the accessibility of contracted or licensed digital tools, including EHR systems, scheduling platforms, and payment interfaces.
- Provide reasonable accommodations and effective communication for employees and service recipients with disabilities, including those with hearing or vision disabilities.
- Designate a Section 504 coordinator (required for entities with 15 or more employees), adopt grievance procedures, and publish a nondiscrimination notice.
- Maintain accessible physical facilities and offer alternative service delivery methods where structural modifications are not feasible.

Key dates:
- July 8, 2024: HHS Section 504 final rule (45 C.F.R. Part 84) took effect, establishing WCAG 2.1 AA as the explicit digital accessibility standard for covered web content and mobile applications; underlying nondiscrimination obligation applies immediately.
- May 11, 2027: WCAG 2.1 AA technical compliance deadline for HHS-funded entities with 15 or more employees (extended by one year from May 11, 2026 by HHS Interim Final Rule published May 11, 2026).
- May 10, 2028: WCAG 2.1 AA technical compliance deadline for HHS-funded entities with fewer than 15 employees (extended by one year from May 10, 2027 by the same HHS Interim Final Rule).

Penalties & enforcement: Noncompliance with Section 504 can result in suspension or termination of federal financial assistance-an existential threat for any organization dependent on Medicare, Medicaid, or HHS grants. The HHS Office for Civil Rights may initiate investigations proactively through compliance reviews or in response to individual complaints, and may refer cases to the Department of Justice for civil litigation. Individuals also hold a private right of action under Section 504 without first exhausting administrative remedies, and may obtain injunctive relief and compensatory damages. However, punitive damages and emotional-distress damages are not available following the U.S. Supreme Court's 2022 ruling in Cummings v. Premier Rehab Keller, P.L.L.C., 596 U.S. 212 (2022), which held that such damages are not recoverable in Spending Clause anti-discrimination statutes.

Relation to WCAG: The HHS Section 504 final rule (effective July 8, 2024) explicitly adopts the Web Content Accessibility Guidelines (WCAG), Version 2.1, Level A and Level AA success criteria as the mandatory technical standard for covered websites and mobile applications. Covered entities may alternatively conform to a stricter standard-such as WCAG 2.2 Level AA-provided it offers substantially equivalent or greater accessibility. The rule's WCAG 2.1 AA requirement aligns Section 504 with Section 508 of the Rehabilitation Act (which governs federal agency ICT procurement) and with ADA Title II regulations finalized in April 2024, creating a largely unified federal digital accessibility framework built on the same WCAG foundation.

How EqualWeb helps: EqualWeb's AI Accessibility Widget provides a one-line installation that automatically remediates up to 95% of common WCAG 2.1 AA issues - depending on how the site is built - in real time on the client side-helping organizations begin working toward Section 504 digital compliance immediately while a broader remediation plan is developed. The widget alone does not constitute conformance; meeting the WCAG 2.1 AA standard that Section 504 demands requires a more comprehensive approach. For certified conformance, EqualWeb's Managed Compliance service deploys IAAP/CPWA-certified experts to audit, remediate, monitor, and certify a site toward WCAG 2.1 AA conformance, delivering a signed Accessibility Compliance Certificate and a VPAT/Accessibility Conformance Report that can serve as evidence of good-faith compliance efforts in an HHS review or complaint investigation. EqualWeb's Continuous Monitoring provides a live 0-100 compliance score and regression alerts, enabling organizations to detect and address new barriers before they affect users or trigger enforcement action. For healthcare and social services organizations with PDF-heavy content-such as intake forms, patient education materials, and policy documents-EqualWeb's PDF Tools check, remediate, and serve accessible PDFs meeting PDF/UA and Section 508 standards, addressing a common gap in Section 504 digital programs. Together, these capabilities form a layered compliance infrastructure aligned with the phased Section 504 deadlines running through 2027-2028.

Q: What is Section 504 of the Rehabilitation Act?
A: Section 504 of the Rehabilitation Act (29 U.S.C. § 794) is a federal civil rights law enacted in 1973 that prohibits discrimination on the basis of disability in any program or activity receiving federal financial assistance. It requires covered organizations to provide individuals with disabilities equal access to their programs and services, including websites and digital content under a 2024 HHS final rule that mandates WCAG 2.1 AA conformance.

Q: Who must comply with Section 504?
A: Any program or activity receiving federal financial assistance must comply, including hospitals, health plans, physician practices, state Medicaid agencies, K-12 schools, universities, and federally funded nonprofits. Federal executive agencies and the U.S. Postal Service are also directly covered. Even small organizations-such as a clinic with only a few staff members-are subject to Section 504 if they accept any form of federal funding, including Medicare or Medicaid reimbursements.

Q: What WCAG level does Section 504 require?
A: The HHS Section 504 final rule (effective July 8, 2024) requires covered entities to conform to WCAG 2.1 Level A and Level AA success criteria for websites and mobile applications. Entities may also satisfy this requirement by conforming to a stricter standard such as WCAG 2.2 AA, provided it offers substantially equivalent or greater accessibility. The technical compliance deadlines extend through 2027-2028, but the underlying nondiscrimination obligation applies immediately.

Q: What are the Section 504 digital accessibility compliance deadlines?
A: Following a one-year extension issued by HHS in May 2026, HHS-funded entities with 15 or more employees must achieve WCAG 2.1 AA conformance by May 11, 2027. Entities with fewer than 15 employees have until May 10, 2028. The deadline extension does not affect the underlying legal obligation: the nondiscrimination requirement has been in force since 1973, and the HHS final rule took effect July 8, 2024.

Q: What are the penalties for violating Section 504?
A: The primary consequence is loss of federal financial assistance, including potential suspension or termination from Medicare, Medicaid, or other federal programs. The HHS Office for Civil Rights can open compliance reviews without a complaint and refer cases to the Department of Justice for litigation. Individuals may file private lawsuits without first exhausting administrative processes and may seek compensatory damages and injunctive relief, though punitive damages and emotional-distress damages are not recoverable under Section 504 following the Supreme Court's 2022 ruling in Cummings v. Premier Rehab Keller.

### California Unruh Civil Rights Act
URL: https://www.equalweb.com/platform/standards/unruh-act.html
Region: United States (California). Governing body: The California Civil Rights Department (CRD) - renamed from the Department of Fair Employment and Housing (DFEH) in July 2022 - is the state agency authorized to investigate and enforce Unruh Act complaints; it operates under the Business, Consumer Services and Housing Agency. The Attorney General, district attorneys, and city attorneys may also bring civil enforcement actions seeking injunctive relief. Additionally, private plaintiffs enforce the Act directly through civil litigation in California state and federal courts, with no requirement to file a government complaint first. In effect: Originally enacted 1959; amended 1992 to incorporate the ADA (making ADA violations per-se Unruh violations); amended 2015 (SB 600, effective January 1, 2016) to add citizenship, primary language, and immigration status as protected characteristics; further amended by Stats. 2024, Ch. 779 (effective January 1, 2025) to expand the definition of "race" to explicitly include hair texture and protective hairstyles, and to clarify that discrimination based on perceived characteristics or association with protected individuals is prohibited..

The California Unruh Civil Rights Act (California Civil Code § 51) is a state law enacted in 1959 that grants all persons within California full and equal accommodations, advantages, facilities, privileges, and services in all business establishments, prohibiting discrimination on the basis of disability, sex, race, religion, national origin, and other protected characteristics. A 1992 amendment incorporated the Americans with Disabilities Act by reference, making any ADA violation - including inaccessible websites - a per-se violation of the Unruh Act. Statutory damages of at least $4,000 per violation make California one of the most litigated states for digital accessibility claims.

What it is: The Unruh Civil Rights Act, codified at California Civil Code §§ 51-52, is California's primary anti-discrimination statute for business establishments. Enacted in 1959 and named for its author Jesse M. Unruh, the law declares that "all persons within the jurisdiction of this state are free and equal" and entitled to full and equal access to all business establishments regardless of disability, sex, race, color, religion, ancestry, national origin, medical condition, genetic information, marital status, sexual orientation, citizenship, primary language, or immigration status. The 1992 amendment explicitly incorporated the ADA, so any ADA violation - including failure to provide accessible websites or mobile applications - constitutes an automatic violation of the Unruh Act. A 2025 amendment (Stats. 2024, Ch. 779) further expanded the definition of "race" to include hair texture and protective hairstyles and clarified that discrimination based on perceived characteristics or association with protected individuals is prohibited. Unlike the federal ADA, the Unruh Act provides plaintiffs with statutory damages, making California one of the most litigated states for digital accessibility claims.

Who must comply: The Unruh Act applies to "business establishments of every kind whatsoever" operating in California, including retail stores, restaurants, hotels, hospitals, financial institutions, professional services, non-profits with commercial purposes, and digital platforms. Courts have extended the Act to websites and mobile applications that function as gateways to goods or services - including those of out-of-state businesses that generate significant revenue from California residents. A 2020 California Court of Appeals decision held that if a business derives approximately 10% of its sales from California consumers, its website is treated as the functional equivalent of a physical California storefront. However, the August 2022 ruling in Martinez v. Cot'n Wash, Inc. (81 Cal.App.5th 1026) - binding precedent after the California Supreme Court denied review in November 2022 - held that purely online-only businesses with no nexus to a physical place of business may fall outside Unruh Act coverage under the ADA-incorporation theory (§ 51(f)), though direct intentional-discrimination claims under § 51(b) remain an open avenue.

Key requirements:
- Provide full and equal access to all goods, services, and digital content for persons with disabilities, consistent with California Civil Code § 51.
- Ensure websites and mobile applications are accessible to users with disabilities; California courts have consistently applied WCAG 2.1 Level AA as the de facto technical benchmark in litigation and settlements, while California state agencies are now required to meet WCAG 2.2 Level AA.
- Do not discriminate against any person on the basis of disability - denial of equal digital access is treated as intentional discrimination under California case law when the barrier is known and not remediated.
- Incorporate ADA Title III requirements into digital properties, since any ADA violation constitutes an automatic Unruh Act violation under the 1992 amendment (Civil Code § 51(f)).
- Provide alternative means of equal access where a specific digital barrier cannot be immediately remediated (a temporary mitigation measure; full remediation is required).
- Maintain ongoing accessibility compliance - each visit to an inaccessible website by a person with a disability may constitute a separate, independently actionable violation.
- File complaints with the California Civil Rights Department (CRD) within one year of the last discriminatory act, consistent with the Act's administrative complaint timeline; however, direct civil litigation requires no prior administrative filing.

Penalties & enforcement: Under California Civil Code § 52(a), a business that violates the Unruh Act is liable for actual damages plus punitive damages of up to three times actual damages, but no less than $4,000 per violation, as well as attorney's fees and costs awarded to the prevailing plaintiff. Because each encounter with an inaccessible barrier can constitute a distinct offense, damages aggregate rapidly - a single disabled user making multiple visits to an inaccessible website before it is corrected can result in tens of thousands of dollars in statutory exposure. A reduced-damages provision applies to certain construction-related accessibility violations: a qualifying defendant who corrects barriers promptly after service of a complaint may see the per-violation minimum reduced to $2,000 or $1,000 depending on the speed of correction, but this construction-specific safe harbor does not reliably apply to digital accessibility claims. The Attorney General, district attorneys, and city attorneys may also seek civil injunctive relief under § 52(b). California accounts for a disproportionately large share of all ADA-related federal litigation nationwide, in large part because the Unruh Act's damages provision makes California claims significantly more financially consequential than ADA-only claims in other states.

Relation to WCAG: The Unruh Act does not specify a technical accessibility standard within its statutory text, but California courts have consistently applied the Web Content Accessibility Guidelines (WCAG) as the practical benchmark for evaluating website accessibility claims. The California Court of Appeals in Thurston v. Midvale Corp. affirmed an injunction requiring the defendant's website to conform to WCAG 2.0 Level A and AA, and subsequent litigation has standardized on WCAG 2.1 Level AA as the de facto compliance threshold in both settlements and court orders. Because the Unruh Act incorporates the ADA by reference, the U.S. Department of Justice's April 2024 final rule (effective June 24, 2024) adopting WCAG 2.1 Level AA as the ADA Title II standard for state and local governments further reinforces WCAG 2.1 AA as the authoritative technical benchmark for Unruh Act compliance. Note: the DOJ issued an interim final rule in April 2026 extending the compliance deadlines for state and local governments, but the WCAG 2.1 AA standard itself remains unchanged. California state agencies are separately required to meet WCAG 2.2 Level AA under state-specific mandates.

How EqualWeb helps: EqualWeb's AI Accessibility Widget - installed with a single line of code - automatically remediates up to 95% of common WCAG 2.1 Level AA barriers - depending on how the site is built - in real time on the client side, directly addressing the technical standard that California courts apply to Unruh Act claims, and helps businesses begin working toward the level of digital accessibility that courts expect. The widget alone does not constitute conformance; it is the starting layer of a broader compliance approach. For organizations seeking certifiable conformance that can support a documented good-faith record, EqualWeb's Managed Compliance service pairs IAAP/CPWA-certified experts with continuous client-side remediation, producing a signed Accessibility Compliance Certificate, a VPAT/Accessibility Conformance Report, and a documented evidence pack - the kind of good-faith compliance record that is relevant when Unruh Act exposure arises. EqualWeb's Continuous Monitoring provides a live 0-100 compliance score with regression alerts, so new content or code changes that could create fresh Unruh Act exposure are flagged before they accumulate as actionable barriers. For businesses with document-heavy workflows, EqualWeb's PDF Tools check and remediate PDFs to PDF/UA standards, addressing accessibility barriers that extend beyond web pages. Together, the platform supports a layered, documented approach to the WCAG 2.1 AA conformance that California courts treat as the Unruh Act's de facto technical benchmark.

Q: Does the Unruh Act apply to websites and mobile apps?
A: Yes. California courts have held that websites and mobile applications that serve as gateways to a business's goods or services must be accessible to people with disabilities under the Unruh Act. A business does not need a physical presence in California for its digital properties to be covered - courts have found that generating roughly 10% of sales from California consumers is sufficient to create Unruh Act obligations. However, the August 2022 ruling in Martinez v. Cot'n Wash, Inc. established that purely online-only businesses with no physical nexus may have a defense against ADA-incorporation claims under the Act; businesses with any physical operations or California customer base remain at significant risk. Each inaccessible webpage visit by a person with a disability can constitute a separate violation.

Q: What WCAG level is required for Unruh Act compliance?
A: The Unruh Act does not specify a WCAG version in its text, but California courts and settlement agreements have converged on WCAG 2.1 Level AA as the de facto standard. The California Court of Appeals in Thurston v. Midvale Corp. ordered WCAG 2.0 AA conformance, and more recent litigation and settlements consistently reference WCAG 2.1 AA. California state agencies face a higher bar - WCAG 2.2 Level AA - under separate state mandates. Private businesses seeking to demonstrate good-faith compliance should target WCAG 2.1 Level AA at minimum.

Q: What are the penalties for an Unruh Act violation?
A: Under California Civil Code § 52, a violating business is liable for the greater of actual damages or a statutory minimum of $4,000 per violation, plus up to three times actual damages (punitive damages), plus attorney's fees. Damages accumulate per discriminatory incident, meaning multiple visits to an inaccessible website can compound liability rapidly. There is no cap on the number of violations a single plaintiff may claim.

Q: Who enforces the Unruh Civil Rights Act?
A: The California Civil Rights Department (CRD) - formerly the Department of Fair Employment and Housing (DFEH), renamed in July 2022 - is the state agency authorized to investigate Unruh Act complaints. Individuals may file administrative complaints with the CRD within one year of the discriminatory act. However, the Unruh Act also provides a direct private right of action - the vast majority of digital accessibility cases are filed as civil lawsuits in California state or federal court without any prior administrative filing. The Attorney General, district attorneys, and city attorneys may additionally bring civil enforcement actions seeking injunctive relief.

Q: Is the Unruh Act the same as the ADA?
A: No, but they are closely linked. The Unruh Act is a California state law that, since a 1992 amendment, explicitly incorporates the ADA - meaning any ADA violation is automatically also an Unruh Act violation. The key practical difference is damages: the federal ADA limits disability plaintiffs to injunctive relief and attorney's fees, while the Unruh Act additionally provides statutory damages of at least $4,000 per violation plus punitive damages of up to three times actual damages, making California-based Unruh claims significantly more financially consequential for defendants.

### Colorado House Bill 21-1110
URL: https://www.equalweb.com/platform/standards/colorado-hb-21-1110.html
Region: United States (Colorado). Governing body: Colorado General Assembly (enacted); Colorado Governor's Office of Information Technology (OIT) (standard-setting and oversight via rulemaking); enforcement through private civil action in Colorado state courts In effect: July 1, 2025 (full enforcement; original WCAG conformance deadline was July 1, 2024, extended to July 1, 2025 by HB 24-1454 for qualifying entities demonstrating good-faith efforts).

Colorado HB 21-1110 is a Colorado state law, signed on June 30, 2021, that requires all state and local government entities - including agencies, school districts, and public universities - to make their information and communications technology (ICT) conform to WCAG 2.1 Level AA accessibility standards. Full enforcement has been in effect since July 1, 2025, following the expiration of the one-year grace period established by companion bill HB 24-1454.

What it is: Colorado House Bill 21-1110, formally titled "Colorado Laws for Persons with Disabilities," was signed into law on June 30, 2021, and strengthens existing Colorado anti-discrimination statutes by explicitly requiring government ICT to be digitally accessible to people with disabilities. The law directs the Colorado Governor's Office of Information Technology (OIT) to establish and maintain accessibility standards based on the most current Web Content Accessibility Guidelines (WCAG) published by the W3C Web Accessibility Initiative. Colorado OIT's current mandated standard, reaffirmed in its May 2025 rules amendment, is WCAG 2.1 Level AA. The law establishes a private right of action, allowing individuals with disabilities who experience discrimination due to inaccessible government technology to sue in Colorado state court. A companion bill, HB 24-1454 (signed May 24, 2024), provided a one-year immunity from liability for entities demonstrating good-faith compliance efforts, with that grace period expiring July 1, 2025. In May 2025, OIT also amended its Technology Accessibility Rules to introduce multiple compliance pathways and align more closely with the ADA Title II web accessibility rule, while retaining WCAG 2.1 AA as the core technical standard.

Who must comply: Colorado HB 21-1110 applies to all Colorado government entities - encompassing every state agency across the executive, legislative, and judicial branches, as well as state-supported higher education institutions and community colleges. It also covers every local government entity in the state, including counties, municipalities, towns, school districts (K-12), and special districts such as water, fire, and transportation authorities. The law reaches any ICT used by employees or the public to access government services, programs, or activities - including public-facing websites, web applications, mobile apps, digital documents (including PDFs), kiosks, videos, and embedded third-party tools. Private businesses are not directly covered by HB 21-1110, though they remain subject to the ADA and other Colorado civil rights provisions.

Key requirements:
- All covered government entities must bring their websites, web applications, and ICT into conformance with WCAG 2.1 Level AA success criteria, as mandated by Colorado OIT under its Technology Accessibility Rules.
- State agencies were required to submit a written digital accessibility plan to Colorado OIT (via the agency's annual IT Roadmap) by July 1, 2022. Local governments, higher education institutions, and judicial entities are not required to submit plans to OIT but must still develop and implement accessibility plans.
- Entities that qualified for the HB 24-1454 grace period were required to post quarterly progress reports and maintain a process for resolving accessibility complaints during the grace period.
- Colorado OIT must establish and regularly update accessibility standards based on the most recent W3C WCAG guidelines, and may update the required version through rulemaking without new legislation.
- Covered entities must ensure accessibility across all ICT modalities, including digital documents (PDFs, forms), mobile apps, videos (captioning), kiosks, and embedded third-party tools.
- Both public-facing and internal employee-facing digital content and systems must meet the OIT-mandated accessibility standards.
- The May 2025 OIT rules amendment introduced multiple compliance pathways: full WCAG conformance; provision of accessible alternate versions; reasonable accommodations or modifications; or demonstrated good-faith progress with an accessibility plan - giving entities structured options beyond an all-or-nothing standard.
- Entities found liable in civil court are subject to court-ordered remediation and a statutory fine of $3,500 per violation payable to each affected plaintiff, or actual monetary damages if higher, plus attorney's fees.

Key dates:
- July 1, 2022: State agencies must submit a written digital accessibility plan to Colorado OIT as part of the agency's annual IT Roadmap. (Note: local governments, higher education institutions, and judicial entities are not required to file with OIT but must still plan and implement accessibility improvements.)
- July 1, 2024: Original deadline for full WCAG 2.1 AA conformance across all government ICT. Extended to July 1, 2025 for qualifying entities under HB 24-1454 that demonstrated good-faith compliance efforts.
- July 1, 2025: Final enforcement deadline - grace period under HB 24-1454 expired; all covered entities are subject to civil liability for inaccessible government ICT.

Penalties & enforcement: Non-compliant government entities face private civil lawsuits in Colorado state courts brought by individuals with disabilities who experience discrimination due to inaccessible ICT. If found liable, a court may order mandatory remediation of inaccessible digital content and award a statutory fine of $3,500 per violation payable to each affected plaintiff, or actual monetary damages if higher, plus attorney's fees. There is no administrative enforcement by OIT; enforcement is entirely through private right of action - any person with a disability who encounters an inaccessible government digital service may file suit in Colorado state court.

Relation to WCAG: Colorado HB 21-1110 directly mandates conformance with WCAG, directing Colorado OIT to adopt standards based on the most recent guidelines published by the W3C Web Accessibility Initiative. Colorado OIT's current required standard - reaffirmed in its May 2025 amended Technology Accessibility Rules - is WCAG 2.1 Level AA, covering all four principles (Perceivable, Operable, Understandable, and Robust) and their success criteria. OIT has stated it will consider adopting WCAG 2.2 in future rulemaking. The law's forward-looking language requiring adoption of the "most recent" WCAG version means OIT can update the standard without new legislation, keeping Colorado's requirements current with evolving international best practice.

How EqualWeb helps: EqualWeb's AI Accessibility Widget can be deployed on Colorado government websites with a single line of code, automatically remediating up to 95% of common WCAG 2.1 AA issues - depending on how the site is built - in real time - giving agencies a meaningful starting point on their path toward HB 21-1110 compliance from day one. The widget alone does not make a site conformant; achieving WCAG 2.1 AA conformance requires expert review and remediation. For entities that need to reach and certify conformance, EqualWeb's Managed Compliance service pairs certified IAAP/CPWA experts with client-side remediation, continuous monitoring, and delivery of a signed Accessibility Compliance Certificate, a VPAT/Accessibility Conformance Report, and a full evidence pack - supporting the documented compliance posture government entities need to demonstrate good-faith efforts and withstand scrutiny in the event of a civil action. EqualWeb's Continuous Monitoring tool provides a live 0-to-100 compliance score with regression alerts, helping agencies track progress and support their accessibility plan obligations and quarterly reporting requirements. PDF Tools address a common compliance gap for government entities: checking, remediating, and serving accessible PDFs that meet PDF/UA and Section 508 standards - covering the digital documents such as forms, reports, and public notices that HB 21-1110 requires to be accessible. Together, these services give Colorado government entities a structured, evidence-backed path toward the WCAG 2.1 AA conformance that HB 21-1110 demands, without overstating what any single automated tool can achieve on its own.

Q: What is Colorado HB 21-1110?
A: Colorado HB 21-1110, signed into law on June 30, 2021, is a state law requiring all Colorado government entities - state agencies, local governments, school districts, and public universities - to make their websites, apps, and other ICT accessible to people with disabilities. The required technical standard is WCAG 2.1 Level AA as established by Colorado OIT. Full enforcement has been in effect since July 1, 2025.

Q: Who must comply with Colorado HB 21-1110?
A: All Colorado state and local government entities are covered, including executive, legislative, and judicial branch agencies, public K-12 school districts, community colleges, state universities, counties, municipalities, and special districts such as water, fire, and transportation authorities. Private businesses are not directly subject to HB 21-1110, though they face separate obligations under the ADA and other civil rights laws.

Q: What is the compliance deadline for HB 21-1110?
A: The original WCAG conformance deadline was July 1, 2024. A subsequent law, HB 24-1454 (signed May 24, 2024), provided a one-year immunity from liability until July 1, 2025 for entities that demonstrated good-faith compliance efforts, posted quarterly progress reports, and maintained a complaint resolution process. As of July 1, 2025, the grace period has expired and all covered entities are subject to civil enforcement.

Q: What are the penalties for violating Colorado HB 21-1110?
A: Individuals with disabilities who experience discrimination due to inaccessible government ICT may file a private lawsuit in Colorado state court. If a government entity is found liable, a court may order it to remediate the accessibility barriers and pay a statutory fine of $3,500 per violation to each affected plaintiff, or actual monetary damages if higher, plus attorney's fees. Enforcement is entirely through private civil action - there is no administrative penalty from OIT.

Q: Does HB 21-1110 require WCAG 2.1 or WCAG 2.2?
A: Colorado OIT's current mandated standard, reaffirmed in its May 2025 amended Technology Accessibility Rules, is WCAG 2.1 Level AA. OIT has indicated it will consider adopting WCAG 2.2 in a future rulemaking cycle. The law instructs OIT to base its standards on the 'most recent' WCAG published by the W3C, so the required version can be updated through OIT rulemaking without new legislation. Covered entities should monitor OIT guidance for updates.

Q: What compliance pathways does HB 21-1110 allow?
A: The May 2025 OIT rules amendment introduced multiple pathways to compliance: (1) full WCAG 2.1 AA conformance; (2) provision of an equally accessible alternate version of the digital content; (3) reasonable accommodations or modifications; or (4) demonstrated good-faith progress with a documented accessibility plan. Entities must also publish a technology accessibility statement providing at least two contact methods for users to request assistance.

### Accessibility for Ontarians with Disabilities Act (AODA)
URL: https://www.equalweb.com/platform/standards/aoda.html
Region: Canada (Ontario). Governing body: Accessibility Directorate of Ontario, a branch of the Ministry for Seniors and Accessibility, Government of Ontario In effect: June 13, 2005 (Act in force); key web accessibility deadline January 1, 2021.

The Accessibility for Ontarians with Disabilities Act (AODA) is a 2005 Ontario law that requires public-sector organizations and private-sector businesses operating in Ontario to identify, remove, and prevent barriers for people with disabilities across customer service, employment, information and communications, transportation, and the design of public spaces. Its Integrated Accessibility Standards Regulation (Ontario Regulation 191/11) mandates that covered organizations' public-facing websites and web content meet WCAG 2.0 Level AA, with the compliance deadline for large organizations and public bodies having passed on January 1, 2021.

What it is: The Accessibility for Ontarians with Disabilities Act, 2005 (AODA) is Ontario's landmark disability-rights legislation, enacted with the goal of making Ontario fully accessible by January 1, 2025. It empowers the Government of Ontario to develop and enforce binding accessibility standards across five domains: customer service, information and communications, employment, transportation, and design of public spaces. The Act's primary implementing regulation - the Integrated Accessibility Standards Regulation (IASR), Ontario Regulation 191/11 - sets out detailed, time-phased requirements and explicitly references WCAG 2.0 Level AA as the technical benchmark for digital accessibility. Non-compliance with the AODA and its regulations can expose organizations to administrative penalties, Director's Orders, and significant daily fines.

Who must comply: The AODA applies to every person or organization in Ontario that provides goods, services, or facilities to the public or third parties, and that has at least one employee in Ontario - encompassing private businesses, non-profit organizations, the broader public sector (hospitals, schools, universities, municipalities), and the provincial government itself. Web accessibility requirements under the IASR specifically cover designated public-sector organizations of any size and private-sector businesses or non-profits with 50 or more employees in Ontario; organizations with fewer than 50 employees are encouraged but not legally required to meet WCAG 2.0 Level AA for websites under the regulation, though they remain subject to other AODA standards. Organizations with no employees in Ontario are exempt. Mandatory accessibility compliance reporting applies to businesses and non-profits with 20 or more employees, who must file a report every three years.

Key requirements:
- Public websites and web content published after January 1, 2012 must conform to WCAG 2.0 Level AA (with exceptions for live captions and pre-recorded audio descriptions) for organizations with 50 or more employees or in the public sector.
- Organizations must establish, implement, and maintain a written multi-year accessibility plan and review it at least every five years.
- All employees and volunteers must receive accessible customer service training; organizations with 50 or more employees must document their training policy.
- Information and communications - including digital documents, feedback processes, and emergency procedures - must be available in accessible formats upon request.
- Employment practices covering recruitment, retention, accommodation, and career development must be accessible for employees and job applicants with disabilities.
- New or significantly renovated public spaces (recreational trails, service counters, waiting areas, etc.) must meet the AODA Design of Public Spaces Standards.
- Organizations with 20 or more employees must file an Accessibility Compliance Report with the Ontario government on the prescribed schedule (next private-sector deadline: December 31, 2026).

Key dates:
- January 1, 2012: Reference date: web content published on or after this date must meet WCAG 2.0 Level AA for covered organizations.
- January 1, 2014: WCAG 2.0 Level A compliance required for large organizations (50+ employees) and public-sector bodies; initial accessibility compliance reports due December 31, 2014 for organizations with 20+ employees.
- January 1, 2021: Full WCAG 2.0 Level AA compliance deadline for all public websites and web content: public-sector organizations of any size and private/non-profit organizations with 50 or more employees.
- December 31, 2025: Mandatory Accessibility Compliance Report filing deadline for designated public-sector organizations.
- December 31, 2026: Next mandatory Accessibility Compliance Report filing deadline for private-sector businesses and non-profits with 20 or more employees.

Penalties & enforcement: Under the AODA, individuals and unincorporated organizations found in violation face fines of up to $50,000 per day, while corporations face fines of up to $100,000 per day; directors and officers of a corporation may also be personally fined up to $50,000 per day. Enforcement follows a graduated process administered by the Accessibility Directorate of Ontario: a notice of non-compliance is issued first, followed by a Director's Order if corrective action is not taken, and administrative monetary penalties or prosecution for persistent violations. Complaints from individuals with disabilities can be filed directly with the Ontario government, and organizations that fail to submit mandatory compliance reports are also subject to enforcement action.

Relation to WCAG: The AODA's Integrated Accessibility Standards Regulation (Ontario Regulation 191/11) explicitly mandates WCAG 2.0 Level AA as the technical standard for public websites and web content, requiring compliance with all Level A and Level AA success criteria except for two specific provisions: Success Criterion 1.2.4 (Captions - Live) and Success Criterion 1.2.5 (Audio Description - Prerecorded). While newer WCAG versions (2.1 and 2.2) are not yet formally required under the IASR, organizations are encouraged to adopt them as they provide stronger protection for users with cognitive, motor, and low-vision disabilities. Aligning with WCAG 2.1 or 2.2 Level AA is increasingly considered best practice and can support compliance with Canada's broader Accessible Canada Act (ACA), which references EN 301 549 and incorporates WCAG 2.1, suggesting an upward trajectory for Canadian accessibility requirements.

How EqualWeb helps: EqualWeb's AI Accessibility Widget can be deployed on Ontario-based websites with a single line of code, automatically remediating up to 95% of common WCAG 2.0 Level AA issues - depending on how the site is built - in real time - directly addressing the technical web-content requirements at the core of the AODA's Information and Communications Standards. For organizations requiring full, auditable conformance (and the documented evidence trail that AODA compliance reporting demands), EqualWeb's Managed Compliance service pairs certified IAAP/CPWA accessibility experts with continuous client-side remediation, delivering a signed Accessibility Compliance Certificate and a VPAT/Accessibility Conformance Report that support regulatory submissions and demonstrate good-faith compliance efforts to the Accessibility Directorate of Ontario. EqualWeb's Continuous Monitoring provides a live 0-100 compliance score with regression alerts, helping organizations maintain WCAG 2.0 Level AA conformance on an ongoing basis rather than treating it as a one-time exercise - critical given that AODA compliance reporting is a recurring obligation. The PDF Tools module checks and remediates organizational documents for accessibility, supporting the AODA's broader requirement that information be available in accessible formats on request. Together, these capabilities help Ontario organizations work toward meeting - and maintaining - their AODA digital accessibility obligations in a structured, evidence-based manner.

Q: What is the AODA and what does it require?
A: The Accessibility for Ontarians with Disabilities Act (AODA) is an Ontario law that obligates organizations operating in the province to remove barriers for people with disabilities across customer service, employment, information and communications, transportation, and public spaces. For digital properties, the Integrated Accessibility Standards Regulation requires covered organizations to make public websites and web content conform to WCAG 2.0 Level AA. The Act also mandates written accessibility plans, accessible employment practices, and regular compliance reporting.

Q: Who must comply with the AODA?
A: The AODA applies to any person or organization with at least one employee in Ontario that provides goods, services, or facilities to the public. Website accessibility obligations specifically apply to public-sector organizations of any size and to private businesses or non-profits with 50 or more employees in Ontario. Smaller private-sector organizations (fewer than 50 employees) are not legally required to meet WCAG 2.0 Level AA for their websites under the IASR but remain subject to other AODA standards such as accessible customer service.

Q: What is the AODA web accessibility deadline?
A: The primary web accessibility deadline under the AODA passed on January 1, 2021, by which date all public-sector organizations and private/non-profit organizations with 50 or more employees were required to have their public-facing websites and web content meet WCAG 2.0 Level AA. Looking ahead, organizations subject to mandatory compliance reporting must note that private-sector businesses and non-profits with 20 or more employees must file their next Accessibility Compliance Report by December 31, 2026, and designated public-sector organizations had a filing deadline of December 31, 2025.

Q: What are the AODA penalties for non-compliance?
A: The AODA imposes significant financial penalties: up to $100,000 per day for corporations and up to $50,000 per day for individuals, unincorporated organizations, or corporate directors and officers. Enforcement by the Accessibility Directorate of Ontario is progressive - beginning with a notice of non-compliance, escalating to a Director's Order, and potentially resulting in formal prosecution for persistent or egregious violations. Failure to file a required Accessibility Compliance Report is itself a violation subject to these penalties.

Q: Does the AODA require WCAG 2.1 or WCAG 2.2?
A: No - the AODA's Integrated Accessibility Standards Regulation currently requires WCAG 2.0 Level AA, not the newer 2.1 or 2.2 versions. However, adopting WCAG 2.1 or 2.2 Level AA is strongly recommended as a forward-looking best practice, as these versions address additional barriers for users with cognitive, low-vision, and motor disabilities. Canada's federal Accessible Canada Act (ACA) and its associated standard reference EN 301 549, which incorporates WCAG 2.1, suggesting an upward trajectory for Canadian accessibility requirements.

### Accessible Canada Act (ACA)
URL: https://www.equalweb.com/platform/standards/aca.html
Region: Canada. Governing body: Employment and Social Development Canada (ESDC) issues regulations for most sectors; the Accessibility Commissioner (operating within the Canadian Human Rights Commission) monitors compliance and enforces the Act for ESDC-regulated sectors; the Canadian Radio-television and Telecommunications Commission (CRTC) enforces accessibility requirements for broadcasting and telecommunications; and the Canadian Transportation Agency (CTA) enforces requirements for federally regulated transportation. Accessibility Standards Canada (ASC, formerly CASDO) develops the technical accessibility standards - including CAN/ASC-EN 301 549 - that underpin the digital technology regulations. In effect: July 11, 2019 (Royal Assent June 21, 2019); Digital Technologies Accessibility Regulations registered December 5, 2025 (SOR/2025-255), with compliance deadlines phasing in from December 5, 2027 to December 5, 2028..

The Accessible Canada Act (ACA) is a federal statute enacted in Canada in 2019 that requires federally regulated organizations to identify, remove, and prevent barriers to accessibility across seven priority areas, with a legislated goal of making Canada barrier-free by January 1, 2040. Regulations registered in December 2025 (SOR/2025-255) add binding ICT technical requirements referencing CAN/ASC-EN 301 549:2024, which incorporates WCAG 2.1 Level AA, with digital compliance deadlines staggered between December 5, 2027 (federal public sector, web pages) and December 5, 2028 (private sector and all mobile/document obligations).

What it is: The Accessible Canada Act (S.C. 2019, c. 10) is Canada's first proactive federal accessibility law, applying to all organizations under federal jurisdiction. It mandates the systematic identification, removal, and prevention of barriers in seven priority areas: the built environment; employment; information and communication technologies (ICT); communication other than ICT; the procurement of goods, services, facilities, and premises; the design and delivery of programs and services; and transportation. The Act established Accessibility Standards Canada (ASC) to develop technical standards and the office of the Accessibility Commissioner within the Canadian Human Rights Commission to investigate complaints and enforce compliance for ESDC-regulated entities. The overarching statutory objective is a barrier-free Canada by January 1, 2040.

Who must comply: The ACA applies to federally regulated entities, including the Government of Canada, Parliament, Crown corporations, and federally regulated private-sector organizations in banking, telecommunications, broadcasting, and interprovincial transportation. For digital technology obligations under the December 2025 regulations: federal public-sector entities must meet web-page requirements by December 5, 2027 and mobile/document requirements by December 5, 2028; large private-sector entities (500 or more employees) must meet web, mobile, and digital-document requirements by December 5, 2028; medium private-sector entities (100-499 employees) must meet employee-facing web-page requirements by December 5, 2028, but are not yet subject to requirements for public-facing pages, mobile apps, or digital documents in this phase. For accessibility planning, organizations with 10 or more employees must publish accessibility plans; those with fewer than 10 employees are exempt from planning and reporting requirements. The Act does not directly regulate provincially regulated businesses, though provinces such as Ontario have parallel legislation (e.g., AODA).

Key requirements:
- Publish an accessibility plan describing how the organization will identify, remove, and prevent barriers, updated on a three-year cycle.
- Establish and maintain a feedback process allowing persons with disabilities to comment on accessibility barriers, and report on feedback received.
- Submit progress reports to the relevant regulator (Accessibility Commissioner, CRTC, or CTA) between accessibility plan updates.
- Notify the Accessibility Commissioner (or sector regulator) within 48 hours of publishing any accessibility plan, feedback-process description, or progress report, via the My Accessibility Portal.
- Conform to CAN/ASC-EN 301 549:2024 for web pages, mobile applications, and digital documents by the applicable sector-specific deadlines in 2027-2028 (scope of obligations varies by entity type and size - see deadlines).
- Provide digital accessibility training on accessibility fundamentals to all staff involved in developing, maintaining, or procuring digital technologies by December 5, 2027 (public sector and all private entities with 100+ employees), with refreshers at least once every three years.
- For large entities (500+ employees): conduct conformity assessments when procuring ICT products and services, and retain accessibility documentation for at least four years.
- Publish annual accessibility statements describing the entity's digital accessibility posture once digital obligations take effect.

Key dates:
- December 31, 2022: Federal government, Crown corporations, Parliament, RCMP, and Canadian Forces must publish first accessibility plans.
- June 1, 2023: Large private-sector organizations (100 or more employees) must publish first accessibility plans.
- June 1, 2024: Small private-sector organizations (10-99 employees) must publish first accessibility plans.
- December 5, 2027: Federal public-sector entities must achieve conformity with CAN/ASC-EN 301 549:2024 for employee-facing and public-facing web pages; all entities with 100+ employees must complete mandatory digital accessibility training for relevant staff.
- December 5, 2028: Federal public-sector entities must achieve conformity for mobile applications and non-web documents. Large private-sector entities (500+ employees) must achieve conformity for public-facing web pages, mobile applications, and digital documents available for download, and must conduct accessibility conformity assessments for procured ICT. Medium private-sector entities (100-499 employees) must achieve conformity for employee-facing web pages (public-facing pages, mobile apps, and documents are not required in this phase).

Penalties & enforcement: Administrative monetary penalties under the ACA range from CAD $250 to $250,000 per violation, with the actual amount within that range determined by the severity classification (minor, serious, or very serious), the size of the organization, and the number of prior violations. For large regulated entities (100 or more employees), minor violations can attract penalties from $1,000 up to $75,000; serious violations from $10,000 up to $150,000; and very serious violations - such as obstructing an investigation or providing false information - from $25,000 up to $250,000. Smaller entities and individuals face lower maxima within the same tiers. The Accessibility Commissioner may issue warnings, compliance orders, compliance agreements, or notices of violation before escalating to financial penalties, and considers factors such as prior history of non-compliance, harm caused, and remediation efforts when setting amounts. Importantly, the December 2025 digital-technology regulations classify non-conformance with the ICT standard as a "minor" violation, meaning the relevant financial exposure sits at the lower end of the penalty range for an initial violation.

Relation to WCAG: The ACA's technical digital accessibility requirements are set by the Digital Technologies Accessibility Regulations (SOR/2025-255, registered December 5, 2025), which reference CAN/ASC-EN 301 549:2024 - Canada's national adoption of the European standard EN 301 549 - on an ambulatory basis, meaning the regulations automatically incorporate future updates to the standard as they are published. CAN/ASC-EN 301 549:2024 incorporates WCAG 2.1 Level AA as its core web and non-web software accessibility requirement (via clauses 9 and 10 of the standard), and also applies additional requirements for mobile applications, hardware, and ICT services beyond WCAG's web scope. An update to EN 301 549 incorporating WCAG 2.2 is anticipated in 2026; because Canada adopted the standard on an ambulatory basis, organizations are well advised to target WCAG 2.2 Level AA now to reduce remediation rework when the updated edition takes effect.

How EqualWeb helps: EqualWeb's AI Accessibility Widget can be deployed on any federally regulated organization's website with a single line of code, automatically remediating up to 95% of common WCAG 2.1 Level AA issues - depending on how the site is built - in real time - helping organizations work toward the CAN/ASC-EN 301 549:2024 web conformance obligations that take effect under the ACA in 2027-2028. The widget alone does not constitute conformance; organizations seeking to meet the Act's complete digital conformance requirements and to obtain the documented evidence the regulations demand should consider EqualWeb's Managed Compliance service, which pairs IAAP/CPWA-certified experts with client-side remediation, continuous monitoring, and a signed Accessibility Compliance Certificate along with a VPAT/Accessibility Conformance Report - the kind of auditable evidence pack that supports accountability to the Accessibility Commissioner. EqualWeb's Continuous Monitoring provides a live 0-100 compliance score and regression alerts, helping organizations maintain their accessibility posture between the mandatory three-year accessibility plan cycles and annual progress reporting the ACA requires. For large entities (500 or more employees) subject to document obligations, EqualWeb's PDF Tools address PDF/UA conformance, a requirement under CAN/ASC-EN 301 549:2024 clause 10 for digital documents available for download. Taken together, the EqualWeb platform is designed to help federally regulated organizations work toward the documented, verifiable, and maintained conformance the ACA and its 2027-2028 digital deadlines demand.

Q: Who must comply with the Accessible Canada Act?
A: Any organization under federal jurisdiction must comply, including the Government of Canada, Parliament, Crown corporations, and federally regulated private-sector entities in banking, telecommunications, broadcasting, and interprovincial transportation. For accessibility planning, organizations with 10 or more employees must publish accessibility plans; those with fewer than 10 employees are exempt. For digital technology obligations under the 2025 regulations, the scope depends on size: federal public-sector entities and private-sector entities with 100 or more employees have obligations, though the specific requirements differ - large entities (500+ employees) face the broadest digital obligations. Provincially regulated businesses are not directly covered by the ACA, though they may be subject to provincial laws such as Ontario's AODA.

Q: What are the digital accessibility deadlines under the ACA?
A: The Digital Technologies Accessibility Regulations (registered December 5, 2025) set phased deadlines. Federal public-sector entities must conform to CAN/ASC-EN 301 549:2024 for web pages by December 5, 2027, and for mobile applications and non-web documents by December 5, 2028. Private-sector entities with 500 or more employees must conform for public-facing web pages, mobile applications, and downloadable digital documents by December 5, 2028. Medium-sized private entities (100-499 employees) must conform for employee-facing web pages by December 5, 2028, but are not yet subject to mobile app or document requirements in this regulatory phase. Training obligations for staff involved in digital technologies apply to all entities with 100 or more employees by December 5, 2027.

Q: What WCAG version does the Accessible Canada Act require?
A: The ACA's digital requirements reference CAN/ASC-EN 301 549:2024, which currently incorporates WCAG 2.1 Level AA as the web accessibility benchmark. The standard is adopted on an ambulatory basis, so it will automatically incorporate future updates; the anticipated revision to EN 301 549 is expected to bring in WCAG 2.2 Level AA. Organizations are advised to target WCAG 2.2 Level AA proactively to reduce future remediation costs when the standard is updated.

Q: What are the penalties for non-compliance with the ACA?
A: The Accessibility Commissioner can impose administrative monetary penalties ranging from CAD $250 to $250,000 per violation, depending on severity, organization size, and prior violation history. For large regulated entities, minor violations (including ICT non-conformance) can attract penalties up to $75,000, serious violations up to $150,000, and very serious violations such as obstructing an investigation up to $250,000. The enforcement approach typically begins with warnings and compliance orders before financial penalties are levied.

Q: Does the ACA require an accessibility plan?
A: Yes. All covered organizations with 10 or more employees must prepare and publish an accessibility plan describing how they will identify, remove, and prevent barriers across the seven priority areas defined in the Act, including ICT, employment, and the built environment. Plans must be updated every three years, and organizations must publish progress reports in the intervening years. All plans and reports must be submitted to the relevant regulator (Accessibility Commissioner, CRTC, or CTA) within 48 hours of publication via the My Accessibility Portal.

### EN 301 549
URL: https://www.equalweb.com/platform/standards/en-301549.html
Region: European Union. Governing body: EN 301 549 is jointly produced by three European Standards Organisations (ESOs) - ETSI (European Telecommunications Standards Institute), CEN (European Committee for Standardisation), and CENELEC (European Committee for Electrotechnical Standardisation) - under mandate from the European Commission. Legal force derives from its harmonisation under the Web Accessibility Directive (Directive (EU) 2016/2102) and the European Accessibility Act (Directive (EU) 2019/882). In effect: June 28, 2025 (EAA private-sector enforcement); public-sector websites from September 23, 2020; public-sector mobile apps from June 23, 2021.

EN 301 549 is the harmonised European Standard that specifies functional accessibility requirements for information and communications technology (ICT) products and services - including websites, mobile apps, software, hardware, documents, and telecommunications - sold or provided within the European Union. Developed jointly by ETSI, CEN, and CENELEC, it serves as the technical benchmark for compliance with both the EU Web Accessibility Directive and the European Accessibility Act.

What it is: EN 301 549 (full title: "Accessibility requirements for ICT products and services") is a harmonised European Standard that defines measurable technical and functional accessibility criteria for the full range of ICT - spanning websites, native mobile applications, desktop software, operating systems, hardware devices, self-service terminals, telecommunications services, and electronic documents. First published in 2014, it incorporates the complete text of WCAG 2.1 Level AA as the web and mobile content baseline. Conformance with EN 301 549 creates a legal "presumption of conformity" under both the Web Accessibility Directive and the European Accessibility Act, making it the definitive technical reference for digital accessibility compliance across the EU. ETSI, CEN and CENELEC maintain the standard and update it periodically; a revised edition expected to incorporate WCAG 2.2 AA is anticipated to be referenced in the Official Journal of the European Union in October 2026.

Who must comply: EN 301 549 applies to two broad groups. First, all public-sector bodies in EU member states - including central government, regional and local authorities, universities, hospitals, and public broadcasters - must meet the standard for their websites and mobile applications under the Web Accessibility Directive. Second, private-sector organisations offering consumer-facing products and services in the EU - including e-commerce platforms, banking and financial services, transport operators, e-books and audiovisual media services, and consumer electronics manufacturers - must comply under the European Accessibility Act, which became enforceable on June 28, 2025. The standard also functions as the mandatory technical specification for public procurement of ICT across EU member states, meaning any company bidding for government ICT contracts must demonstrate conformance.

Key requirements:
- Web content (Chapter 9): All public-facing websites and web applications must meet WCAG 2.1 Level AA in full - covering perceivability, operability, understandability, and robustness.
- Non-web software (Chapter 11): Desktop applications, mobile apps, and operating systems must meet equivalent accessibility criteria, including keyboard accessibility and compatibility with platform assistive technologies.
- Non-web documents (Chapter 10): Electronic documents - PDFs, Word files, spreadsheets, and presentations - must meet adapted WCAG 2.1 criteria including logical reading order, tagged structure, text alternatives, and accessible forms.
- Two-way voice communication (Chapter 6): ICT providing real-time voice calls must also support Real-Time Text (RTT), enabling users who cannot use voice to communicate concurrently in text over the same connection.
- Hardware (Chapter 8): Physical ICT products - including self-service terminals, kiosks, and consumer hardware - must provide operable controls without requiring gripping or twisting, adequate contrast, and connections for assistive devices.
- Documentation and support services (Chapter 12): User documentation, help content, and support services (including call centres and chat) must themselves be accessible and available in accessible formats.
- Authoring tools (Chapter 11.8): Software used to create digital content must support the production of accessible output and guide authors toward accessibility best practices.

Key dates:
- September 23, 2019: EU public-sector websites published after September 23, 2018 must meet EN 301 549 (Web Accessibility Directive)
- September 23, 2020: All EU public-sector websites (including older sites) must meet EN 301 549
- June 23, 2021: All EU public-sector mobile applications must meet EN 301 549
- June 28, 2025: European Accessibility Act enforcement begins: private-sector products and services placed on the EU market must conform with EN 301 549
- October 2026 (expected): A revised edition of EN 301 549 (incorporating WCAG 2.2 AA) anticipated to be referenced in the Official Journal of the EU, replacing the current harmonised edition

Penalties & enforcement: Penalties for non-compliance are set by each EU member state individually rather than by the EU centrally, and enforcement began actively in mid-to-late 2025. Under the European Accessibility Act framework, member states have established fines and enforcement mechanisms that vary by jurisdiction: Germany applies administrative fines up to €100,000 per violation and enforcement authorities may order non-compliant products or services removed from the German market; France applies fines up to approximately €250,000-€300,000 with additional annual penalties for missing accessibility statements; the Netherlands applies fines that some sources cite as up to €103,000 and others cite as up to €900,000 or 10% of annual turnover. Enforcement authorities across member states may also require non-compliant products or services to be corrected within a stated deadline or withdrawn from the market. Ireland is notable for permitting criminal penalties: on summary conviction, fines up to €5,000 and/or imprisonment up to 6 months; on conviction on indictment, fines up to €60,000 and/or imprisonment up to 18 months for directors, managers, and officers.

Relation to WCAG: EN 301 549 (the current enforceable edition) incorporates the full text of WCAG 2.1 Level AA in Chapter 9 for web content and applies equivalent criteria in Chapters 10 and 11 for documents and non-web software, meaning WCAG 2.1 AA conformance is a necessary - but not sufficient - component of EN 301 549 compliance. The standard extends beyond WCAG's web focus to cover hardware, telecommunications, real-time text, and authoring tools, areas WCAG does not address. A forthcoming revision (expected to be harmonised in October 2026) will upgrade the baseline to WCAG 2.2 Level AA, adding criteria such as focus appearance, dragging movements, and accessible authentication.

How EqualWeb helps: EqualWeb's AI Accessibility Widget addresses the WCAG 2.1 Level AA layer of EN 301 549 directly: a single line of code auto-remediates up to 95% of common WCAG 2.1 issues - depending on how the site is built - in real time on the client side and provides a profile-based accessibility menu, giving organisations a strong foundation toward the web-content requirements of Chapter 9. For organisations that need to demonstrate conformance - as required when the EAA's "presumption of conformity" standard applies - EqualWeb's Managed Compliance service pairs certified IAAP/CPWA experts with client-side remediation, continuous monitoring, and a signed Accessibility Compliance Certificate alongside a VPAT/Accessibility Conformance Report and evidence pack, supporting the path to full, certified EN 301 549 conformance. Because EN 301 549 also applies to electronic documents (Chapter 10), EqualWeb's PDF Tools check, remediate, and serve accessible PDFs conforming to PDF/UA, directly supporting that clause of the standard. EqualWeb's Accessibility Testing suite - including its checker, crawler, and live 0-100 compliance score with regression alerts - provides the ongoing monitoring evidence that regulators and procurement bodies increasingly expect as proof of sustained EN 301 549 conformance across a digital estate.

Q: Is EN 301 549 the same as WCAG?
A: No, but EN 301 549 incorporates WCAG 2.1 Level AA as its web-content baseline (in Chapter 9). EN 301 549 is broader in scope: it also covers hardware, software applications, electronic documents, telecommunications, self-service terminals, and support services - areas that WCAG does not address. Meeting WCAG 2.1 AA is necessary for EN 301 549 web compliance but does not constitute full EN 301 549 conformance.

Q: Who must comply with EN 301 549 in 2025 and 2026?
A: All EU public-sector bodies (government websites and apps) have been required to comply since 2020-2021 under the Web Accessibility Directive. From June 28, 2025, private-sector businesses offering consumer products and services in the EU - including e-commerce, banking, transport, and consumer electronics - must also comply under the European Accessibility Act. Companies bidding on EU public ICT procurement contracts must demonstrate conformance as well.

Q: What are the penalties for not complying with EN 301 549?
A: Penalties are determined by each EU member state and vary significantly. Germany applies per-violation fines up to €100,000; France applies fines up to approximately €250,000-€300,000 with additional annual penalties for missing accessibility statements; the Netherlands applies fines up to €103,000 or higher depending on jurisdiction. Authorities may also order market withdrawal of non-compliant products. Ireland is the only member state that currently allows criminal penalties, including imprisonment - up to 6 months on summary conviction and up to 18 months on conviction on indictment.

Q: Is EN 301 549 regularly updated?
A: Yes. EN 301 549 is maintained jointly by ETSI, CEN and CENELEC and is updated periodically to stay current with technology and with WCAG's own evolution. A revised edition incorporating WCAG 2.2 AA is expected to be referenced in the Official Journal of the EU in 2026. For the current published edition, see ETSI's EN 301 549 standard page.

Q: Does EN 301 549 apply to PDFs and mobile apps?
A: Yes. Chapter 10 of EN 301 549 applies adapted WCAG 2.1 success criteria to electronic documents, including PDFs, Word files, spreadsheets, and presentations - requiring tagged structure, text alternatives, correct reading order, and accessible forms. Chapter 11 applies equivalent requirements to non-web software including native iOS and Android mobile apps, desktop applications, and operating systems.

### European Accessibility Act (EAA)
URL: https://www.equalweb.com/platform/standards/eaa.html
Region: European Union. Governing body: European Parliament and Council of the European Union (Directive (EU) 2019/882); enforcement delegated to designated national market surveillance and enforcement authorities in each of the 27 EU Member States. In effect: June 28, 2025.

The European Accessibility Act (EAA) is Directive (EU) 2019/882, a binding EU law that requires key products and services - including e-commerce, banking, telecommunications, and digital media - sold or provided to consumers in the European Union to meet defined accessibility standards. It became enforceable on June 28, 2025, applying to all covered businesses regardless of where they are headquartered.

What it is: The European Accessibility Act (EAA), formally Directive (EU) 2019/882, is a landmark piece of EU legislation that establishes harmonized accessibility requirements for a broad range of consumer-facing products and services across all 27 Member States. It was adopted on April 17, 2019, to eliminate the fragmentation caused by differing national accessibility rules and to create a level playing field in the EU single market. The EAA's technical requirements for digital products and services are operationalized through EN 301 549, the harmonized European standard, which incorporates WCAG 2.1 Level AA for web and software content. The Act is grounded in the UN Convention on the Rights of Persons with Disabilities (UNCRPD) and treats accessible design as a fundamental rights obligation, not merely a best practice.

Who must comply: The EAA applies to any manufacturer, importer, distributor, or service provider placing in-scope products on the EU market or offering in-scope services to consumers within the EU - regardless of whether the business is headquartered inside or outside the European Union. Covered sectors include e-commerce platforms, online banking and payment services, electronic communications, audiovisual media services, transport ticketing and information systems, e-books and e-readers, computers, smartphones, tablets, and self-service terminals such as ATMs and ticketing kiosks. The sole categorical exemption is for microenterprises providing services - defined as fewer than 10 employees and no more than €2 million annual turnover - although microenterprises that manufacture or distribute covered products remain subject to product requirements. Larger businesses may invoke a limited "disproportionate burden" exception only where compliance would require a fundamental alteration of a product or service, but this must be documented and justified.

Key requirements:
- Digital products and services must be perceivable, operable, understandable, and robust - aligned with WCAG 2.1 Level AA as referenced through EN 301 549.
- E-commerce websites and apps must provide accessible product information, purchasing flows, electronic payment, and order confirmation.
- Banking and financial services must make websites, mobile apps, and electronic documents accessible to users with disabilities.
- Telecommunications providers must ensure voice, messaging, and emergency service interfaces are accessible.
- Self-service terminals (ATMs, ticketing machines, check-in kiosks) must meet hardware and software accessibility requirements.
- Audiovisual media service platforms must provide accessible interfaces and support for captions, audio description, and signing services.
- Economic operators must maintain technical documentation, issue a declaration of conformity, and cooperate with national market surveillance authorities on request.

Key dates:
- June 28, 2022: Deadline for EU Member States to transpose the EAA into national law.
- June 28, 2025: Primary enforcement date: all new in-scope products placed on the market and new in-scope services launched after this date must comply.
- June 28, 2030: Final transitional deadline: existing services (and products already on the market before June 28, 2025) must achieve full compliance by this date.
- Up to 20 years after entry into use: Self-service terminals lawfully in use before June 28, 2025 may continue operating until end of economic life, capped at 20 years from deployment.

Penalties & enforcement: The EAA does not prescribe a single EU-wide penalty scale; instead it requires each Member State to establish penalties that are "effective, proportionate, and dissuasive." Administrative fines vary significantly by country. Spain and Sweden can impose fines reaching €1,000,000 for serious infringements. Germany provides fines up to €100,000 for selling non-compliant products and up to €10,000 for failure to provide accurate accessibility information. France's base penalty is €7,500 per offence for legal entities (doubling to €15,000 for repeat offenders), but aggregate penalties for systemic non-compliance can reach €250,000. Enforcement authorities may also order withdrawal of non-compliant products from the market, prohibit services from being offered, mandate accessibility audits, and publicly disclose non-compliance. Ireland is currently the only Member State that additionally provides for criminal penalties, including imprisonment, for serious violations. Some countries also allow daily fines - typically around €1,000 per day - until compliance is achieved. Beyond regulatory action, consumers and disability organizations in many Member States may bring complaints or civil proceedings.

Relation to WCAG: The EAA does not cite WCAG directly in its legislative text; instead it instructs the European Commission to mandate harmonized standards, and EN 301 549 (the applicable harmonized European ICT accessibility standard) serves as the presumed conformance pathway. EN 301 549 incorporates WCAG 2.1 Level AA in full for web content, mobile apps, and non-web software - meaning that meeting WCAG 2.1 AA is a necessary component of EAA compliance for digital products and services. A future revision of EN 301 549, planned for 2026, is expected to incorporate WCAG 2.2 AA, but WCAG 2.2 is not yet mandated by the current standard. Organizations that have already implemented WCAG 2.2 AA will satisfy and exceed the WCAG-related requirements of the current EN 301 549. WCAG conformance alone is not sufficient: EN 301 549 adds requirements for hardware, telecommunications, two-way voice communication, documentation, and support services that go beyond the web-focused WCAG criteria.

How EqualWeb helps: EqualWeb's AI Accessibility Widget provides a one-line installation that automatically remediates up to 95% of common WCAG 2.1 AA issues - depending on how the site is built - in real time - directly addressing the EN 301 549 web-content requirements that underpin EAA compliance and giving organizations a measurable starting point quickly. The widget alone does not constitute conformance; it works toward compliance by handling a significant share of common issues automatically, with a profile-based accessibility menu that further supports users with disabilities. For businesses that need to demonstrate certified conformance ahead of national enforcement action, EqualWeb's Managed Compliance service pairs certified IAAP/CPWA accessibility experts with ongoing client-side remediation, producing a signed Accessibility Compliance Certificate, a VPAT/Accessibility Conformance Report, and a complete evidence pack that can be presented to market surveillance authorities. Continuous Monitoring provides a live 0-100 compliance score with regression alerts, so that a site or app does not slip out of conformance after initial remediation - a critical safeguard given that the EAA requires ongoing accessibility, not just a one-time audit. EqualWeb's PDF Tools address the EAA's reach into electronic documents, checking and remediating PDFs to PDF/UA and Section 508 standards so that product information sheets, terms and conditions, and service documentation meet accessibility requirements alongside the web interface. Together, these capabilities support organizations in building and maintaining the documented, evidence-based compliance posture that EAA national enforcement authorities expect.

Q: What is the European Accessibility Act and what does it require?
A: The European Accessibility Act (EAA) is Directive (EU) 2019/882, an EU law that mandates accessible design for key consumer-facing products and services - including e-commerce, banking, telecoms, and digital media - across all 27 Member States. It requires businesses to meet the technical requirements in EN 301 549, which incorporates WCAG 2.1 Level AA for digital content. Compliance has been legally required for new products and services since June 28, 2025.

Q: Who has to comply with the European Accessibility Act?
A: Any business that sells or provides in-scope products or services to consumers in the EU must comply, regardless of where the business is based. This includes non-EU companies with EU customers. The only blanket exemption is for microenterprises (fewer than 10 employees and annual turnover of no more than €2 million) that provide services; microenterprises manufacturing or distributing covered products still have obligations.

Q: What is the EAA compliance deadline?
A: The primary enforcement date was June 28, 2025, from which all new covered products placed on the market and new services launched must comply. Existing services and products already on the market before that date have a transitional period until June 28, 2030. Self-service terminals already in use may continue operating until the end of their economic life, up to a maximum of 20 years from deployment.

Q: What are the penalties for not complying with the EAA?
A: Penalties are set by each EU Member State and vary considerably. Spain and Sweden can impose fines up to €1,000,000 for serious violations. Germany provides fines up to €100,000 for non-compliant products. France can reach €250,000 for systemic non-compliance. Enforcement authorities may also order market withdrawal of non-compliant products, prohibit services, or mandate audits. Ireland additionally allows criminal penalties including imprisonment for serious non-compliance. Some countries also impose daily fines until compliance is achieved.

Q: Does the EAA require WCAG 2.1 AA or WCAG 2.2?
A: The EAA's current presumed conformance standard, EN 301 549, incorporates WCAG 2.1 Level AA for web and software content - not WCAG 2.2. A forthcoming revision, expected in 2026, is planned to incorporate WCAG 2.2 AA, but it is not yet the required standard. Organizations that have already implemented WCAG 2.2 AA will satisfy and exceed the WCAG-related requirements of EN 301 549 today. EN 301 549 also adds requirements beyond WCAG for hardware, telecommunications, and other ICT components.

### UK Equality Act 2010
URL: https://www.equalweb.com/platform/standards/uk-equality-act.html
Region: United Kingdom. Governing body: Equality and Human Rights Commission (EHRC) - the statutory body responsible for enforcing the Equality Act 2010 in England, Scotland, and Wales. The Equality Commission for Northern Ireland (ECNI) holds equivalent powers in Northern Ireland. The Act itself was passed by the UK Parliament and is administered by the Government Equalities Office (now the Office for Equality and Opportunity). In May 2026, the EHRC laid a new Draft Code of Practice for Services, Public Functions and Associations before Parliament, updating the 2011 Code to reflect legal developments and reinforcing guidance on disability and reasonable adjustments. In effect: 1 October 2010 (main provisions); Public Sector Equality Duty: 5 April 2011.

The UK Equality Act 2010 is a comprehensive anti-discrimination law that consolidates over 100 previous UK equality statutes into a single legal framework, prohibiting discrimination against people with protected characteristics - including disability - in employment, education, and the provision of goods and services. Under Section 20, all service providers, both public and private, are legally required to make proactive "reasonable adjustments" to ensure disabled people can access their services, which courts and regulators have consistently interpreted to include websites, mobile applications, and other digital channels.

What it is: The Equality Act 2010 (EQA) is the primary equality and anti-discrimination legislation in Great Britain, receiving Royal Assent on 8 April 2010 with most substantive provisions coming into force on 1 October 2010. It consolidates and replaces over 100 earlier Acts, regulations, and statutory instruments - including the Disability Discrimination Act 1995 - into one unified framework covering nine protected characteristics: age, disability, gender reassignment, marriage and civil partnership, pregnancy and maternity, race, religion or belief, sex, and sexual orientation. For digital accessibility, the most operationally significant provision is the anticipatory and proactive duty in Section 20 to make reasonable adjustments, which requires organisations to remove barriers before a disabled person is actually disadvantaged, not merely in response to individual complaints. The Act applies throughout England, Scotland, and Wales; Northern Ireland retains parallel provisions under the Disability Discrimination Act 1995 as amended. In May 2026, the EHRC laid an updated statutory Code of Practice for Services, Public Functions and Associations before Parliament, strengthening practical guidance on disability-related reasonable adjustments.

Who must comply: The Equality Act 2010 applies to virtually every organisation that provides goods, facilities, or services to the public in Great Britain, regardless of size or sector - including retailers, financial services firms, hospitality businesses, healthcare providers, charities, educational institutions, and public bodies. Employers of any size must also comply with disability-related reasonable adjustment duties toward their employees and job applicants. Website and app owners serving users in the UK are considered service providers under the Act, meaning their digital channels must be accessible to disabled users under the reasonable adjustments duty. Public sector bodies face an additional, overlapping obligation under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, which explicitly require conformance with WCAG 2.2 Level AA as the current minimum technical standard.

Key requirements:
- Make reasonable adjustments proactively and in advance: the duty is anticipatory, not reactive - service providers must not wait for a disabled person to complain before addressing accessibility barriers.
- Remove or alter physical features, practices, policies, and procedures that place disabled people at a substantial disadvantage compared to non-disabled people (Sections 20-21).
- Provide auxiliary aids and services - including accessible digital formats, screen-reader-compatible content, and alternative-text descriptions for images - where their absence would disadvantage disabled users.
- Ensure websites and mobile applications are navigable without a mouse (keyboard accessibility), have sufficient colour contrast, and use proper semantic markup so assistive technologies can interpret content correctly.
- Do not treat a disabled person less favourably because of something arising in consequence of their disability, unless the treatment can be objectively justified (Section 15, discrimination arising from disability).
- Public sector bodies must additionally publish a written accessibility statement and demonstrate compliance against WCAG 2.2 Level AA under the Public Sector Bodies Accessibility Regulations 2018.
- Employers must make reasonable adjustments for disabled employees and job applicants, including adaptations to digital workplace tools, intranets, and HR systems.

Penalties & enforcement: Individuals who experience disability discrimination may bring civil claims in the county court (for service-provider complaints) or employment tribunal (for workplace complaints), and there is no statutory cap on compensation - courts may award damages for financial loss, injury to feelings, and in egregious cases, aggravated damages. Injury-to-feelings awards follow the Vento bands (updated April 2026): lower band £1,300-£12,600 for less serious cases; middle band £12,600-£37,700; upper band £37,700-£62,900 for the most serious cases, with exceptional cases capable of exceeding £62,900. The Equality and Human Rights Commission (EHRC) holds additional enforcement powers: it can conduct formal investigations, issue unlawful act notices, seek court orders requiring compliance, and enter into binding Section 23 agreements - all of which can result in significant legal costs, reputational harm, and ongoing regulatory scrutiny for non-compliant organisations.

Relation to WCAG: The Equality Act 2010 does not specify any technical standard by name, but demonstrating conformance with the Web Content Accessibility Guidelines (WCAG) - currently at version 2.2, with Level AA as the accepted benchmark - has become the recognised way for private sector service providers to show a court or regulator that they have taken proactive, reasonable steps to meet their digital accessibility obligations. For public sector bodies, the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 (which operate alongside the EQA) now explicitly reference WCAG 2.2 Level AA as the current minimum standard, confirmed by GOV.UK guidance updated in September 2024. Achieving WCAG 2.2 Level AA is therefore the most effective evidence of compliance across both sectors.

How EqualWeb helps: EqualWeb's AI Accessibility Widget can be installed on any UK website with a single line of code, automatically remediating up to 95% of common WCAG 2.2 Level AA issues - depending on how the site is built - in real time - helping service providers begin working toward the reasonable adjustments standard required under Section 20 of the Equality Act 2010 without a full site rebuild. The widget handles a significant share of common barriers on the client side, and also provides a profile-based accessibility menu, but achieving full WCAG 2.2 conformance requires expert-led remediation beyond the widget alone. For organisations seeking to demonstrate conformance and produce the evidence a regulator or court would expect, EqualWeb's Managed Compliance service pairs IAAP/CPWA-certified experts with client-side remediation, continuous monitoring, and a signed Accessibility Compliance Certificate backed by a VPAT/Accessibility Conformance Report and an evidence pack. EqualWeb's Continuous Monitoring provides a live 0-100 compliance score with regression alerts, giving legal and compliance teams ongoing visibility of their accessibility posture rather than a point-in-time snapshot. For UK organisations that publish PDFs - contracts, policies, annual reports - EqualWeb's PDF Tools check, remediate, and serve documents to PDF/UA standards, closing a common but overlooked accessibility gap that can independently give rise to discrimination claims. Together, these capabilities give UK businesses a structured, evidenced path toward meeting their Equality Act obligations across websites, apps, and documents.

Q: Does the Equality Act 2010 apply to websites and mobile apps?
A: Yes. UK courts and regulators interpret website and app owners as 'service providers' under the Equality Act 2010, making them subject to the Section 20 duty to make reasonable adjustments. This means digital channels must be proactively made accessible to disabled users - not simply fixed after a complaint is raised. Both private businesses and public sector organisations are covered, although public bodies also face explicit technical requirements under the Public Sector Bodies Accessibility Regulations 2018.

Q: Who must comply with the Equality Act 2010 accessibility requirements?
A: Any organisation that provides goods, facilities, or services to the public in England, Scotland, or Wales must comply, regardless of whether it is a large corporation, small business, charity, or public body. Employers of all sizes must also make reasonable adjustments for disabled staff and applicants. There is no minimum headcount or revenue threshold - the duty applies broadly to all service providers, including those that operate exclusively online.

Q: Is there a specific compliance deadline for the Equality Act 2010?
A: There is no future compliance deadline; the Act has been in force since 1 October 2010, meaning the duty to make reasonable adjustments has applied to service providers for over 15 years. Organisations that have not yet addressed digital accessibility are therefore already potentially exposed to discrimination claims. The Public Sector Bodies Accessibility Regulations 2018 introduced separate phased deadlines for public sector websites and apps, which have also fully elapsed.

Q: What are the penalties for non-compliance with the Equality Act 2010?
A: Claimants may sue in the county court or employment tribunal with no upper cap on damages. Compensation can cover financial losses, injury to feelings (Vento bands updated April 2026: up to £62,900 in the upper band for the most serious cases, with exceptional cases going higher), and aggravated damages. The EHRC can investigate organisations, issue unlawful act notices, and seek court orders enforcing compliance, creating further legal and reputational risk.

Q: What WCAG level does the Equality Act 2010 require?
A: The Equality Act 2010 itself does not reference WCAG, but demonstrating conformance with WCAG 2.2 Level AA is the accepted way for private sector service providers to show they have met the reasonable adjustments duty for digital services. For public sector bodies, the Public Sector Bodies Accessibility Regulations 2018 set WCAG 2.2 Level AA as the current explicit standard, and this benchmark is now recognised across both sectors.

### Israeli Standard 5568
URL: https://www.equalweb.com/platform/standards/is-5568.html
Region: Israel. Governing body: The Standards Institution of Israel (SII) publishes IS 5568. Enforcement of digital accessibility obligations is carried out by the Commission for Equal Rights of Persons with Disabilities (CERPD), which operates under Israel's Ministry of Justice under the Equal Rights for Persons with Disabilities Law, 5758-1998. In effect: October 2017 (full enforcement for remaining covered entities: October 2020).

Israeli Standard 5568 (IS 5568) is Israel's official technical standard for digital accessibility, defining the requirements that websites, web applications, and digital documents must meet to be usable by people with disabilities - requirements based on WCAG 2.0 Level AA and incorporated into law through the Equal Rights for Persons with Disabilities Law, 5758-1998. Compliance with IS 5568 is legally mandatory for both public-sector entities and private businesses serving the Israeli public, making it one of the most enforceable digital accessibility regimes in the Middle East.

What it is: Israeli Standard 5568 (IS 5568) is the national technical standard governing the accessibility of web content, web applications, and digital documents in Israel. Published by the Standards Institution of Israel (SII) and comprising two parts - Part 1 (website accessibility, most recently updated September 2023) and Part 2 (accessible digital documents, published May 2020) - the standard is substantially based on the W3C Web Content Accessibility Guidelines (WCAG) 2.0 at Level AA, with alignment toward WCAG 2.1 in later revisions. IS 5568 was mandated by the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 5773-2013, enacted under the Equal Rights for Persons with Disabilities Law, 5758-1998, giving it the force of binding national law. Its purpose is to ensure that people with visual, auditory, motor, and cognitive disabilities can perceive, operate, understand, and interact with digital services on equal terms.

Who must comply: IS 5568 applies to virtually all Israeli service providers - both public-sector bodies and private-sector organizations - that offer services or information to the general public through a website or digital channel. Medium and large businesses with average annual revenue of NIS 300,000 or more that were established after the standard's October 2017 entry into force were required to comply immediately; those established before 2017 had until October 2020. Small businesses with average annual revenue below NIS 300,000 were also required to comply by October 2020. Only private contractors with average annual income of NIS 100,000 or less are statutorily exempt. Covered industries span health, finance, banking, insurance, telecommunications, education, e-commerce, transportation, tourism, culture, hospitality, and government services, among others.

Key requirements:
- Websites and web applications must conform to WCAG 2.0 Level AA success criteria (perceivable, operable, understandable, robust).
- All non-text content - including images, buttons, and icons - must have descriptive text alternatives for screen readers.
- All functionality must be operable via keyboard alone, without requiring a mouse or pointer device.
- Video content must include Hebrew-language subtitles; pre-recorded audio must have text transcripts.
- Text must maintain a minimum color contrast ratio of 4.5:1 for normal text and 3:1 for large text.
- Organizations must publish an accessibility statement disclosing their conformance level and listing a designated accessibility coordinator with contact details.
- Digital documents (PDFs, Word files, etc.) must meet IS 5568 Part 2 requirements, including semantic tagging, logical reading order, and text alternatives for non-text elements.

Key dates:
- October 2017: IS 5568 entered into force; immediate compliance required for medium and large businesses (NIS 300,000+ annual revenue) established from 2017 onward.
- October 2020: Full compliance deadline for all remaining covered organizations, including small businesses and entities established before 2017. No grace period remains - all covered organizations are expected to be in compliance.

Penalties & enforcement: Under the Equal Rights for Persons with Disabilities Law, a person with a disability who encounters a non-compliant website may file a civil claim and seek statutory damages of up to NIS 50,000 without needing to prove that they personally suffered any harm - proof of non-compliance alone is sufficient. Additional fines may apply under Section 61(a)(3) of the Penal Law, 5737-1977, including a 5% daily surcharge on any fine for each day a violation continues, with corporate penalties doubled. Enforcement and oversight are exercised by the Commission for Equal Rights of Persons with Disabilities (CERPD) at the Ministry of Justice.

Relation to WCAG: IS 5568 is explicitly and substantially based on the W3C Web Content Accessibility Guidelines (WCAG) 2.0 at Level AA, which the standard's opening section identifies as its primary international source; the standard also aligns with ISO/IEC 40500:2012, the ISO adoption of WCAG 2.0. Part 1 of IS 5568, updated in September 2023, incorporates alignment toward WCAG 2.1, though the statutory baseline embedded in Israel's Service Accessibility Regulations remains WCAG 2.0 Level AA. Organizations that achieve WCAG 2.1 Level AA conformance therefore exceed the current legal minimum and are well-positioned for any future regulatory updates to the standard.

How EqualWeb helps: EqualWeb's AI Accessibility Widget provides a one-line installation that automatically remediates up to 95% of common WCAG 2.0/2.1 Level AA issues - depending on how the site is built - in real time - directly addressing the technical baseline that IS 5568 mandates - while its profile-based accessibility menu supports users with visual, motor, and cognitive needs as required by the standard. For organizations seeking the full certified conformance that IS 5568's legal obligation demands, EqualWeb's Managed Compliance service pairs IAAP/CPWA-certified experts with continuous client-side remediation, delivering a signed Accessibility Compliance Certificate, a VPAT/Accessibility Conformance Report, and a documented evidence pack that supports a demonstrated record of due diligence. EqualWeb's Continuous Monitoring tracks a live 0-100 compliance score with regression alerts, helping Israeli businesses maintain conformance over time and address the ongoing daily penalty exposure that IS 5568 enforcement allows. The PDF Tools module addresses IS 5568 Part 2 obligations by enabling organizations to check, remediate, and serve accessible PDFs aligned with PDF/UA requirements - critical for any covered entity that publishes digital documents to the public. Together, these services help Israeli organizations work systematically toward the full WCAG 2.0 AA conformance that IS 5568 requires, backed by auditable evidence.

Q: What is IS 5568 and what does it require?
A: IS 5568 is Israel's national standard for digital accessibility, published by the Standards Institution of Israel (SII). It requires websites and digital documents to conform to WCAG 2.0 Level AA, meaning content must be perceivable, operable, understandable, and robust for users with disabilities. Key requirements include keyboard navigability, text alternatives for images, adequate color contrast, Hebrew subtitles for video, and a published accessibility statement.

Q: Who is required to comply with IS 5568?
A: Compliance is mandatory for most businesses and organizations that provide services or information to the public in Israel - both government bodies and private-sector entities. Medium and large businesses (NIS 300,000+ annual revenue) must comply, as must small businesses below that threshold; only private contractors earning NIS 100,000 or less per year are exempt. The obligation applies across a wide range of sectors including e-commerce, banking, healthcare, education, and telecommunications.

Q: What is the compliance deadline for IS 5568?
A: The standard entered into force in October 2017, with medium and large businesses established from that point onward required to comply immediately. All remaining covered entities, including small businesses and organizations established before 2017, faced a final compliance deadline of October 2020. There is no grace period remaining - all covered organizations are currently expected to be in compliance.

Q: What are the penalties for non-compliance with IS 5568?
A: A person with a disability who encounters a non-compliant digital service can seek statutory damages of up to NIS 50,000 in civil court without having to prove personal harm - non-compliance itself is sufficient grounds for a claim. Daily fines may also accrue under Israel's Penal Law, and penalties are doubled for corporations. The Commission for Equal Rights of Persons with Disabilities (CERPD) at the Ministry of Justice provides oversight.

Q: Is IS 5568 the same as WCAG, and which version applies?
A: IS 5568 is Israel's national adaptation of the W3C's Web Content Accessibility Guidelines (WCAG) and is explicitly based on WCAG 2.0 Level AA. The standard also aligns with ISO/IEC 40500:2012. Part 1 of IS 5568 was updated in September 2023 with closer alignment to WCAG 2.1, but the statutory legal baseline remains WCAG 2.0 AA. Achieving WCAG 2.1 AA conformance exceeds the current legal minimum and is considered best practice.

### Norway Web Accessibility (Universal Design of ICT Regulations)
URL: https://www.equalweb.com/platform/standards/norway.html
Region: Norway. Governing body: Authority for Universal Design of ICT (Uutilsynet), part of the Norwegian Digitalisation Agency (Digdir) In effect: July 1, 2013 (Regulations on universal design of ICT solutions, FOR-2013-06-21-732); February 1, 2023 (WAD-aligned requirements for the public sector); accessibility statements mandatory for public bodies since February 1, 2023.

Norway has one of the strictest web accessibility regimes in the world: the Regulations on Universal Design of ICT (FOR-2013-06-21-732), issued under the Equality and Anti-Discrimination Act, require BOTH public-sector and private-sector websites and mobile applications directed at the Norwegian public to satisfy WCAG success criteria - Norway is one of very few countries that has applied a concrete WCAG obligation to private businesses since 2014. Public-sector bodies additionally follow the EU Web Accessibility Directive requirements (WCAG 2.1 AA basis plus a published accessibility statement), supervised and enforced by Uutilsynet, which audits sites and can order corrections and impose coercive fines.

What it is: Norwegian web accessibility law rests on the Equality and Anti-Discrimination Act (Likestillings- og diskrimineringsloven) and the Regulations on Universal Design of ICT Solutions. The regulations make universal design of websites, mobile applications and self-service machines a legal duty, using WCAG success criteria as the technical benchmark. For the private sector, the baseline has been WCAG 2.0 (47 of the 61 criteria, Levels A and AA with limited exceptions) applying to ICT solutions directed at the general public in Norway; for the public sector, Norway implemented the EU Web Accessibility Directive through the EEA Agreement, raising the bar to WCAG 2.1 Level AA with a mandatory, regularly updated accessibility statement. The Authority for Universal Design of ICT (Uutilsynet) supervises compliance, runs audits, publishes reports, and can issue orders and daily coercive fines until violations are corrected.

Who must comply: Virtually every organization with a website or app aimed at the Norwegian public: private companies of all sizes (shops, banks, media, services) fall under the ICT regulations for solutions directed at the general public, and public-sector bodies carry the additional WAD-aligned duties, including the accessibility statement. New ICT solutions must comply from launch. Foreign companies whose Norwegian-facing digital services target the Norwegian market are also expected to conform - and as an EEA state, Norway is additionally in the process of incorporating the European Accessibility Act framework, which extends duties for e-commerce, banking and other services.

Key requirements:
- Websites and mobile applications directed at the Norwegian public must satisfy the referenced WCAG success criteria (WCAG 2.0 A/AA baseline for the private sector; WCAG 2.1 AA basis for the public sector under the WAD).
- Public-sector bodies must publish and maintain an accessibility statement for each website and app, including a feedback mechanism, using the designated national solution.
- New ICT solutions must be universally designed from the moment they launch; upgrades and replacements trigger the duty for existing solutions.
- Self-service machines (kiosks, ticketing, payment terminals) are covered alongside web and mobile.
- Organizations must correct violations identified by Uutilsynet within set deadlines or face orders and coercive daily fines.

Key dates:
- : 
- : 
- : 

Penalties & enforcement: Uutilsynet can order corrections and impose coercive daily fines (tvangsmulkt) until a violation is fixed; it audits both public and private sites and publishes its findings. Beyond regulatory action, discrimination claims can be pursued under the Equality and Anti-Discrimination Act. Reputationally, Uutilsynet's public audit reports name non-compliant organizations.

Relation to WCAG: The Norwegian regulations reference WCAG directly: WCAG 2.0 Levels A and AA (with a few excepted criteria) as the private-sector baseline, and WCAG 2.1 Level AA via EN 301 549 for the public sector under the Web Accessibility Directive. Building to WCAG 2.2 AA satisfies both tracks and positions organizations for the EAA-related expansion now working through the EEA.

How EqualWeb helps: EqualWeb takes Norwegian-market sites from scan to evidence: automated auditing against the referenced WCAG criteria, AI plus expert remediation, 24/7 monitoring that catches regressions before an Uutilsynet audit does, and the documentation - audit reports and conformance records - that supports your accessibility statement.

Q: Does Norwegian web accessibility law apply to private companies?
A: Yes - this is what makes Norway unusual. The Regulations on Universal Design of ICT have applied WCAG-based duties to private-sector websites and apps directed at the Norwegian public since July 2014 for new solutions, and since January 2021 for all existing covered solutions.

Q: What standard does Norway require - WCAG 2.0 or 2.1?
A: The private-sector baseline references WCAG 2.0 Levels A and AA (with limited exceptions). Public-sector bodies follow the EU Web Accessibility Directive as incorporated through the EEA, which is based on WCAG 2.1 Level AA plus a mandatory accessibility statement. Targeting WCAG 2.2 AA covers both.

Q: Who enforces web accessibility in Norway?
A: Uutilsynet - the Authority for Universal Design of ICT, part of the Norwegian Digitalisation Agency (Digdir). It audits websites and apps, orders corrections, and can impose coercive daily fines until violations are resolved.

Q: Does a foreign company selling to Norwegian customers need to comply?
A: If your website or app is directed at the general public in Norway, the universal-design duty is engaged regardless of where the company sits. E-commerce and services aimed at Norwegian consumers should conform to the referenced WCAG criteria.

### Germany Web Accessibility (BFSG, BGG and BITV 2.0)
URL: https://www.equalweb.com/platform/standards/germany.html
Region: Germany. Governing body: Federal Ministry of Labour and Social Affairs (BMAS); market surveillance by the federal states (MLBF); Federal Monitoring Body for Accessibility of IT (BFIT-Bund) for the public sector In effect: May 2002 (BGG); May 21, 2019 / partly September 23, 2020 onward (BITV 2.0 as amended for the Web Accessibility Directive); June 28, 2025 (BFSG - the German European Accessibility Act implementation - fully applicable).

Germany regulates digital accessibility on two tracks. Public-sector websites and apps have long been covered by the Disability Equality Act (BGG) and the BITV 2.0 ordinance, which apply EN 301 549 - effectively WCAG 2.1 Level AA - plus a published accessibility statement. Since June 28, 2025, the Barrierefreiheitsstaerkungsgesetz (BFSG), Germany's implementation of the European Accessibility Act, extends binding accessibility duties to the PRIVATE sector: e-commerce, banking, transport booking, e-books and other consumer-facing digital services must be accessible, with market-surveillance authorities empowered to order withdrawal of non-conforming services and impose fines up to EUR 100,000.

What it is: German web accessibility law combines the Behindertengleichstellungsgesetz (BGG - Disability Equality Act) and the Barrierefreie-Informationstechnik-Verordnung (BITV 2.0) for federal public bodies - with state-level equivalents for Laender and municipal bodies - and, since June 2025, the Barrierefreiheitsstaerkungsgesetz (BFSG) for private-sector products and services under the European Accessibility Act. The technical benchmark across both tracks is EN 301 549, which for web content applies the WCAG success criteria at Level AA. Public bodies must also publish accessibility statements with a feedback mechanism and are monitored by BFIT-Bund; private services under the BFSG must document conformance and are supervised by the market-surveillance authorities of the federal states.

Who must comply: Public track: federal, state and municipal public bodies, for websites, intranets, mobile apps and electronic administration. Private track (BFSG, since June 28, 2025): businesses providing covered consumer services in Germany - e-commerce of any sector, consumer banking, passenger transport interfaces, e-books and reading software, telecommunications and media access services - regardless of where the company is established. A microenterprise exemption applies to service providers with fewer than 10 employees and at most EUR 2 million annual turnover; sellers outside the EU are covered when they direct services at German consumers.

Key requirements:
- Meet EN 301 549 for web content and apps - in practice the WCAG Level AA success criteria (WCAG 2.1 today, with the standard's next revision tracking newer WCAG work).
- Public bodies: publish and maintain an accessibility statement per site and app, including a feedback channel and enforcement-route information.
- BFSG services: ensure the covered service (including its website, app, checkout and documents) is perceivable, operable, understandable and robust, and document how conformance is achieved.
- Respond to accessibility complaints; under the BFSG, consumers and associations can escalate to market-surveillance authorities.
- Keep conformance evidence current - the burden of demonstrating accessibility sits with the provider when an authority asks.

Key dates:
- : 
- : 
- : 
- : 

Penalties & enforcement: Under the BFSG, market-surveillance authorities can require corrective measures, restrict or prohibit the provision of a non-conforming service, and impose administrative fines of up to EUR 100,000 for violations of key obligations. Public-sector bodies face supervision by monitoring bodies and administrative enforcement, and individuals can pursue claims under equality law. Consumer and disability associations have standing to bring proceedings under the BFSG.

Relation to WCAG: Both German tracks reference EN 301 549, whose web chapters incorporate the WCAG success criteria at Level AA - currently WCAG 2.1. The updated EN 301 549 revision expected to be cited in the EU Official Journal will track newer WCAG work, so building and testing to WCAG 2.2 AA is the practical way to satisfy BITV 2.0 and BFSG duties and stay ahead of the standard's refresh.

How EqualWeb helps: EqualWeb prepares German-market sites for BFSG and BITV duties end to end: EN 301 549 / WCAG AA auditing, AI plus certified-expert remediation, accessible PDFs for statements and contracts, monitoring that keeps conformance current, and the documentation an authority or procurement team asks for first.

Q: What is the BFSG and when did it take effect?
A: The Barrierefreiheitsstaerkungsgesetz is Germany's implementation of the European Accessibility Act. It has applied since June 28, 2025 to covered private-sector services - e-commerce, consumer banking, transport booking, e-books and more - making accessibility a binding legal duty for private businesses in Germany.

Q: Which standard do German authorities expect - BITV or WCAG?
A: BITV 2.0 and the BFSG both point to EN 301 549, which applies the WCAG Level AA success criteria to web content. Meeting WCAG 2.1 AA (or better, WCAG 2.2 AA) is how conformance is demonstrated in practice.

Q: Does the BFSG apply to non-German companies?
A: Yes. A company established anywhere - the US, Israel, the UK - that provides covered services to consumers in Germany falls under the BFSG. The location of the customer, not the company, is decisive.

Q: What fines are possible under German accessibility law?
A: BFSG violations can draw administrative fines up to EUR 100,000, alongside orders to correct or withdraw the non-conforming service. Authorities act on complaints from consumers and associations, so any visitor can trigger a review.

### Australia Web Accessibility (Disability Discrimination Act)
URL: https://www.equalweb.com/platform/standards/australia.html
Region: Australia. Governing body: Australian Human Rights Commission (AHRC); Digital Transformation Agency (DTA) for government digital standards In effect: March 1, 1993 (Disability Discrimination Act 1992 in force); 2000 (Maguire v SOCOG - first web accessibility ruling worldwide); 2010-2014 (National Transition Strategy: WCAG 2.0 AA for government); WCAG 2.1 AA current under the government Digital Service Standard.

Australian web accessibility obligations flow from the Disability Discrimination Act 1992 (DDA), which makes it unlawful to discriminate in the provision of goods, services and information - and has applied to websites since the landmark Maguire v SOCOG ruling in 2000, the world's first successful web accessibility complaint. The Australian Human Rights Commission's guidance treats WCAG conformance (Level AA) as the benchmark for meeting the duty, government websites are required to meet WCAG 2.1 AA under the Digital Service Standard, and complaints can lead to conciliation and Federal Court proceedings with uncapped damages.

What it is: The DDA is a civil-rights statute rather than a technical regulation: it prohibits disability discrimination by anyone providing goods, services or facilities in Australia, and the AHRC's World Wide Web Access advisory notes make clear this covers websites and apps of organizations 'whether in the public or private sector'. The technical yardstick is WCAG: the AHRC advises conformance with WCAG at Level AA, government agencies have been bound to WCAG conformance since the 2010-2014 National Transition Strategy and today follow WCAG 2.1 AA under the DTA's standards. Enforcement is complaint-driven - individuals lodge complaints with the AHRC, which conciliates; unresolved matters can proceed to the Federal Court, as in Maguire v SOCOG, where the Sydney Olympics organizing committee was ordered to fix its site and pay damages.

Who must comply: Every organization providing goods, services or information to the Australian public through the web: private businesses of all sizes, e-commerce, banks, airlines, education providers, and all levels of government. There is no small-business exemption in the DDA; the 'unjustifiable hardship' defense is narrow and rarely succeeds for standard websites. Australian Government agencies carry the additional, explicit WCAG 2.1 AA duty under the Digital Service Standard, and most state governments mirror it.

Key requirements:
- Provide web content and services in a form accessible to people with disabilities - the AHRC treats WCAG Level AA conformance as the practical measure of compliance.
- Government agencies: meet WCAG 2.1 Level AA under the Digital Service Standard, including for internal-facing systems and documents.
- Ensure documents published on the web (including PDFs) are accessible or provided in accessible alternative formats.
- Respond to accessibility complaints - AHRC conciliation is the first stop, and an unresolved complaint can go to the Federal Court.
- Address accessibility in procurement: AS EN 301 549 (the Australian adoption of the European standard) is used for ICT procurement across government.

Key dates:
- : 
- : 
- : 
- : 

Penalties & enforcement: The DDA carries no fixed fine schedule; exposure comes through complaints. AHRC conciliation commonly produces remediation commitments and compensation; Federal Court proceedings can order remediation and damages without a statutory cap - Maguire v SOCOG ended with an order to make the site accessible and AUD 20,000 in damages, and the reputational cost of a public finding is typically larger than the award.

Relation to WCAG: WCAG is the de facto legal benchmark: the AHRC advisory notes point to WCAG conformance at Level AA for DDA compliance, government is explicitly bound to WCAG 2.1 AA, and AS EN 301 549 embeds the WCAG criteria into procurement. Building to WCAG 2.2 AA satisfies today's expectations and the direction of travel.

How EqualWeb helps: EqualWeb aligns Australian sites with DDA expectations: WCAG 2.1/2.2 AA auditing by certified experts, AI-assisted remediation, accessible PDFs, continuous monitoring, and complaint-ready documentation - so an AHRC letter meets an evidence file, not a scramble.

Q: Is website accessibility legally required in Australia?
A: Yes. The Disability Discrimination Act 1992 applies to websites and apps of both private and public organizations, as established in Maguire v SOCOG (2000). The AHRC's guidance treats WCAG Level AA conformance as the measure of meeting that duty.

Q: What standard applies to Australian government websites?
A: WCAG 2.1 Level AA under the Digital Transformation Agency's Digital Service Standard, with AS EN 301 549 used for ICT procurement. The earlier National Transition Strategy mandated WCAG 2.0 AA by the end of 2014.

Q: Can a private business be sued over web accessibility in Australia?
A: Yes - through the complaint route: an AHRC complaint, conciliation, and if unresolved, Federal Court proceedings with remediation orders and uncapped damages. Maguire v SOCOG set the precedent and remains the reference case.

Q: Does the DDA cover PDFs and documents?
A: Yes. Information provided to the public is covered regardless of format - inaccessible PDFs are one of the most common complaint subjects, and the AHRC expects accessible versions or equal alternatives.

### Japan Web Accessibility (JIS X 8341-3 and the Disability Discrimination Elimination Act)
URL: https://www.equalweb.com/platform/standards/japan.html
Region: Japan. Governing body: Japanese Standards Association / METI (JIS standard); Cabinet Office (Act for Eliminating Discrimination against Persons with Disabilities); Digital Agency and Ministry of Internal Affairs and Communications for government guidance In effect: 2004 (JIS X 8341-3 first edition); 2016 (JIS X 8341-3:2016, aligned with WCAG 2.0 / ISO/IEC 40500); April 1, 2016 (Disability Discrimination Elimination Act in force); April 1, 2024 (amended Act - reasonable accommodation became mandatory for private businesses).

Japanese web accessibility is anchored in JIS X 8341-3:2016 - the national standard technically identical to WCAG 2.0 / ISO/IEC 40500 - and the Act for Eliminating Discrimination against Persons with Disabilities. Since April 1, 2024, an amendment with major practical impact took effect: providing 'reasonable accommodation' to people with disabilities became a LEGAL OBLIGATION for private businesses, not just a best effort. Government bodies are expected to meet JIS X 8341-3 conformance level AA under public guidelines (the miraretsu framework of conformance grades), and while the Act does not name a technical web standard, JIS conformance testing is the accepted way Japanese organizations demonstrate digital accessibility.

What it is: Two instruments define the Japanese landscape. JIS X 8341-3:2016, 'Guidelines for older persons and persons with disabilities - Information and communications equipment, software and services - Part 3: Web content', is Japan's national accessibility standard and is technically identical to WCAG 2.0 (ISO/IEC 40500:2012), using the same success criteria and A/AA/AAA levels; conformance is commonly declared using the JIS-defined grades (conformant / partially conformant) after formal testing. The Act for Eliminating Discrimination against Persons with Disabilities (Shogaisha Sabetsu Kaishoho) prohibits unjust discriminatory treatment and requires reasonable accommodation; the June 2021 amendment - effective April 1, 2024 - upgraded reasonable accommodation from an effort duty to a binding legal duty for private businesses, which in the digital context increasingly means providing accessible websites, apps and documents or equal alternatives on request.

Who must comply: National and local government bodies, whose sites are expected to achieve JIS X 8341-3 Level AA conformance under public-sector guidelines; and, since April 2024, private businesses of all sizes, which must provide reasonable accommodation - a duty engaged when a person with a disability encounters a barrier, including digital ones. Large enterprises, transport, finance and education face the highest expectations, and Japanese procurement and CSR reporting increasingly ask for JIS conformance test results.

Key requirements:
- Conform to JIS X 8341-3:2016 - the WCAG 2.0-identical success criteria - with Level AA as the target for public bodies and the accepted benchmark for serious private-sector programs.
- Test and declare conformance using the JIS framework (formal testing over a defined page sample, published as a conformance declaration - commonly via the WAIC guidelines).
- Since April 1, 2024: provide reasonable accommodation when a person with a disability faces a barrier - refusing without a legitimate reason violates the Act.
- Government bodies: follow the public-sector operational guidelines (accessibility policy, periodic testing, published results).
- Keep documents and PDFs accessible or provide equal alternatives - accommodation requests frequently concern documents.

Key dates:
- : 
- : 
- : 

Penalties & enforcement: The Act is enforced administratively: the competent minister can request reports and issue guidance, recommendations and public findings against non-complying businesses, with fines for false reporting; discrimination disputes can also proceed under civil law. The sharper risk for consumer brands is administrative guidance plus publicity - and procurement exclusion, since JIS conformance is asked for in public tenders.

Relation to WCAG: JIS X 8341-3:2016 is technically identical to WCAG 2.0, so WCAG work transfers directly - and because WCAG is backward compatible, building and testing to WCAG 2.1/2.2 Level AA over-satisfies the JIS criteria while preparing for the standard's eventual refresh. Conformance is declared through JIS-style testing, which EqualWeb's audit methodology maps onto criterion by criterion.

How EqualWeb helps: EqualWeb audits against the WCAG criteria that JIS X 8341-3 is built on, remediates with AI plus certified experts, covers documents and PDFs (a frequent subject of accommodation requests), and produces the criterion-level test documentation that Japanese procurement and conformance declarations expect.

Q: What is JIS X 8341-3 and how does it relate to WCAG?
A: JIS X 8341-3:2016 is Japan's national web accessibility standard, technically identical to WCAG 2.0 (ISO/IEC 40500): the same success criteria and A/AA/AAA levels. Testing to WCAG Level AA is testing to JIS Level AA.

Q: What changed in Japan in April 2024?
A: The amended Act for Eliminating Discrimination against Persons with Disabilities took effect, making reasonable accommodation a binding legal duty for private businesses - previously it was only an effort obligation. Digital barriers are squarely within its scope.

Q: Is WCAG legally mandatory for private Japanese websites?
A: No statute names WCAG for the private sector, but the practical picture is close: reasonable accommodation is now mandatory, JIS X 8341-3 (WCAG 2.0-identical) is the accepted benchmark, procurement asks for JIS conformance, and government guidance points to Level AA.

Q: What level do Japanese government sites target?
A: Public-sector guidelines direct national and local government websites toward JIS X 8341-3 conformance at Level AA, with formal testing and published conformance declarations.

### China Web Accessibility (Barrier-Free Environment Construction Law and GB/T 37668)
URL: https://www.equalweb.com/platform/standards/china.html
Region: China. Governing body: National People's Congress (legislation); Ministry of Industry and Information Technology (MIIT) for internet accessibility programs; Standardization Administration of China (GB/T standards) In effect: September 1, 2023 (Barrier-Free Environment Construction Law in force); 2019 (GB/T 37668-2019 national web accessibility standard); 2020 onward (MIIT special campaigns for website and app accessibility retrofits).

China's first dedicated accessibility statute - the Barrier-Free Environment Construction Law - took effect on September 1, 2023, and elevates information accessibility (including websites, apps and self-service technology) to a national legal requirement, with government bodies, public services and key internet platforms leading the obligations. The technical reference is GB/T 37668-2019, China's national web accessibility standard modeled on WCAG, and the MIIT has run enforcement-backed retrofit campaigns since 2020 requiring hundreds of major websites and apps to add accessibility features, with age-friendly and barrier-free versions now standard among leading Chinese platforms.

What it is: The Barrier-Free Environment Construction Law (Wuzhang'ai Huanjing Jianshe Fa) is China's umbrella accessibility statute, covering the built environment, transport, services and - in a dedicated chapter - information accessibility: government information, emergency information, internet services, smart terminals and telecommunications must be progressively made accessible to persons with disabilities and older adults. Technical implementation leans on GB/T 37668-2019, 'Information technology - Requirements and testing methods for accessibility of web content' - a national standard closely modeled on WCAG's principles, guidelines and testable requirements. Alongside the law, the MIIT's Internet Application Accessibility and Aging-Friendly campaigns (from 2020) directed named lists of major websites and mobile apps to implement accessibility retrofits, publish accessible/elderly modes, and pass evaluation - a compliance mechanism with real teeth through supervision, evaluation results and public reporting.

Who must comply: Government bodies and public institutions first: e-government portals, public-service platforms, emergency information and public cultural services carry the strongest duties. Major internet platforms and telecommunications providers are pulled in through the law's internet-accessibility provisions and MIIT campaign lists (e-commerce, news, social, banking, travel and utility apps). Foreign companies operating consumer platforms in the Chinese market fall under the same expectations for their China-facing properties; enterprises serving older users are additionally covered by the aging-friendly requirements that run in parallel.

Key requirements:
- Make government and public-service websites, apps and information channels accessible, including emergency information in accessible formats.
- Follow GB/T 37668-2019 - WCAG-modeled requirements and testing methods - as the technical benchmark for web content accessibility.
- Major internet platforms named in MIIT campaigns: implement accessibility retrofits, provide barrier-free/aging-friendly modes, and pass the ministry's evaluation.
- Self-service terminals and smart devices used in public services must offer accessible interaction modes.
- Progressively retrofit existing digital services; new public-facing services should be accessible from launch.

Key dates:
- : 
- : 
- : 

Penalties & enforcement: The law works through administrative supervision: responsible departments can order correction of violations, and continued non-compliance draws administrative penalties under the law and adjacent regulations; MIIT campaign compliance is enforced through evaluation, rectification orders and public reporting. Procurators can also bring public-interest litigation over accessibility failures - a mechanism already used since the law took effect - and for consumer platforms, exclusion from the ministry's compliant-app lists carries direct commercial cost.

Relation to WCAG: GB/T 37668-2019 is modeled on WCAG's structure - perceivable, operable, understandable, robust - with testable requirements that map closely to WCAG success criteria. International organizations typically run one WCAG 2.1/2.2 Level AA program and treat GB/T conformance as a mapped output of it, which is exactly how EqualWeb structures audits for China-facing properties.

How EqualWeb helps: EqualWeb runs one WCAG-based program that maps to GB/T 37668 for China-facing properties: auditing, AI plus expert remediation, accessible documents, and evaluation-ready reporting - so global brands cover the Chinese requirements from the same evidence base as the rest of the world.

Q: Does China have a web accessibility law?
A: Yes - the Barrier-Free Environment Construction Law, in force since September 1, 2023, is China's first dedicated accessibility statute and includes a chapter on information accessibility covering websites, apps and smart terminals, with government and public services leading the duties.

Q: What is GB/T 37668-2019?
A: China's national standard for web content accessibility - requirements and testing methods closely modeled on WCAG's principles and success criteria. It is the technical reference used in evaluations and retrofit programs.

Q: Are private companies covered in China?
A: Major internet platforms are - through the law's internet provisions and the MIIT's named retrofit campaigns covering e-commerce, banking, travel, news and social apps. Public-interest litigation and administrative supervision extend the pressure beyond the named lists.

Q: If we already meet WCAG, do we meet the Chinese requirements?
A: Largely yes at the technical level: GB/T 37668-2019 maps closely to WCAG, so a WCAG 2.1/2.2 AA program covers most requirements. China-specific items - aging-friendly modes, evaluation and documentation formats - are handled as a mapped layer on top.

### France Web Accessibility (RGAA and Law 2005-102)
URL: https://www.equalweb.com/platform/standards/france.html
Region: France. Governing body: DINUM (Direction interministerielle du numerique) publishes the RGAA; ARCOM and the DGCCRF gained enforcement roles under the 2023 accessibility reform In effect: February 11, 2005 (Law 2005-102, Article 47); July 24, 2019 (Decree 2019-768 - RGAA obligations, declarations and fines); October 2023 (Law 2023-171 and Decree 2023-931 - reinforced sanctions and European Accessibility Act alignment).

France requires web accessibility through Article 47 of Law 2005-102 and its implementing decrees: public-sector bodies AND private companies with revenue in France of EUR 250 million or more must make their websites, intranets and mobile applications conform to the RGAA (Referentiel General d'Amelioration de l'Accessibilite), publish an accessibility declaration per site, display the conformance status on every page, and maintain a multi-year accessibility plan. The RGAA's technical baseline is WCAG 2.1 Level AA via EN 301 549, and the 2023 reform raised the ceiling on fines to EUR 50,000 per non-compliant service, renewable while the violation persists - with the European Accessibility Act extending duties to e-commerce, banking and other private services regardless of the revenue threshold.

What it is: French web accessibility law is built on Article 47 of the 2005 disability-rights law (Law 2005-102), made operational by Decree 2019-768 and the RGAA. The RGAA translates WCAG 2.1 Level AA (through the European standard EN 301 549) into 106 testable criteria adapted to French legal requirements. Covered organizations must reach RGAA conformance, publish an accessibility declaration for each website and app stating its conformance level (fully, partially or not compliant - and that status must appear on the site itself), publish a three-year accessibility plan (schema pluriannuel) with annual action plans, and provide users a way to report barriers and reach a mediation path. Law 2023-171 and Decree 2023-931 (2023) strengthened enforcement as part of France's European Accessibility Act transposition, adding new supervising authorities and substantially higher penalties.

Who must comply: All public-sector bodies (state, local government, public agencies and bodies delegated a public mission), plus private companies whose average revenue generated in France over the last three financial years is EUR 250 million or more. The European Accessibility Act, transposed into French law and applying since June 28, 2025, extends accessibility duties to in-scope private services - e-commerce, consumer banking, e-books, transport ticketing and telecoms - including SMEs above the microenterprise threshold, regardless of the EUR 250M test.

Key requirements:
- Conform to the RGAA (current major version 4), whose baseline is WCAG 2.1 Level AA via EN 301 549.
- Publish an accessibility declaration for every website, intranet, extranet and mobile app, and state the conformance level (totalement / partiellement / non conforme) visibly on the site.
- Publish a multi-year accessibility plan covering at most three years, plus an annual action plan.
- Give users an accessible way to report accessibility barriers and escalate to the Defenseur des droits mediation path.
- EAA-scope services must additionally meet the European Accessibility Act requirements in force since June 28, 2025.

Key dates:
- : 
- : 
- : 
- : 

Penalties & enforcement: Under the 2019 regime, failing the publication obligations (declaration, plan, page status) carried an administrative fine of up to EUR 20,000 per site per year. The 2023 reform (Law 2023-171, Decree 2023-931) raised sanctions sharply: up to EUR 50,000 per service for non-compliance, renewable every six months while the breach continues, with ARCOM and the DGCCRF empowered to supervise and sanction. Discrimination claims can also be pursued through the Defenseur des droits.

Relation to WCAG: The RGAA is France's national implementation of WCAG: its technical criteria map to WCAG 2.1 Level AA through EN 301 549, restructured into 106 French-law criteria with test methodology. Building to WCAG 2.2 AA satisfies the RGAA baseline and positions you for future RGAA revisions, since WCAG 2.2 is backward-compatible with 2.1.

How EqualWeb helps: EqualWeb helps French-market sites reach and prove RGAA conformance: expert audits mapped to WCAG 2.1/2.2 AA criteria, AI plus certified-expert remediation, continuous monitoring that catches regressions, and the audit trail and conformance documentation your accessibility declaration and multi-year plan are built on.

Q: Does the RGAA apply to private companies?
A: Yes, in two ways: any company with revenue in France of EUR 250 million or more falls under Article 47's RGAA obligations, and since June 28, 2025 the European Accessibility Act covers in-scope private services - e-commerce, banking, transport ticketing, e-books and telecoms - regardless of that revenue threshold.

Q: What is the difference between the RGAA and WCAG?
A: The RGAA is France's legal implementation of WCAG. It takes WCAG 2.1 Level AA (via the European standard EN 301 549) and restructures it into 106 testable criteria with a French test methodology, adding French-specific publication duties: the accessibility declaration, the visible conformance status and the multi-year plan.

Q: What are the fines for non-compliance in France?
A: The 2019 decree set fines up to EUR 20,000 per site per year for failing the publication obligations. The 2023 reform raised the ceiling to EUR 50,000 per non-compliant service, renewable every six months while the violation persists.

Q: Do I need an accessibility declaration in French?
A: Yes. Covered sites must publish an accessibility declaration for each digital service, state the conformance level on the site itself, and keep a multi-year accessibility plan with annual updates. EqualWeb's audit and documentation services produce the evidence base these declarations rest on.

### India Web Accessibility (RPwD Act 2016 and GIGW)
URL: https://www.equalweb.com/platform/standards/india.html
Region: India. Governing body: Department of Empowerment of Persons with Disabilities (DEPwD) and the Chief Commissioner for Persons with Disabilities enforce the RPwD Act; MeitY/NIC publish the GIGW; the Bureau of Indian Standards issues IS 17802 In effect: April 19, 2017 (Rights of Persons with Disabilities Act, 2016 in force); June 15, 2017 (RPwD Rules - Rule 15 ICT accessibility standards); 2021-2022 (BIS IS 17802 Parts 1 and 2); 2023 (GIGW 3.0); November 8, 2024 (Supreme Court judgment in Rajive Raturi v. Union of India ordering mandatory accessibility standards).

India's web accessibility duties come from the Rights of Persons with Disabilities Act, 2016 (RPwD Act), which obligates both government and private service providers to make ICT - including websites and mobile apps - accessible. The technical benchmarks are the Guidelines for Indian Government Websites (GIGW 3.0, aligned with WCAG 2.1 Level AA) for the public sector and BIS standard IS 17802 (harmonized with EN 301 549) for ICT products and services. In November 2024 the Supreme Court of India, in Rajive Raturi v. Union of India, held that accessibility standards must be mandatory rather than advisory and directed the government to frame binding rules - making Indian digital accessibility enforcement a live, tightening obligation rather than a recommendation.

What it is: The RPwD Act, 2016 is India's comprehensive disability-rights law, replacing the 1995 Act and implementing the UN CRPD. Sections 40-46 cover accessibility: the government notifies standards (RPwD Rules 2017, Rule 15 points ICT accessibility at the GIGW and associated standards), establishments must comply, and existing infrastructure and services were given time-bound windows to conform. For websites this means GIGW conformance for government bodies - GIGW 3.0 (2023) is explicitly WCAG 2.1 AA-aligned and certified through STQC - and IS 17802 (the BIS standard harmonized with EN 301 549) as the reference for ICT products and services generally. The 2024 Supreme Court ruling found the existing self-regulatory posture inadequate and ordered mandatory minimum standards, signaling stronger enforcement ahead.

Who must comply: Government ministries, departments and public bodies (GIGW conformance, STQC certification for central government sites); 'establishments' under the RPwD Act - which includes private companies providing goods, services or facilities to the public; and ICT product and service providers measured against IS 17802. Practically, any organization serving Indian users - banks, e-commerce, education, transport, healthcare - carries accessibility duties, and government-facing vendors are contractually bound to GIGW.

Key requirements:
- Government websites and apps: conform to GIGW 3.0 (WCAG 2.1 Level AA-aligned) and obtain STQC certification where required.
- ICT products and services: meet IS 17802 (Parts 1-2), the BIS standard harmonized with EN 301 549.
- Service providers must ensure persons with disabilities can access services provided to the public, under the RPwD Act's accessibility and non-discrimination duties.
- Respect the time-bound compliance windows set by the RPwD Rules for existing services, and track the mandatory standards ordered by the Supreme Court in 2024.
- Public procurement increasingly requires accessibility conformance as a contract condition.

Key dates:
- : 
- : 
- : 

Penalties & enforcement: Section 89 of the RPwD Act penalizes contraventions: a fine of up to INR 10,000 for a first offense and INR 50,000 to 500,000 for subsequent offenses. The Chief Commissioner and State Commissioners for Persons with Disabilities take complaints and can direct corrective action; courts entertain writ petitions - the route that produced the 2024 Supreme Court accessibility judgment. Government sites failing GIGW risk losing certification and procurement eligibility.

Relation to WCAG: GIGW 3.0 is expressly aligned with WCAG 2.1 Level AA, and IS 17802 is harmonized with EN 301 549 - whose web requirements are WCAG-based. Building to WCAG 2.2 AA therefore satisfies India's technical baselines with headroom for the mandatory standards now being framed after the Supreme Court's 2024 ruling.

How EqualWeb helps: EqualWeb audits against WCAG 2.1/2.2 AA - the baseline GIGW 3.0 and IS 17802 build on - combines AI remediation with certified-expert fixes, monitors continuously, and produces the conformance documentation that GIGW certification, procurement and RPwD Act compliance reviews ask for.

Q: Is website accessibility legally required in India?
A: Yes. The RPwD Act, 2016 obligates government bodies and service providers to make ICT accessible, with GIGW 3.0 and IS 17802 as the technical benchmarks - and in November 2024 the Supreme Court ordered that accessibility standards be made mandatory, not advisory.

Q: Does the RPwD Act apply to private companies?
A: Yes. 'Establishments' under the Act include private bodies, and service providers offering goods, services or facilities to the public carry accessibility duties. Private ICT products and services are measured against IS 17802.

Q: What standard do Indian government websites follow?
A: GIGW 3.0 (Guidelines for Indian Government Websites, 2023), which is aligned with WCAG 2.1 Level AA. Central government sites are audited and certified through STQC.

Q: What changed with the 2024 Supreme Court judgment?
A: In Rajive Raturi v. Union of India (November 8, 2024) the Supreme Court held that leaving accessibility to self-regulation violates the RPwD Act, and directed the government to prescribe mandatory minimum standards - so binding, enforceable rules are the direction of travel.

### Hong Kong Web Accessibility (DDO and Government Guidelines)
URL: https://www.equalweb.com/platform/standards/hong-kong.html
Region: Hong Kong. Governing body: Equal Opportunities Commission (EOC) enforces the Disability Discrimination Ordinance; the Digital Policy Office (formerly OGCIO) sets government web accessibility requirements and runs the Web Accessibility Recognition Scheme In effect: 1996 (Disability Discrimination Ordinance, Cap. 487, in operation); 2013 (government websites required to meet WCAG 2.0 Level AA); ongoing (Web Accessibility Recognition Scheme and updated government guidelines referencing current WCAG versions).

Hong Kong has no standalone web accessibility statute; instead, the Disability Discrimination Ordinance (Cap. 487) makes it unlawful to discriminate against persons with disabilities in the provision of goods, services and facilities - which the Equal Opportunities Commission applies to inaccessible websites and apps. Government websites have been required to meet WCAG 2.0 Level AA since 2013 under OGCIO (now Digital Policy Office) guidelines, current guidance references the newest WCAG versions, and the private sector is pushed the same way through EOC guidance and the long-running Web Accessibility Recognition Scheme. A visitor who cannot use your service can complain to the EOC and litigate under the DDO, where damages are uncapped.

What it is: The DDO is Hong Kong's disability anti-discrimination law: Section 26 covers goods, services and facilities, and refusing or failing to provide reasonable access - including digital access - can constitute unlawful discrimination unless accommodation would impose unjustifiable hardship. The EOC investigates complaints, conciliates, and can support proceedings in the District Court. On the standards side, the government mandates WCAG conformance for its own estate: since 2013, government websites must meet WCAG 2.0 Level AA (guidance since updated to reference newer WCAG versions), and mobile apps carry parallel requirements. The Digital Policy Office and the EOC jointly promote adoption in the private sector, most visibly through the Web Accessibility Recognition Scheme, which awards conforming sites and apps annually.

Who must comply: Every provider of goods, services or facilities to the Hong Kong public falls under the DDO - banks, retailers, utilities, schools, healthcare, media and e-commerce, local or foreign, if they serve Hong Kong users. Government bureaux and departments must meet the WCAG-based guidelines as policy. Private organizations face no direct WCAG statute, but an inaccessible digital service is exposure under the DDO's services provisions.

Key requirements:
- Do not discriminate in the provision of goods, services and facilities - digital channels included (DDO s.26); provide reasonable accommodation short of unjustifiable hardship.
- Government websites and apps: meet the WCAG Level AA-based requirements set by the Digital Policy Office (WCAG 2.0 AA mandated since 2013, guidance tracking newer versions).
- Provide accessible alternatives and assistance channels where conformance is not yet achieved.
- Private sector: align with EOC guidance and the Web Accessibility Recognition Scheme criteria - WCAG conformance is the de facto benchmark used.
- Keep evidence of accessibility efforts - audits, fixes, statements - to answer EOC complaints.

Key dates:
- : 
- : 
- : 

Penalties & enforcement: There is no fixed administrative fine: DDO claims proceed as discrimination cases. The EOC conciliates complaints, and unresolved cases go to the District Court, where damages for unlawful discrimination are uncapped and can include injunctions requiring the service be made accessible, plus reputational exposure from published findings. For government-facing suppliers, failing the WCAG-based requirements is a procurement and policy compliance problem.

Relation to WCAG: WCAG is the operative benchmark at every layer: the government's own requirement is WCAG Level AA (2.0 since 2013, with guidance tracking newer versions), the Recognition Scheme judges against WCAG criteria, and the EOC points service providers at WCAG as the standard of reasonable digital access. Building to WCAG 2.2 AA is the defensible position under the DDO.

How EqualWeb helps: EqualWeb gives Hong Kong organizations the WCAG 2.2 AA evidence trail the DDO environment rewards: automated plus expert audits, AI-and-human remediation, continuous monitoring, and documentation that answers an EOC complaint - or a Recognition Scheme submission - with proof instead of promises.

Q: Is there a web accessibility law in Hong Kong?
A: Not a standalone one. The Disability Discrimination Ordinance (Cap. 487) covers digital services through its goods-services-facilities provisions, so an inaccessible website can be unlawful discrimination. Government sites additionally must meet WCAG Level AA under Digital Policy Office requirements.

Q: What standard should a Hong Kong website meet?
A: WCAG Level AA is the benchmark: mandated for government websites since 2013 (WCAG 2.0, guidance tracking newer versions), used by the Web Accessibility Recognition Scheme, and treated by the EOC as the reference for reasonable digital access. Building to WCAG 2.2 AA covers it with headroom.

Q: Can someone sue over an inaccessible website in Hong Kong?
A: Yes. A person who cannot access your service can complain to the Equal Opportunities Commission, which conciliates and can support District Court proceedings under the DDO - where damages are uncapped and courts can order the service made accessible.

Q: What is the Web Accessibility Recognition Scheme?
A: An ongoing government-backed scheme (Digital Policy Office with the EOC and industry partners) that audits participating websites and apps against WCAG criteria and awards gold/silver recognition - Hong Kong's main lever for private-sector adoption.

## Main site content clusters (www.equalweb.com)

The domain-root clusters - distinct content from the /platform/ pages above:

**WCAG library**
- WCAG: What It Is, Who Writes It, and Which Version You Need - https://www.equalweb.com/wcag/ - WCAG explained: what the Web Content Accessibility Guidelines are, who at the W3C writes them, how 2.0, 2.1 and 2.2 differ, and what Level AA means.
- WCAG 2.1 Explained: Levels A, AA, AAA and 17 New Criteria - https://www.equalweb.com/wcag/2-1/ - WCAG 2.1 in plain English: 4 principles, 13 guidelines, 78 success criteria, what Level AA actually requires, and the 17 criteria new since WCAG 2.0.
- WCAG 2.2: The 9 New Criteria and How to Comply - https://www.equalweb.com/wcag/2-2/ - WCAG 2.2 is the current accessibility standard: 86 success criteria, 9 new since 2.1, one removed. What changed, who must comply, and how to get there.
- WCAG Compliance: What It Means and How to Achieve It - https://www.equalweb.com/wcag/compliance/ - What WCAG compliance means, what WCAG stands for, the difference between Level A, AA and AAA, and the steps to make a website WCAG compliant.
- All 86 WCAG Success Criteria, Explained in Plain English - https://www.equalweb.com/wcag/criteria/ - Every WCAG 2.2 success criterion with its level (A, AA, AAA), the version it arrived in, who it helps and how to meet it. Filter by level and principle.
- WCAG for PDFs: How the Standard Applies to Documents - https://www.equalweb.com/wcag/pdf/ - Does WCAG apply to PDF files? Yes - here is how each criterion maps to PDF tags, reading order and forms, where PDF/UA fits in, and how to test a document.
- WCAG Testing: How to Test a Website Against WCAG - https://www.equalweb.com/wcag/testing/ - What WCAG testing involves, automated vs manual testing, a step-by-step process to run a WCAG test, and how results become audit-grade documentation.
- Plus 87 success-criterion pages under https://www.equalweb.com/wcag/criteria/

**Guides**
- Accessibility Guides - Web Accessibility and ADA Compliance - https://www.equalweb.com/guides/ - In-depth, practical guides: what web accessibility is and how to achieve it, ADA compliance for websites with a working checklist, and the WCAG library.
- ADA Website Compliance: Requirements + 15-Point Checklist - https://www.equalweb.com/guides/ada-compliance/ - What the ADA requires of websites, how WCAG defines compliance, the 5-step path to an ADA-compliant site, and a 15-point checklist to work through today.
- WCAG 2.2 Compliance Checklist: Every A and AA Requirement - https://www.equalweb.com/guides/wcag-checklist/ - The full WCAG 2.2 compliance checklist: all 55 Level A and AA success criteria grouped by principle, each linked to a plain-language guide to passing it.
- Web Accessibility: The Complete Guide for 2026 - https://www.equalweb.com/guides/website-accessibility/ - What web accessibility means, the barriers that lock out 1 in 6 people, the WCAG, ADA and EAA rules, and the practical path to an accessible site.

**Free tools**
- Free Web Accessibility Tools - Try Them in Your Browser - https://www.equalweb.com/tools/ - Free accessibility tools: text magnifier, contrast checker, statement generator, PDF and WCAG checkers - plus 9 free EqualWeb Chrome extensions.
- Accessibility Statement Generator - Free - https://www.equalweb.com/tools/accessibility-statement-generator/ - Generate a ready-to-publish website accessibility statement free: conformance status, measures, limitations and feedback - copy or download the HTML.
- Highlight Links: Make Every Hyperlink Visible - https://www.equalweb.com/tools/highlight-links/ - See how link highlighting works: underlined, high-contrast hyperlinks that low-vision users can actually find. Try the live demo, add it to your site.
- Text Magnifier - Magnify Text Online, Free - https://www.equalweb.com/tools/text-magnifier/ - Free online text magnifier: paste any text and read it enlarged up to 10x. Plus how the EqualWeb widget adds hover text magnification to any website.

**Blog**
- The EqualWeb Blog - Web Accessibility, ADA, WCAG and PDFs - https://www.equalweb.com/blog/ - Practical articles on web accessibility: ADA compliance, WCAG techniques, PDF accessibility, assistive technology and the lawsuits shaping the field.
- A Comprehensive Guide to Making Videos Accessible - https://www.equalweb.com/blog/a-comprehensive-guide-to-making-videos-accessible/ - Create accessible videos that comply with WCAG and ADA standards. Improve usability and inclusivity with captions, transcripts, and audio descriptions.
- Accessible Fonts: How to Choose Readable Typography - https://www.equalweb.com/blog/accessible-fonts/ - What makes a font accessible: legibility features, size, spacing and contrast - with font recommendations and the WCAG criteria that govern typography.
- Accessible Navigation Design: Best Practices for 2026 - https://www.equalweb.com/blog/accessible-navigation-design-best-practices-for-2025/ - Inclusive navigation patterns that hold up in 2026: clear structure, keyboard and screen-reader support, consistent menus and WCAG 2.2-ready focus states.
- ADA Website Compliance Standards: What Changed in 2026 - https://www.equalweb.com/blog/ada-compliance-for-websites-in-2025-essential-standards/ - The ADA standards that apply to websites in 2026 - WCAG 2.1 AA as the benchmark, Title II deadlines, lawsuit trends and the practices that reduce risk.
- ADA Title II Deadline: WCAG 2.1 AA by April 2027 - The Plan - https://www.equalweb.com/blog/ada-title-ii-deadline-2027-plan/ - US state and local government websites must meet WCAG 2.1 AA by 26 April 2027 (or 2028 for smaller entities). An eight-month work plan that actually fits.
- ADA Web Accessibility Lawsuits in 2026: Numbers and Costs - https://www.equalweb.com/blog/ada-web-accessibility-lawsuits-2026/ - ADA web litigation in 2026: filing volumes, who gets targeted, what settlements really cost, and the defense that actually works.
- ARIA Attributes - https://www.equalweb.com/blog/aria-attributes-why-they-re-important-and-how-to-use/ - Learn why ARIA attributes matter for web accessibility and how to use them effectively to enhance usability for assistive technologies.
- WCAG Testing Methods Compared: Automated, Manual, Hybrid - https://www.equalweb.com/blog/comprehensive-wcag-testing-methods-in-2025/ - How the main WCAG testing approaches compare - automated scans, manual expert review and hybrid programs - and when each is enough for compliance.
- Creating accessible PDFs for reports and statements - https://www.equalweb.com/blog/creating-accessible-pdf-documents-for-financial-reports/ - Financial reports and statements are critical for stakeholders. But what happens when these documents aren&amp;#226;&amp;#128;&amp;#153;t accessible? We will guide...
- Ensuring Table Accessibility in PDFs: Best Practices - https://www.equalweb.com/blog/ensuring-table-accessibility-in-pdfs-best-practices/ - Learn how to make tables in PDFs accessible with proper structuring, tagging, and testing to enhance usability and meet ADA compliance standards.
- The European Accessibility Act, One Year On (2026 Review) - https://www.equalweb.com/blog/european-accessibility-act-one-year-on/ - A year after the EAA took effect: how enforcement is unfolding across member states, who is exposed - including non-EU sellers - and what to fix first.
- How AI is Revolutionizing Digital Accessibility - https://www.equalweb.com/blog/how-ai-is-revolutionizing-digital-accessibility/ - AI is reshaping digital accessibility with automation, real-time adjustments, and compliance solutions. Discover how AI-driven tools enhance accessibility.
- How to Convert Inaccessible PDFs to Fully Accessible Formats - https://www.equalweb.com/blog/how-to-convert-inaccessible-pdfs-to-fully-accessible-formats/ - Learn how to convert inaccessible PDFs into fully accessible formats, ensuring inclusivity, compliance with ADA and WCAG standards, and usability for...
- How to Make Interactive PDFs Accessible - https://www.equalweb.com/blog/how-to-make-interactive-pdfs-accessible/ - Learn how to create accessible interactive PDFs with our step-by-step guide. Improve usability, ensure compliance, and make your PDFs inclusive for all...
- How to Test Your Website for ADA Compliance - https://www.equalweb.com/blog/how-to-test-your-website-for-ada-compliance/ - Learn how to test your website for ADA compliance using automated and manual testing methods.
- How to Write Alt Text for Images in PDFs | web accessibility - https://www.equalweb.com/blog/how-to-write-alt-text-for-images-in-pdfs/ - Alt text is essential for making PDFs accessible to visually impaired users and meeting legal standards like WCAG and Section 508 . To write effective...
- How Voice Recognition Improves Web Accessibility - https://www.equalweb.com/blog/how-voice-recognition-technology-enhances-web-accessibility/ - Explore how voice recognition technology is making websites more accessible for users with disabilities and about its benefits, challenges, and future...
- Section 508 Compliance | Does It Apply to Your Business? - https://www.equalweb.com/blog/is-my-business-subject-to-section-508-compliance/ - Learn if Section 508 compliance applies to your business. Understand your obligations, avoid risks, and ensure your website meets accessibility laws.
- Maximizing ADA Tax Credits for Website Accessibility - https://www.equalweb.com/blog/maximizing-ada-tax-credits-for-website-accessibility-complia/ - Learn how to claim ADA tax credits for website accessibility compliance while ensuring your website meets WCAG standards.
- AI PDF Remediation Benchmark: 20 Healthcare PDFs Tested - https://www.equalweb.com/blog/pdf-accessibility-ai-remediation-benchmark/ - We ran 20 real healthcare-provider PDFs through EqualWeb's AI remediation engine and measured every file's accessibility report score before and after.
- Screen Reader Compatibility and Web Accessibility - https://www.equalweb.com/blog/screen-reader-compatibility-and-web-accessibility/ - Screen reader compatibility ensures digital content is accessible to visually impaired users. Learn how to optimize your website for screen readers.
- Step-by-Step Guide to Tagging PDFs for Accessibility - https://www.equalweb.com/blog/step-by-step-guide-to-tagging-pdfs-for-accessibility/ - Learn how to tag PDFs for accessibility with this step-by-step guide. Ensure compliance, usability, and inclusivity for all users.
- Font and color importance in pdf accessibility - https://www.equalweb.com/blog/the-importance-of-font-and-color-choices-in-pdf-accessibilit/ - Font and color choices are essential for PDF accessibility. Learn to create documents that are readable for all users, including those with visual...
- Assistive Technology in Web Accessibility - https://www.equalweb.com/blog/the-road-to-an-equal-web-includes-assistive-technology/ - Assistive technology bridges the gap for digital inclusion. Learn how web accessibility and assistive tools work together to create an inclusive online...
- WCAG 3.0: What Is Coming, When, and What To Do Now - https://www.equalweb.com/blog/wcag-3-0-what-to-expect/ - WCAG 3.0 is a W3C working draft, not a standard you can meet yet. What changes - outcomes, scoring, scope - the timeline, and what to do today.
- Web Accessibility Certification &amp; Compliance - https://www.equalweb.com/blog/web-accessibility-certification/ - Learn what web accessibility certification is, why it matters, and how we can help your business demonstrate compliance with ADA and WCAG standards.
- Web accessibility: test and optimize for all browsers - https://www.equalweb.com/blog/web-accessibility-how-to-test-and-optimize-for-all-browsers/ - Web accessibility isn&amp;#226;&amp;#128;&amp;#153;t just about inclusivity; it&amp;#226;&amp;#128;&amp;#153;s about making sure your website works seamlessly across all...
- Web Accessibility Initiative (WAI) Explained - https://www.equalweb.com/blog/web-accessibility-initiative/ - Understand the role of the Web Accessibility Initiative (WAI) in shaping inclusive web standards. Learn how EqualWeb supports your compliance journey.
- Website Disability Access: Global Laws and History - https://www.equalweb.com/blog/website-disability-access-countries-and-history/ - Explore web accessibility laws worldwide and key milestones in digital inclusion. Learn how regulations impact businesses and compliance strategies.
- What is PDF Accessibility and Why is it Important? - https://www.equalweb.com/blog/what-is-pdf-accessibility-and-why-is-it-important/ - Learn the importance of PDF accessibility and discover how to make PDFs usable for everyone, ensuring inclusivity and compliance with legal standards.
- Why Businesses Are Struggling with Accessibility - https://www.equalweb.com/blog/why-businesses-are-struggling-with-digital-accessibility/ - Discover the key challenges businesses face in digital accessibility in 2025. Learn why companies struggle with compliance, implementation, and...

**EqualWeb vs. alternatives**
- EqualWeb vs. Alternatives - Compare Accessibility Platforms - https://www.equalweb.com/go/ - Side-by-side comparisons of EqualWeb and other web accessibility platforms: features, certified expert services, compliance coverage and pricing.
- EqualWeb vs accessiBe - Accessibility Platforms Compared - https://www.equalweb.com/go/accessibe.html - Compare EqualWeb and accessiBe: widget, certified human experts, managed compliance, PDF accessibility tools, API and monitoring - side by side.
- EqualWeb vs AccessiWay - Accessibility Platforms Compared - https://www.equalweb.com/go/accessiway.html - Compare EqualWeb and AccessiWay: widget, certified human experts, managed compliance, PDF accessibility tools, API and monitoring - side by side.
- EqualWeb vs AudioEye - Accessibility Platforms Compared - https://www.equalweb.com/go/audioeye.html - Compare EqualWeb and AudioEye: widget, certified human experts, managed compliance, PDF accessibility tools, API and monitoring - side by side.
- EqualWeb vs Level Access - Accessibility Platforms Compared - https://www.equalweb.com/go/level-access.html - Compare EqualWeb and Level Access: widget, certified human experts, managed compliance, PDF accessibility tools, API and monitoring - side by side.
- EqualWeb vs Monsido - Accessibility Platforms Compared - https://www.equalweb.com/go/monsido.html - Compare EqualWeb and Monsido (now Acquia Optimize): monitoring, remediation, certified experts, PDF accessibility and documentation - side by side.
- EqualWeb vs Siteimprove - Accessibility Platforms Compared - https://www.equalweb.com/go/siteimprove.html - Compare EqualWeb and Siteimprove: widget, certified human experts, managed compliance, PDF accessibility tools, API and monitoring - side by side.
- EqualWeb vs UserWay - Accessibility Platforms Compared - https://www.equalweb.com/go/userway.html - Compare EqualWeb and UserWay: widget, certified human experts, managed compliance, PDF accessibility tools, API and monitoring - side by side.

**About EqualWeb**
- About EqualWeb - The Hybrid Accessibility Platform Company - https://www.equalweb.com/about/ - Who is behind EqualWeb: the company, the team of certified accessibility experts, careers, the partner and affiliate programs, and press coverage.
- EqualWeb Affiliate Program - Program Update - https://www.equalweb.com/about/affiliate/ - The EqualWeb Affiliate Program is closing to new registrations. Existing affiliates keep their terms until December 31, 2026 - new partners welcome.
- Careers at EqualWeb - Accessibility Career - https://www.equalweb.com/about/careers/ - Accessibility careers at EqualWeb: open roles in development, sales and solution integration - and a mission of digital equality your work actually serves.
- Customer Stories - What EqualWeb Users Say - https://www.equalweb.com/about/customers/ - Real reviews from EqualWeb partners and customers: agencies, developers and businesses on the widget, the platform, the support and the partnership.
- The EqualWeb Partner Program - Partner With Us - https://www.equalweb.com/about/partners/ - The EqualWeb Partner Program: help your clients achieve ADA compliance and accessibility with the trusted EqualWeb solutions - join thousands of partners.
- Press and News - https://www.equalweb.com/about/press/ - Stay up to date with the latest press releases and company news from EqualWeb: product milestones, WCAG 2.2 compatibility, client stories and analysis.
- Security &amp; Privacy at EqualWeb - How We Protect Data - https://www.equalweb.com/about/security/ - Security at EqualWeb: MFA/SSO access controls, secure development, encryption, WAF and DDoS protection, continuous monitoring and disaster recovery.
- Enterprise Single Sign-On (SSO) - https://www.equalweb.com/about/sso/ - Sign in to EqualWeb with the directory you already run: SAML 2.0 and OpenID Connect, sessions on your own hostname, offboarding enforced at the source.
- Who We Are - https://www.equalweb.com/about/who-we-are/ - EqualWeb is a software development company that makes the web accessible for people with disabilities - AI technology plus in-house accessibility experts.

**Legal**
- Legal - Terms, Privacy &amp; Accessibility - https://www.equalweb.com/legal/ - The EqualWeb legal library: Terms of Service, Privacy Policy, our Accessibility Statement and the statement example templates in 14 languages.
- Accessibility Statement - https://www.equalweb.com/legal/accessibility-statement/ - EqualWeb's accessibility statement: conformance status, measures taken, compatibility with browsers and assistive technology, and how to reach us.
- Privacy Policy - https://www.equalweb.com/legal/privacy/ - The EqualWeb Privacy Policy: what information is collected, how it is used and shared, retention, your rights, and how to contact us about privacy.
- Terms of Service - https://www.equalweb.com/legal/terms/ - The EqualWeb Terms of Service: applicability, the site and services, user accounts, licensing, payment, liability and all legal terms of use.