Dilawar Malik
Published
6 min read
Accessibility is often treated as a specialist subject, something to address after the real work is done. In practice, most accessibility fixes are simply good usability. A site that can be used by someone who cannot see the screen, cannot use a mouse, or cannot distinguish low-contrast text is also a site that is easier for everyone else: the visitor on a phone in bright sunlight, the visitor with a temporary injury, and the visitor who is simply in a hurry.
The fixes below are practical, and none of them requires a redesign. They address the problems that affect real visitors most often, and each one improves the experience for every visitor, not only for visitors with disabilities. Start with the ones that touch the most pages, and work through the rest in order of impact.
Make the whole site usable by keyboard
Many visitors navigate without a mouse, using the keyboard alone or a switch device. Every link, button, and form field on the site should be reachable by keyboard, in a sensible order, and it should always be clear which element is currently focused. A visible focus indicator, such as a clear outline around the focused element, is essential. Removing it for visual tidiness is one of the most common and most damaging accessibility mistakes.
Test the site by putting the mouse aside and using only the Tab key. Can you reach the main navigation, the search, and every form? Can you open menus and dismiss popups? Can you tell where you are at all times? If the answer to any of those questions is no, keyboard users are locked out of that part of the site, and so is anyone whose mouse has stopped working or whose hands are occupied.
Give every image and link a clear purpose
Images that carry information need a text alternative that conveys the same information. A chart, a diagram, or a photograph that illustrates a point should have alt text that explains what the image shows and why it matters. Decorative images, which add nothing, should be marked as decorative so screen readers skip them rather than announcing meaningless file names.
Links need the same care. A link that reads click here or read more tells a screen reader user nothing about where it leads, and it tells a sighted user little more. Link text should describe the destination: the guide it opens, the service it describes, or the action it starts. Descriptive links help every visitor, because they make scanning a page faster and more certain.
Fix contrast and text size so content is readable
Text that is too light, too small, or placed over a busy image is hard to read for many people, including older visitors and anyone reading on a phone outdoors. Body text should have strong contrast against its background, and it should remain readable when the visitor increases the text size in their browser. A layout that breaks when text is enlarged is a layout that fails the people who need larger text most.
Check the combinations that are most often overlooked: grey text on a white background, white text over a photograph, and small text in footers and captions. These are the places where contrast problems hide, because they look acceptable on a large, well-lit monitor and fail everywhere else. The same attention to small screens matters throughout the site, as the article on mobile-first design mistakes that cost service businesses enquiries explains: a page that is hard to read on a phone is hard to read for everyone.
Label forms clearly and explain errors helpfully
Every form field needs a visible, descriptive label that stays visible while the visitor types. Placeholder text alone is not a label, because it disappears as soon as the visitor starts typing, and it is often too light to read. A field labelled Your email address is clear to everyone, including a screen reader user who hears the label announced when the field receives focus.
Errors should be explained in plain language, beside the field that caused them, with a suggestion for how to fix the problem. An error message that only says invalid input helps nobody. One that says please enter an email address like name@example.com tells the visitor exactly what to do. Clear error handling reduces failed submissions for every visitor, not only for visitors using assistive technology.
Structure headings and landmarks so pages make sense
Headings are the skeleton of a page. Screen reader users often navigate by headings alone, jumping from one to the next to build a picture of the page. A page with a single heading level, or with headings used for visual effect rather than structure, is difficult to navigate that way. Use one main heading for the page title, then headings in a logical order that reflect the structure of the content.
The same principle applies to the overall page structure. Navigation, main content, and footer should be marked as distinct regions, so visitors using assistive technology can skip to the content they want. A skip link, which lets keyboard users jump past the navigation to the main content, is a small addition that makes a large difference on every page of the site.
Frequently asked questions
What is WCAG, and which level should I aim for
WCAG, the Web Content Accessibility Guidelines, is the internationally recognised standard for accessible websites. Level AA is the level most organisations aim for, because it addresses the barriers that affect the most people without imposing requirements that are impractical for most sites. Use it as a checklist, not as a one-time project.
Will accessibility fixes make my site look plain
No. Accessibility is about how a site works, not about removing visual design. Strong contrast, clear focus indicators, and well-structured pages can all be designed attractively. Many of the best-looking sites are also the most accessible, because their designers treated clarity as a design value rather than a constraint.
How do I test accessibility without specialist tools
Start with the keyboard test, a contrast checker, and a screen reader trial on the most important pages. Free automated checkers will catch some issues, such as missing alt text and contrast failures, but they cannot catch everything. Manual testing with real assistive technology, even briefly, reveals problems that automated tools miss.
Is accessibility a legal requirement for my website
It depends on the country, the sector, and the type of organisation. Public sector bodies in many countries have explicit duties, and accessibility law is expanding in several regions. Even where there is no direct legal duty, an inaccessible site excludes customers and creates avoidable risk. Treat accessibility as a quality standard, and the legal position becomes much simpler.
Where should I start if I have limited time
Start with keyboard navigation, image alternatives, contrast, and form labels, because those four areas affect the most visitors and the most pages. Fix them on the templates and the most visited pages first, then work through the rest of the site. A short, regular routine will improve accessibility steadily without needing a large project.
Accessibility fixes are usability fixes. A site that works for visitors who navigate by keyboard, who listen to the page, or who need stronger contrast is a site that works better for everyone who visits it.
