When a business thinks about accessibility, it usually thinks about buildings: a ramp, a wide door, a parking bay. When it thinks about customer follow-up, it thinks about speed: did we reply, did we send the quote, did we chase the payment. The two rarely meet in the same conversation. Yet the follow-up is where many customers find out, quietly, whether the business works for them.
A quote that arrives only as a scanned image cannot be read by a screen reader. A reminder sent in pale grey text on a white background cannot be read by someone with low vision. A payment link that works only on a mouse does not work for someone who navigates by keyboard. A follow-up that insists on a phone call excludes a customer who is deaf. This piece argues that accessibility is not only a design or compliance topic, but an operational question: does the way we follow up let every customer actually complete what they came to do?
It is a hypothesis about a common blind spot. It does not claim to describe the experience of any particular group, and it does not replace advice from accessibility specialists or the people affected.
Why follow-up is where access is won or lost
Follow-up is the stretch of a customer relationship in which the customer has to do something: confirm an appointment, approve a quote, upload a document, pay an invoice, answer a query. Unlike browsing a website, these steps are transactional, and a failure at any one ends the transaction.
That makes them unusually exposed. A business may have a perfectly good website and still send a PDF form that cannot be filled in without a printer, a link to a portal that times out too quickly, or a voice-note-only update. Each of these is a small operational choice. Together they decide who can complete the process without asking for help, and who has to ask.
Asking for help is not neutral. Needing to phone, explain and wait takes time and some dignity, and many customers will simply give up. The business sees that as a lost sale or a late payment, and rarely connects it to how the message was built.
What the standards and the law say
The international reference point for digital accessibility is the Web Content Accessibility Guidelines. The W3C's overview explains that WCAG 2.2 is organised under four principles, namely that content should be perceivable, operable, understandable and robust, with testable success criteria at three levels. It applies to web content and, through related guidance, to documents and applications. It is a technical standard rather than an introduction, but its principles are easy to translate into everyday terms.
The W3C's business case for accessibility states that the global market of people with disabilities is over a billion people with a spending power of more than six trillion US dollars, and that accessible design often improves the experience for everyone. Those are global figures, supplied by the W3C, and they say nothing about a particular South African customer base. They do make the general point that excluding people is also a commercial choice.
South Africa's Promotion of Equality and Prevention of Unfair Discrimination Act, published on the Government site, exists to prevent and prohibit unfair discrimination and to promote equality. How it applies to a particular business's customer communications is a legal question, and one for qualified advice. The practical point is simpler: an inaccessible process can exclude people, and excluding people unintentionally is still excluding them.
An illustrative case
Consider an illustrative example, not a real case: a Bloemfontein physiotherapy practice with six therapists and two reception staff. Its follow-up process is efficient by any ordinary measure. After each appointment, a template email goes out with a PDF invoice and a coloured status line: green for paid, red for outstanding. Reminders follow by SMS, and anyone who has not paid within two weeks receives a call.
A patient who is partially sighted uses a screen magnifier and finds the invoice's small, light grey figures hard to read. The PDF is a scan, so her reader cannot read it aloud. The status colours mean nothing to a colour-blind patient. A patient who is deaf cannot take the chasing call and has asked twice for email only, but the system has no field for contact preference. A patient recovering from a stroke can manage a keyboard better than a touchscreen, and the payment link works poorly with it.
No one at the practice intended any of this. The receptionists are kind, and every one of these patients ends up paying after a conversation. But each had to ask, and each conversation cost the practice time as well.
The human tax: access and autonomy
The tax here is access: not being able to use the standard route and having to find another. It is repeated at every follow-up, and it is usually invisible to the people who designed the route.
The dividend on the other side is autonomy: the ability to read the invoice, approve the quote or settle the account on your own, at a time that suits you, without asking anyone. Many people, with and without disabilities, value that. A parent reading an invoice on a small phone in a school car park benefits from the same readable text, clear structure and big tap targets as a person with low vision.
Mellorca has looked at related ground in when digital-only leaves some customers behind and, on the employee side, in the employee locked out by a system built for someone else. The angle here is the operational one: the follow-up process is a system, and it can be designed.
What could realistically change
None of this requires a rebuild. Most improvements are choices in how routine messages are made.
- Send real text, not pictures of text. Quotes and invoices should be generated documents or plain email text, not scans or screenshots, so that assistive software can read them.
- Do not rely on colour alone. The W3C's design tips recommend adding a symbol or label to colour. "Paid" and "Overdue" should be written, not just coloured.
- Check contrast and size. Pale grey on white is common in templates and hard for many people to read. The W3C explains how to check contrast ratios.
- Make links and buttons usable by keyboard. A payment or approval link should work without a mouse, and be clearly identifiable as something to select.
- Record contact preferences. A single field for preferred channel, such as email, SMS, WhatsApp or phone, stops the wrong channel being used again and again. Treat it as personal information and keep it to what is needed.
- Offer more than one way to finish. A phone number, an email address and a link should all lead to the same result.
- Ask, and test. Invite customers to say what works for them, and try your own messages with a screen reader or zoomed in. A fifteen-minute test is more informative than any assumption.
The related customer who gets a different answer from every person is a reminder that consistency across channels is part of access too.
The business outcome
Customers complete quotes, confirmations and payments with fewer calls. Fewer messages are lost to unreadable formats. The business also reduces the risk of unintentionally excluding customers it would be glad to serve.
The trade-offs
- Several channels cost more to maintain. Each extra route to completion needs someone to monitor it.
- Preferences are personal information. A record that someone prefers email because of a hearing impairment is sensitive, and must be handled with care.
- Standards are not the same as lived experience. A message can meet a technical guideline and still be awkward for a particular person. Listening matters.
- Assumptions can be patronising. The aim is to widen the options, not to decide on someone's behalf what they need.
Why it matters
Accessibility is often treated as a specialist subject, handled after the "real" process is built. But for a customer, the follow-up is the process. If it can be completed independently, by the widest range of people, with the least effort, the business has made a quiet operational improvement that also happens to be the right thing to do.
Sources and further reading
- WCAG 2 Overview (last verified 10 October 2026)
- The Business Case for Digital Accessibility (last verified 10 October 2026)
- Designing for Web Accessibility – Tips for Getting Started (last verified 10 October 2026)
- Promotion of Equality and Prevention of Unfair Discrimination Act 4 of 2000 - South African Government (last verified 10 October 2026)
Related Mellorca reading
- The Slow Leak of Time Through Manual Reminders
- When Late Invoices Become Late Salaries
- The Owner Facing Illness With No One Who Knows the Systems