A phone enquiry form should be easy to finish without guessing
Review labels, errors and confirmation as part of the same customer task.
A contact form can fit within a phone screen and still be difficult to use. Placeholder text disappears after typing. A required field may be marked only by colour. An error may appear above the screen while the customer keeps pressing the button below.
Review the whole task from the customer's perspective: understand what is needed, enter it, correct a mistake and know whether the request was sent.
Keep instructions where they are needed
Use visible labels for fields. Explain unusual formats beside the relevant control. If a phone number is optional, say so; customers should not have to attempt submission to find out. Avoid asking for information that the business does not use.
W3C's form-label guidance explains the connection between labels and controls. That connection also helps when someone uses a screen reader or speech input rather than tapping directly.
Write errors that help someone recover
“Invalid input” gives little help. “Enter an email address such as name@example.com” points to a correction. Preserve the other fields so a customer does not have to write their project description twice.
Test with the phone keyboard open and with text enlarged. The submit button, privacy link and any error messages should remain reachable. If an upload fails, explain whether the enquiry can still be sent without it.
Do not mistake a click for a completed enquiry
The confirmation must follow a successful submission. If the connection fails, show a useful recovery step and a direct contact alternative. Staff should verify receipt during the acceptance test.
This review can identify practical accessibility improvements, but it is not a certification or a complete legal assessment. A broader accessibility review may be needed for your organisation. Faith Forge Labs includes these customer tasks in website design and focused repair work.