ComplyPages

Legal Disclaimer

Last updated: 5 July 2026

1. Purpose of ComplyPages

ComplyPages provides practical accessibility QA and EAA-readiness support for public website transaction flows.

Our services may include free snapshots, developer-ready fix packs, retesting, monitoring, and related reporting for public customer flows such as checkout, booking, ticketing, enrollment, payment, login, and form submission.

ComplyPages is designed to help website owners, developers, web agencies, and platform suppliers identify visible accessibility risks and prioritise practical improvements.

2. Not legal advice

ComplyPages does not provide legal advice.

The information, reports, snapshots, issue descriptions, recommendations, and website content provided by ComplyPages are for general information and practical accessibility QA purposes only.

You should not rely on ComplyPages reports as legal advice, legal interpretation, regulatory advice, or a substitute for advice from a qualified lawyer, accessibility auditor, or compliance professional.

If you need a legal opinion about the European Accessibility Act, national accessibility laws, enforcement risk, contractual obligations, procurement obligations, or regulatory exposure, you should consult a qualified legal adviser.

3. No certification or compliance guarantee

ComplyPages does not certify that a website, app, service, organisation, product, or digital flow complies with:

  • The European Accessibility Act;
  • WCAG;
  • EN 301 549;
  • National accessibility laws;
  • Consumer protection laws;
  • Equality or anti-discrimination laws;
  • Procurement requirements;
  • Any other legal, technical, or regulatory standard.

A ComplyPages report does not mean that a website is compliant or non-compliant. It is a practical report based on selected observations and testing methods.

4. Selected flow scope

Unless otherwise agreed in writing, ComplyPages reviews selected public pages or selected public transaction-flow states.

Issues may exist outside the reviewed pages or may appear only under specific browsers, devices, screen sizes, operating systems, assistive technologies, user accounts, languages, locations, payment methods, booking conditions, third-party widgets, cookie-consent states, A/B test variants, network conditions, or time-based scenarios.

A report may not identify every issue that exists on a website.

5. Automated and manual review limitations

ComplyPages may use automated tools, structured review methods, and manual observations. Automated accessibility checks are useful but limited. They cannot identify all accessibility issues, usability barriers, legal risks, or user-experience problems.

Some accessibility issues require deeper manual testing with assistive technologies, user testing, code review, design review, or legal analysis.

ComplyPages reports should therefore be treated as practical QA outputs, not full accessibility audits unless a separate written agreement states otherwise.

6. Public-page and safe-review limitation

ComplyPages is generally focused on public website flows.

Unless expressly agreed, we do not:

  • Access private admin areas;
  • Bypass authentication, paywalls, or CAPTCHA;
  • Exploit vulnerabilities;
  • Perform penetration testing;
  • Make real purchases;
  • Submit sensitive or record-creating forms;
  • Access customer accounts;
  • Collect private customer records;
  • Review source code repositories;
  • Modify client systems.

For more details, see our Scanner Ethics Policy at /legal/scanner-ethics.

7. Third-party platforms and embedded services

Many transaction flows depend on third-party systems, such as booking engines, e-commerce platforms, payment providers, ticketing platforms, course platforms, form builders, consent banners, chat widgets, analytics scripts, maps, video players, and embedded content.

ComplyPages may identify visible accessibility issues in or around these components, but implementation responsibility remains with the website owner, developer, agency, platform provider, or relevant third-party supplier.

8. Suggested fixes and code examples

ComplyPages reports may include suggested fixes, implementation notes, code examples, acceptance criteria, or developer guidance.

These suggestions are provided for practical reference only. They must be reviewed, adapted, tested, and approved by the client’s developer, agency, platform supplier, or qualified technical team before implementation.

ComplyPages is not responsible for code changes made by third parties based on our reports unless separately agreed in writing.

9. Retesting limitation

A retest checks whether specific previously reported findings appear to have been addressed under the retest conditions.

A passed retest does not guarantee full accessibility compliance, full EAA compliance, absence of other issues, future non-regression, or correct behaviour in every browser, device, user state, or third-party flow.

10. Monitoring limitation

Monitoring can help identify visible changes, new issues, or regressions in selected flows. Monitoring is not continuous unless explicitly agreed. It may not detect every change, error, issue, outage, or accessibility barrier.

11. No emergency or critical-system use

ComplyPages is not designed for emergency, safety-critical, medical, financial trading, life-support, or critical infrastructure use.

12. Client responsibility

Clients and website owners remain responsible for their websites, apps, content, services, legal obligations, implementation decisions, developers, agencies, suppliers, and ongoing accessibility maintenance.

13. Website content

The content on complypages.com is provided for general information. We try to keep it accurate and useful, but we do not guarantee that it is complete, current, legally accurate, or suitable for your specific circumstances.

14. External links

Our website and reports may link to third-party websites or resources. These links are provided for convenience only. We are not responsible for third-party content, accessibility, security, policies, or practices.

15. Limitation of liability

To the maximum extent permitted by applicable law, ComplyPages and Bobook Limited are not liable for indirect, incidental, special, consequential, punitive, or exemplary damages, including lost profits, lost revenue, lost data, lost goodwill, business interruption, or regulatory penalties arising from use of our website, reports, or services.

Nothing in this disclaimer excludes liability that cannot be excluded under applicable law.

16. Contact

Legal contact: legal@complypages.com General contact: hello@complypages.com

Operator: Bobook Limited, Venture Hub, 136 Capel Street, Dublin 1, D01 T2C9, Ireland.

Legal Disclaimer | ComplyPages