When an interested customer never becomes an enquiry
A customer finds your service, decides you may be a good fit and starts your contact form. They fill in several fields, then encounter an unclear error message. Or they use a keyboard rather than a mouse and cannot reach the submit button. They leave. Your business sees no enquiry and has no obvious sign that someone tried to contact you.
This is not only a technical concern. If your contact, quote request or consultation form is the main route into your business, it is part of the service you provide before work begins. A form should let a customer understand what is being asked, provide the information they reasonably have, and know whether their request was sent.
The issue can affect more people than owners expect. Statistics Canada reported that 17% of Canadians with disabilities experienced at least one Internet-accessibility barrier in 2022. Eleven per cent experienced a barrier when booking appointments, services or reservations online. Those figures do not tell you whether your individual form has a problem, but they are a good reason to test an important customer task rather than assume it works for everyone.
What “accessible enough to enquire” means
Accessibility means removing avoidable barriers so more people can use a website. For a contact form, that does not require you to become an accessibility specialist. Start with a practical question: can a customer identify each field, move through the form, correct a mistake and submit it without unnecessary difficulty?
A usable form has visible, specific labels; identifies required information before submission; works with a keyboard; makes the current field or button clear; and gives a helpful explanation when something is missing or invalid. Clear instructions and feedback help many customers, including people using screen readers, voice input, enlarged text, mobile devices or simply a poor internet connection and a small screen.
This is separate from deciding what information your form should collect. A form can ask sensible questions and still be hard to use. For help deciding what belongs in an initial quote request, read What Should Your Quote Request Form Ask? A Field-by-Field Guide for Service Businesses.
Forms Tutorial | Web Accessibility Initiative (WAI) | W3C
CAN-ASC-3.1:2025 – Plain Language - Accessibility Standards Canada
Run a 10-minute check on one important form
Choose the form connected to your most valuable customer action: requesting a quote, booking a consultation, registering for a service or contacting the team. Test it first on a phone, then on a desktop or laptop. Use sample information rather than a real customer’s details, and make a note of any step that feels uncertain or fails.
First, read the form before entering anything. Can a first-time visitor tell what each field is for? “Project details” is clearer than an empty box with no label. If a field is required, say so beside the field rather than waiting until the customer presses submit. Explain unusual requests, such as why photos, a postal code or a preferred contact method are needed.
Next, test the form without a mouse. On a desktop or laptop, press the Tab key repeatedly. You should be able to reach every field, checkbox, dropdown, consent option and submit button, then move away from each one. Watch the order: it should follow the form naturally rather than jumping unpredictably around the page.
As you tab through the form, check whether you can see where you are. A visible outline, highlight or other indicator should appear around the active item. If nothing changes on screen, a keyboard user may not know which button they are about to activate or where their next keystroke will go.
Then deliberately create an error. Leave one required field blank or enter an invalid email address and submit the form. A useful message identifies the problem and tells the customer how to fix it. “Error” alone is not enough. Ideally, the form keeps correctly entered information so the customer does not need to start again.
Finally, enlarge the page. Increase browser zoom on a computer or increase text size on a phone. Check that instructions remain readable, fields do not overlap and the submit button remains available. You are not judging whether the design looks identical at every size; you are checking whether the customer can still complete the task.
Easy Checks – A First Review of Web Accessibility | Web Accessibility Initiative (WAI) | W3C
[Draft] Visible Keyboard Focus - Easy Checks | Web Accessibility Initiative (WAI) | W3C
Decide what to fix first
Sort what you find by the effect on a customer. A vague label, such as “Message,” is usually a content issue. Rewrite it to explain the expected answer, such as “Briefly describe the repair or project.” An unexplained required field can often be corrected at the same time. These changes can improve the quality of enquiries as well as the experience of completing the form.
Treat barriers to submission as a higher priority. If a keyboard user cannot reach the submit button, the active field cannot be seen, an error cannot be understood, or text enlargement makes a control unusable, some prospective customers may be unable to enquire at all. Record the page, device, browser and failed step. A screenshot or short screen recording can help a website provider reproduce the issue.
More complex forms may need deeper review. Conditional questions that appear unexpectedly, file uploads, appointment selection, payment steps and multi-page applications introduce more ways for a customer to get stuck. If one of these is central to your business, ask for an accessibility review of the full task rather than requesting isolated cosmetic changes.
Once a customer submits successfully, they should also know what follows. A clear confirmation message and realistic response expectation prevent a completed form from becoming another uncertain moment. What Should Happen After a Customer Sends an Enquiry? A Website Checklist for Service Businesses explains what that confirmation should cover.
[Draft] Easy Checks – A First Review of Web Accessibility | Web Accessibility Initiative (WAI) | W3C
Know the limits of a short self-check
A form that works on your own phone is not necessarily usable for every customer. Equally, passing these checks does not prove that a website is fully accessible, works with every assistive technology or meets every applicable legal requirement. W3C describes quick checks as a way to find common problems, not a comprehensive evaluation.
Accessibility obligations can vary by organization and jurisdiction. Federal digital-accessibility regulations have a defined scope and should not be treated as a universal rule for every Canadian small business. If you need advice on legal obligations, seek advice appropriate to your organization and province rather than relying on a website checklist.
The useful next step is proportionate: test the form that matters most, document one failure at a time and fix anything that stops a person from contacting you. If the main enquiry route is difficult to use or technically unreliable, a focused redesign or professional accessibility review may be more valuable than adding another promotional section to the homepage.
[Draft] Easy Checks – A First Review of Web Accessibility | Web Accessibility Initiative (WAI) | W3C
Guidance on Digital Technologies Accessibility Regulations - Canada.ca