Compliance & Legal

Understanding accessibility requirements and how Inclusify can genuinely help.

WCAG Guidelines

The Web Content Accessibility Guidelines define conformance levels:

  • Level A - Minimum requirements
  • Level AA - Most commonly required (recommended target)
  • Level AAA - Highest accessibility standard

WCAG 2.1 Level AA is the practical benchmark to build and test against: it is what EN 301 549 incorporates for web content, and what US settlements and demand letters are written around. Our scanner runs the axe-core rule set, which spans WCAG 2.0, 2.1 and 2.2.

Accessibility Laws

  • ADA (United States)
    The ADA names no technical standard for private-sector websites. Claims are brought under Title III against businesses that are places of public accommodation, and they are argued and settled around WCAG 2.1 Level AA. How far the statute reaches a website is still decided case by case.
  • EAA (European Union)
    The European Accessibility Act has been enforceable since 28 June 2025. It covers e-commerce and other services offered to consumers in the EU, wherever the provider is established, and it exempts microenterprise service providers - fewer than 10 employees and an annual turnover or balance-sheet total of €2 million or less. The exemption works differently for products, so confirm your own status before relying on it.
  • Other
    Section 508 (US federal agencies and their suppliers), AODA (Ontario, Canada), and EN 301 549, the European ICT standard whose web-content requirements incorporate WCAG 2.1 Level AA.

Our Approach: Reporting + Remediation Tools

Inclusify provides a comprehensive two-part solution: automated scanning to find issues, and an accessibility widget that provides alternative content access for users.

Automated Accessibility Scanning

  • • Daily scans powered by axe-core (industry-standard WCAG engine), from the Starter plan up
  • • Detailed reports highlighting violations by severity
  • • Track progress over time as issues are fixed
  • • Dated PDF compliance documentation on Pro and Enterprise
  • • Actionable guidance for developers

Accessibility Widget Features:

  • • High contrast and color adjustment modes
  • • Text resizing and font changes
  • • Animation and motion controls
  • • Keyboard navigation aids
  • • Pre-configured disability profiles
  • • Read-aloud, and a jump list of the page’s headings, landmarks and links

Being Honest About Accessibility

We don't believe in "magic AI fixes"

Some tools claim to automatically fix all accessibility issues with AI overlays. We think that's misleading. If your website has an accessibility problem - like missing alt text or a broken form - no JavaScript widget can truly "fix" it. A JS workaround is a bandage, not a solution.

The same honesty applies to the scanning half. Automated testing catches roughly a third of accessibility barriers; the rest needs manual testing with assistive technology, and no tool can guarantee compliance.

Our philosophy:

  • • Scan and report - so developers know what to fix
  • • Widget for preferences - give users control over their experience
  • • Fix the source - the real solution is fixing your HTML, CSS, and theme

We help you find issues and provide tools to improve user experience, but true compliance requires fixing problems at the source.

Accessibility statements

Inclusify generates an accessibility statement from your site’s own scan record and publishes it at a stable public URL that the accessibility widget links to. Included from Starter up, on each website’s page in the panel.

Three shapes, because they are three different documents:

  • EU public sector - the model statement prescribed by Commission Implementing Decision (EU) 2018/1523 under Directive (EU) 2016/2102. Prescribed wording, quoted from the Decision in each of the 23 official languages it was published in, with the three compliance-status options in the Decision’s own words, the three separate categories of non-accessible content, and the enforcement body for your Member State (and for Germany and Austria, your Land).
  • EAA private sector - the information Article 13(2) and Annex V of Directive (EU) 2019/882 ask a service provider to prepare and keep for as long as the service runs, including the evidence that the service is monitored on an ongoing basis.
  • General - the W3C/WAI shape, for anyone outside both, including sites addressing the ADA or Section 508.

What is pre-filled: the known limitations, from the site’s current open failures grouped by rule; the assessment section, naming Inclusify and the date and stating that no manual audit was carried out; and the review date. Every field is editable before you publish, and the last-reviewed date moves as the site keeps being scanned.

What it will not do: set the compliance status to fully compliant on the strength of a scan. Automated testing finds a subset of WCAG failures and cannot confirm the rest, and EN 301 549 covers considerably more than WCAG, so that claim requires you to record who evaluated the site. It also will not tell you which of the three shapes applies to you - that depends on what your organisation is and where it operates, and it is a question for your own legal advice.

Important Disclaimer

Inclusify is an accessibility enhancement tool, not a complete compliance solution.
Full WCAG compliance requires proper code remediation, professional audits, and ongoing monitoring. Always consult accessibility professionals and legal counsel for compliance questions.

Litigation Support

If you receive an accessibility legal demand, we can help with documentation, scan reports, and remediation planning. Having evidence of ongoing accessibility efforts can be valuable in legal discussions. Litigation support and the dated PDF record behind it are part of the Pro and Enterprise plans. Inclusify is not a law firm and does not give legal advice.

Contact: support@inclusifyapp.com