How easy is it to arrange a centre visit from your phone?

Begin on the page a parent might actually open

Your homepage is a useful starting point, but families may arrive on a room page or a page about your learning approach. Open one of those pages on your phone. Can you work out which centre it belongs to, where it is, and how to ask about a visit?

For a group of centres, check that the enquiry goes to the centre the family is reading about. Asking parents to choose again from an unfamiliar list can create an unnecessary extra step. The location should remain clear as they move towards the form.

Choose a button that says what will happen

Use everyday wording such as “Arrange a visit” or “Ask about a visit”. Place the invitation where it makes sense: near the opening information and after a section that helps families decide whether your centre could suit them. Avoid making the footer the only place to contact you.

If submitting the form sends a request rather than reserving a time, say so. For example: “Tell us when you would like to visit and our team will contact you to arrange a time.” A parent should not leave believing they have a confirmed appointment when your team still needs to check availability.

Make the tap comfortable

Try the button while holding your phone normally. Can you tap it without hitting a nearby link? Give important controls enough room and separation, especially around menus and form buttons. Check that a banner or floating chat bubble does not cover the next step.

Increase the text size and try again. Do words disappear, overlap, or push the button off the screen? These checks can reveal useful fixes, although they are not a complete accessibility assessment. Ask your website provider to investigate anything you cannot comfortably read or operate.

Keep the first enquiry manageable

Ask for what your team needs to start the conversation. A name, a way to reply and a short message may be sufficient; make extra questions optional unless they are needed at this stage. A visit request does not have to collect everything required for enrolment.

Each box should have a clear label that remains visible as the parent types. Mark required fields and explain any unusual requirements before submission. These are among the practices covered in the W3C’s guidance on accessible forms. On your phone, also check whether moving between fields feels straightforward.

Test mistakes as well as success

Leave a required field blank and try to send the form. Does it explain what to fix, in words you understand? Correct the mistake and check that information you already entered is still there. Then submit a clearly marked test enquiry using your own contact details.

Look for a clear confirmation and check that the message actually reaches the right person. W3C guidance recommends feedback for both successful submissions and errors. Explain what happens next, and only promise a response time your centre can maintain. If the form cannot send, provide another way to contact the team.

Watch what happens while the page loads

Try the journey using mobile data as well as Wi-Fi. Notice whether a large photograph delays the useful information or whether a button moves just as you try to tap it. You are looking for obstacles, not chasing a perfect score.

If photos seem slow, ask your provider whether the site delivers appropriately sized images for different screens. Google’s web.dev guidance explains this approach. It can reduce unnecessary image downloads while keeping photos clear. You can keep a welcoming visual style without asking every phone to load the largest available file.

Fix one obstacle first

Choose the issue most likely to stop a family completing an enquiry, fix it, and repeat the same journey. If you are planning your first website, ask to try this process on a phone before launch. Seeing a form work from beginning to end is more useful than simply being told a design is mobile friendly.