How can a small-business website work better for older customers?

An older customer hears about your bookkeeping practice from a neighbour and opens your website on a tablet. They want to know whether you work with a business like theirs and how to call. The page offers tiny menu labels, a long promotional banner, and a form that gives no clear confirmation. The problem is the journey, not the customer’s age.

Make the important task easy to read, understand, and finish. Put the service, who it is for, the area served, and a clear next step in ordinary page content. Check that text can be enlarged, controls are easy to select, and a person can still contact you if a form or booking tool fails. These choices help many visitors, not only older ones.

Older customers are online, but age is not a usability test

Statistics Canada’s Canada at a Glance 2023, Table 20, reports that 82.6% of Canadians aged 65 and older used the Internet for personal use in 2022. The underlying Canadian Internet Use Survey covers people living in the ten provinces, excluding long-term residents of institutions; responses marked “not stated” are left out of the calculation. This is a national measure of Internet use, not a count of visits to small-business websites, an Ottawa–Gatineau estimate, or proof that a particular design increases inquiries.

The figure is a reason to include older people in the audience you consider. It is not a reason to treat them as one uniform group. Some customers use a phone every day; some prefer a desktop, a call, or a family member’s help. A website should support the task without asking anyone to disclose their age or assuming they cannot manage technology. The W3C Web Accessibility Initiative’s guidance for older users explains that changes in vision, dexterity, hearing, or concentration can overlap with accessibility needs. Those needs vary between people and circumstances.

Start with a service decision, not a font-size debate

Choose a real task before changing the design. For a local accounting or bookkeeping site, a visitor might need to answer: “Do you work with sole proprietors, do you serve my area, and how do I arrange an introductory conversation?” Try finding those answers from the home page without inside knowledge of the business.

Write the service name in a heading and explain it in familiar terms. State the fit and any limits honestly. Put the service area where someone deciding whether to get in touch will see it. Use a contact link whose label says what happens next, such as “Ask about bookkeeping services.” If a call is available, show the number as text and a working phone link; do not hide it inside an image or a menu that is hard to open.

This is an illustrative task, not a claim about a particular client. A repair shop might need hours, address, and entrance information first. A clinic may need to explain how an appointment starts, while avoiding a request for sensitive details in an ordinary inquiry form. The useful content order comes from the customer’s question, not from a template for “senior-friendly” pages.

Let readers enlarge the page without losing the answer

Readable text involves more than choosing a large default font. Make body copy legible, use a clear heading hierarchy, allow breathing room between lines and sections, and keep text and controls distinct from their backgrounds. Avoid putting essential service details in a graphic whose words cannot resize or be selected.

Try the page with the browser’s text or page zoom increased. The W3C’s resize-text guidance explains the accessibility requirement that text can reach 200% of its original size without loss of content or function. Watch for clipped headings, overlapping buttons, hidden form labels, and a contact action pushed off screen. Test both a wide browser window and a phone-sized viewport. The goal is a usable page, not merely a zoom control in the header.

If a service page becomes a wall of text at larger sizes, improve its structure. Short, descriptive headings let someone return to the section they need. Plain-language sentences reduce rereading. A list of services may be useful, but each label still needs enough explanation to let a prospective customer decide whether it fits. Do not replace necessary detail with vague promises such as “solutions for every stage.”

Make choices and controls easy to identify

On a phone or tablet, a visitor should be able to distinguish the menu, the service links, and the contact action without guessing from tiny icons. Leave space between nearby controls. The W3C’s target-size guidance sets a minimum of 24 by 24 CSS pixels for pointer targets, with specified exceptions including sufficient spacing. That is a floor for accessibility, not a recommended size for every important button. A large, clearly labelled call or inquiry action can be easier to use than a small icon that technically meets a minimum.

Check the page with a keyboard as well as touch. Can you see which link has focus? Does the menu open and close? Can you move through a form in a sensible order? A hover-only explanation will not help someone using touch, and an icon without a name may be unclear to someone using assistive technology. The same review can reveal friction for a visitor with a temporary injury or someone trying to use a phone on a moving bus.

Avoid urgent countdowns, moving text, and several competing pop-ups around the contact path. They can interrupt a person’s place in the page. If a promotional notice is genuinely needed, make it easy to dismiss and keep the service answer available. Simplicity is useful when it protects the task; it does not mean removing options customers actually need.

Give a form a clear beginning and end

An inquiry form should explain what it is for, ask only for information needed to route the first conversation, and label each field in visible text. Explain required fields before submission. If something goes wrong, identify the field and how to correct it without clearing everything the visitor entered. After submission, show a clear confirmation of what happened and what to expect next, without promising a response time the business has not committed to.

For an accounting practice, the first contact can ask about the broad service need and preferred reply method. It need not ask for tax documents or account credentials. If an embedded booking tool is used, explain what kind of appointment it books and provide a contact alternative when the tool is unavailable. A visible phone or email path may also suit someone who simply prefers a conversation. Verify that every option reaches the business and that staff know who responds.

The alternative should be genuine. A phone number that is an unclickable image or an inbox nobody monitors only creates a second dead end. Review the contact details whenever hours, staff responsibilities, or service areas change.

Test with people and with realistic conditions

Begin with a short task script: find a relevant service, decide whether the business serves your area, then start contact. Ask participants to say what they expect a link or control to do before selecting it. Observe where they hesitate and which wording they use. If possible, include older people with different devices and experience, and compensate them appropriately for their time. Do not ask one participant to represent every older customer.

Run your own checks too: enlarge text, use the keyboard, try a narrow screen, follow the service link, and submit a test inquiry. Keep a note of the page, device, task, and exact point of difficulty. If a family member helps a customer navigate, ask whether the site still lets the customer understand the decision and choose a contact method themselves. Do not replace direct user feedback with an automated score.

Prioritize a blocker that stops the task before polishing a less important detail. If the service fit is unclear, fix the words and page structure. If the call button cannot be selected, fix the control. If the form fails silently, fix the error and confirmation path. Retest after the change; a visually cleaner page can still have the same broken journey.

This work takes content decisions, interaction design, and technical testing. A website partner can help map the customer task, implement responsive and accessible controls, and test the form end to end. The owner still supplies accurate service boundaries and maintains the contact details. If your site makes a useful service hard to understand or reach, discuss a clearer website with Red Comet. We design and develop business websites around clear content and a usable inquiry path.

Sources

• Statistics Canada, Canada at a Glance 2023: Digital society, Table 20, custom tabulation of the 2022 Canadian Internet Use Survey and its population notes.
• Statistics Canada, Canadian Internet Use Survey, 2022, released July 20, 2023; survey collection and context.
• W3C Web Accessibility Initiative, Older Users and Web Accessibility, updated November 20, 2025.
• W3C, Understanding Resize Text and Understanding Target Size (Minimum), WCAG 2.2 explanatory guidance.