Insights / Article / Design Services
ArticleAccessible design is better design
Accessibility widens your audience and improves usability for everyone. Readable contrast, clear structure and testing with real people are where to start.
Accessibility widens your audience and improves usability for everyone. It is often treated as a compliance task, something to check just before launch so that a legal box can be ticked. That framing undersells it. The changes that help a person with a visual impairment or a motor difficulty almost always help everyone else as well.
Think of the people who use your website or app on any given day. Someone reading on a phone in bright sunshine. Someone holding a child in one arm and tapping with the other thumb. Someone whose first language is not English. Someone recovering from an eye operation, or simply getting older and finding small grey text harder to read than they used to. None of them would call themselves disabled, and all of them benefit from accessible design.
The business case is about usability, not only compliance
Many countries now have laws or public-sector rules requiring digital services to meet accessibility standards, most often the Web Content Accessibility Guidelines. Those obligations are real, and the risk of complaints or legal action is a reasonable reason to act. But organisations that only aim for compliance tend to do the minimum, late, and at high cost.
The stronger argument is commercial. Every customer who cannot read a price, find a button or complete a form is a customer you lose. Clear contrast, sensible structure and forgiving forms reduce abandoned baskets, support calls and complaints across your whole audience. Accessible pages are also easier for search engines to understand, because the same structure that helps a screen reader helps an indexing robot.
Colour contrast: make text readable
Make text readable against its background. Low-contrast text, such as pale grey on white or white on a light brand colour, is one of the most common accessibility failures and one of the easiest to fix. It often comes from a design that looked elegant on a large, high-quality monitor in a dim studio and fails on a cheap laptop by a sunny window.
The accessibility guidelines set a minimum contrast ratio of 4.5 to 1 for normal body text and 3 to 1 for large text. Free contrast checkers will tell you in seconds whether a combination passes. The practical step is to check your brand palette once, mark which colour pairs are safe for text, and build those pairs into your design system so nobody has to think about it again.
- Check body text, links, button labels and text placed over images.
- Do not rely on colour alone to carry meaning; add an icon, label or pattern.
- Make sure focus outlines and error messages are clearly visible.
- Test in bright light and on a mid-range phone, not only on a designer’s screen.
Clear structure: headings, labels and logical order
Use headings, labels and logical order. People using screen readers often move through a page by jumping from heading to heading, much as a sighted reader scans. If the headings are missing, or are just bold text styled to look like headings, the page becomes one long block with no way in.
The same discipline helps everyone. A page with clear, descriptive headings is easier to scan. A form where every field has a visible label, rather than placeholder text that vanishes when you start typing, is easier to complete and easier to check before submitting. A logical tab order means keyboard users, and anyone filling in a long form quickly, move through it in the sequence they expect.
Common structural fixes
- Use real heading levels in order, with one main heading per page.
- Give every form field a visible label and every image meaningful alternative text, or mark decorative images as such.
- Write link text that makes sense on its own: “Download the pricing guide” rather than “Click here”.
- Make sure everything can be reached and used with a keyboard alone.
- Explain errors in plain words next to the field that needs fixing.
Automated checkers help, but only so far
Automated tools catch missing labels and low contrast quickly, but they cannot tell you whether alternative text is meaningful or whether a journey makes sense. Use them as a first pass, never as the final word.
Test with people who have different needs
Include users with different needs in testing. A design can pass every automated check and still be confusing for someone using a screen reader, voice control or a switch device. The only reliable way to find those problems is to watch real people try to complete real tasks.
This does not have to be a large research programme. Recruiting four or five participants with a mix of needs for each round of usability testing will surface most serious problems. Specialist recruitment agencies and disability charities can help find participants, and they should be paid for their time like any other research participant.
We had passed the audit, so we assumed we were fine. Watching a screen reader user try to book an appointment showed us three dead ends in ten minutes.
Digital product manager, healthcare client
Build it in rather than bolt it on
The cost of accessibility depends almost entirely on when you start. Choosing an accessible colour palette at the brand stage costs nothing. Changing it after hundreds of pages and templates have been built is expensive. The same is true of components: an accessible button or form field built once into a design system is reused everywhere, while fixing each instance by hand takes weeks.
There are trade-offs. Some striking visual effects, such as text laid over busy photography or very light typography, are hard to make accessible and may need to be dropped or reworked. That can feel like a creative loss. In practice, designers usually find that working within clear constraints produces cleaner, more confident work.
A sensible starting point is a short audit of your five most important journeys, such as signing up, buying, booking or contacting support. Fix the contrast and labelling issues first, because they are cheap and affect the most people. Then add one or two participants with access needs to your next round of user testing, and make accessibility checks part of the definition of done for every new feature.
Source: Intelliversal analysis.
