Frequently Asked Questions
Common questions about EAA accessibility checks, snapshots, Fix Packs, and working with your developer.
Do you provide legal advice?
No. ComplyPages does not provide legal advice, legal certification, or a full legal compliance opinion. We provide practical accessibility QA for public website flows and developer-ready findings that your team can review and act on.
Do you need access to our codebase?
No. The free snapshot and initial review are based on public-facing website flows. We do not need access to your codebase, admin panel, analytics, orders, or customer data.
Do you make purchases or submit private forms?
No. We do not make purchases, submit sensitive forms, bypass logins, or create real customer records. We focus on public pages and safe review methods.
Can our developer or agency fix the issues?
Yes. That is the point. ComplyPages is designed to help your existing developer, agency, or platform supplier move faster by giving them clear, prioritized, developer-ready findings.
What is the difference between a free snapshot and a full Fix Pack?
The free snapshot is a short preview with a few visible observations. The full Developer-Ready Fix Pack provides deeper issue documentation, screenshots, reproduction steps, suggested fixes, acceptance criteria, and retest support.
Is this a full WCAG audit?
No. ComplyPages is focused on practical accessibility QA for customer-critical transaction flows. A full WCAG audit may still be needed for legal, procurement, or certification purposes.
Which flows do you check?
We focus on flows where customers take action: checkout, booking, ticketing, enrollment, payment, login, account creation, quote request, contact, and multi-step forms.
What happens after we fix the issues?
ComplyPages can retest the reported issues and update the status. For teams that want ongoing coverage, we can also monitor selected transaction flows for new issues or regressions.
See also our disclaimer, sample report and pricing.