Accessibility (a11y)
Accessibility (often abbreviated a11y) is the practice of designing and building products that people with disabilities can perceive, operate, and understand.
Accessible products support keyboard use, screen readers, sufficient colour contrast, and clear structure. It is both an ethical baseline and a practical one: the same semantic structure and clarity that make a product accessible also make it more usable for everyone and more legible to machines.
How it works
The reference standard is WCAG, the Web Content Accessibility Guidelines, organised around four principles: content must be perceivable, operable, understandable and robust. In practice that means text alternatives for images, enough colour contrast, every function usable by keyboard, visible focus, forms with real labels and clear errors, captions for video, and markup that assistive technology can interpret.
Much of it is decided before any code is written, in the design: contrast, type size, target size, and not relying on colour alone to carry meaning.
Example
A booking form whose fields show their names only as placeholder text fails twice: the label vanishes as soon as someone starts typing, and a screen reader may not announce it at all. A visible <label> tied to each field, with errors that say what to fix, works for everyone.
In practice
When you commission a site, put accessibility in the brief as a requirement with a named target, usually WCAG at level AA, rather than a hope. Ask the developer how they test it: a good answer mentions keyboard-only checks, a screen reader on at least one phone and one computer, and automated scans run during the build, not only at the end. Ask too who is responsible for content added after launch, because a new image with no alt text or a PDF menu nobody can read undoes careful work within weeks.
Third-party pieces are the usual edge case. Booking widgets, chat bubbles, cookie banners and embedded maps come from other companies, and many are hard to use without a mouse. Test them like your own pages, and prefer suppliers that publish an accessibility statement. Video needs captions, and audio-only content needs a transcript. If a full audit is beyond the budget, fix the paths that earn money first: the contact form, the booking flow and the checkout. A short accessibility statement on the site, saying what you have done and how to report a problem, shows good faith and gives frustrated visitors a route other than leaving.
Why it matters for your business
A visitor who cannot complete your booking form with a keyboard or a screen reader is a lost enquiry, and they rarely tell you why they left. There is also legal exposure: in the EU, the European Accessibility Act applies accessibility requirements to many consumer-facing services such as online shops and booking flows, with microenterprises providing services exempt. Building to WCAG from the start costs little extra, while retrofitting a finished site means reworking forms, menus and colour contrast after the budget is spent. Many fixes, such as clear labels and readable text, also help older visitors and anyone on a phone in bright sunlight.
Common mistakes
- Treating accessibility as an audit at the end instead of a design and build requirement.
- Relying on automated checkers, which catch only a portion of real problems.
- Building custom buttons and menus from generic elements that keyboards and screen readers cannot use.
Questions people ask
Is my small business legally required to have an accessible website?
It depends on your country, sector and size. Public bodies are covered in many countries, including across the EU, and in the EU many private businesses selling to consumers online are covered too, while microenterprises providing services are exempt. Even where no law applies to you, accessible sites reach more customers, so it is worth checking the rules that apply locally.
How do I check if my website is accessible?
Start by using the site with only the keyboard: press Tab through every page and complete a form. Then run a free automated checker, read every image's alternative text, and try a screen reader such as the one built into your phone. For a fuller picture, have a specialist audit the site against WCAG.
Does accessibility help SEO?
Indirectly. Google does not rank pages on an accessibility score, but much of the same work helps search engines too: descriptive alternative text, a clear heading structure, real links and readable text. Accessible pages also tend to be easier for AI engines to parse, because the structure that helps a screen reader helps a crawler.