Loading...
If this is a follow-up enquiry, please use the same email address as before for smoother communication. (If you don't remember, a different one is fine.)
Basic Information
Accessibility remediation context
Existing findings
Initial remediation scope
Implementation context
Call preparation
Confirmations
Company Name
Enter your company name.
Primary contact
Enter the name of the main contact person for this enquiry.
Email address
Enter the email address we should use for scheduling and follow-up communication.
Role / Department
Please specify your role or department if applicable.
Company website
Share your company website, if available.
Industry
Please select your industry from the list. If not listed, select "Other" and specify.
Primary business location
Select the country or region most relevant to this enquiry. If not listed, select "Other" and specify.
Preferred timezone for communication
Select the timezone you would prefer to use for scheduling and communication.
Select the service that best matches your needs
Please select the service that best matches your needs. If you are considering multiple services, please select your top choice.
What would you like us to help fix?
Choose the option that best matches the website, product, or flow you have in mind.
Briefly describe the website, product, or flow.
What does it do, who uses it, and what needs to be fixed? A few sentences are enough.
Which market or audience is this mainly for?
This helps us understand the EU/UK context before the first call.
Is this linked to public-sector or procurement requirements?
This helps us see whether you may need a more formal audit or documentation process.
Do you need formal accessibility documentation?
For example, a formal audit report, certification, VPAT/ACR, or procurement documentation.
Public URL, if available
Share any public page that would help us prepare for the call.
Please do not include credentials, customer data, source code, unpublished links, or staging details here.
What prompted this request?
Select any that apply. This helps us focus the first call.
What existing findings or issue information do you have?
To plan implementation work, we usually need specific issues, affected pages or flows, and enough context to estimate the scope.
How specific are the issues?
This helps us see whether the findings are ready for implementation planning, or whether more review is needed first.
Briefly summarise the issues you want fixed.
Bullet points are fine. Please keep confidential details out of this form.
Which areas may need fixing?
Select any that may be relevant.
Roughly how many issues, screens, or components are involved?
An estimate is enough.
Is there a main user flow you want us to prioritise?
For example: landing page → pricing → sign-up → confirmation, or product page → checkout → payment confirmation.
What implementation context can you share at this stage?
A rough answer is enough. This helps us understand how close the request is to implementation work.
If we move forward, could codebase or repository access be arranged?
This helps us understand whether implementation support may be possible. No code or access details are needed here.
Could a staging, test, or login-protected environment be available later if needed?
This helps us understand how fixes could be checked. No links or access details are needed here.
What is the main frontend or website setup?
Select any that apply. Broad categories are enough for now.
Do you already have a preferred way to share or review code changes?
The final workflow can be confirmed later.
Who would review, merge, or deploy the changes on your side?
This helps us understand the handoff and release process. A rough answer is enough.
Is there any timing we should be aware of?
For example, a launch date, review window, internal check, or planned release.
What would you like to cover in the first 30-minute call?
Select any that apply.
Anything else we should know before the call?
You can share timing constraints, approval steps, accessibility concerns, or anything else that would help us prepare.
Terms of Service Agreement
Privacy Policy Acknowledgement
