HARDLINE/

Journal /

Website Accessibility for Suffolk Small Businesses: A Practical Starting Point

What web accessibility means for a small business, why it matters for customers and contracts, and the most common problems you can fix without starting again.

A person testing a website on a smartphone held in hand beside a laptop on a cafe table

Web accessibility means making sure people can use your website regardless of disability, device or circumstance. That includes people who are blind or partially sighted and use screen readers or magnification, people who cannot use a mouse, people with hearing loss, and people with cognitive or learning disabilities. It also includes many more people in temporary situations: someone with a broken arm, someone reading in bright sunlight, someone on an old phone with a cracked screen.

For a small business, accessibility is often treated as something for large organisations to worry about. In practice, the most common accessibility problems are simple to fix, and fixing them makes the site easier for everyone to use.

Why it matters for a small business

Customers. A significant share of the UK population lives with a disability, and many more people have age-related changes to sight, hearing or dexterity. Suffolk has an older population than the national average, which makes accessibility particularly relevant for local businesses selling to the public.

Contracts. Businesses that supply councils, the NHS, universities or larger companies are increasingly asked about accessibility, and public sector websites are required to meet accessibility regulations. Even when your website is not directly in scope, buyers notice when a supplier's site is difficult to use.

The law. The Equality Act 2010 requires service providers to make reasonable adjustments so disabled people are not put at a substantial disadvantage. A website is part of how many businesses provide their services.

Search and usability. Many accessibility improvements, such as clear headings, descriptive links, text alternatives for images and good structure, also help search engines understand the page and make it easier for every visitor to use.

The standard to aim for

The widely used standard is the Web Content Accessibility Guidelines (WCAG), currently version 2.2. Most organisations aim for level AA. You do not need to read the full guidelines to make progress. The common problems below cover a large part of what goes wrong on small business websites.

Common problems and how to fix them

Low colour contrast

Pale grey text on white, or white text on a light photo, is hard to read for many people. Check your text and background colours with a free contrast checker. Body text should have a contrast ratio of at least 4.5 to 1.

Images without useful alt text

Screen readers announce images using their alt text. Missing alt text means the image is skipped or announced as a file name. Write a short description of what the image shows and why it is there. Decorative images can have empty alt text so they are ignored.

Forms without labels

Placeholder text inside a field is not a label. It disappears when someone starts typing and is often not read out properly. Every form field needs a visible label. Error messages should say what went wrong and how to fix it, not just turn the field red.

Keyboard traps and invisible focus

Try using your website with only the Tab, Enter and arrow keys. Can you reach every link, menu and button? Can you see where you are on the page? Many sites remove the focus outline for visual reasons, leaving keyboard users lost.

Headings used for styling

Headings should form a logical outline of the page: one main heading, then sections and subsections. Many sites use heading tags just to make text big, or skip levels, which makes the page confusing for screen reader users who navigate by headings.

Vague link text

"Click here" and "read more" tell a screen reader user nothing when links are read out in a list. Use link text that describes where the link goes, such as "read our guide to customs clearance".

PDFs instead of web pages

Menus, price lists and brochures uploaded as PDFs are often inaccessible and awkward on phones. Where possible, put the content on a web page.

Videos without captions

Add captions to videos, and avoid autoplaying video or audio.

How to check your own site

You can do a useful first check in an hour:

  1. Navigate the site using only the keyboard.
  2. Zoom the browser to 200 per cent and check nothing overlaps or disappears.
  3. Run a few pages through a free automated checker such as WAVE or the Lighthouse accessibility audit in Chrome.
  4. Turn on your phone's built-in screen reader (VoiceOver on iPhone, TalkBack on Android) and try to complete a simple task, like finding your contact details.

Automated tools find only part of the problems, but they are a good start.

Fixing problems without a rebuild

Most of the issues above can be fixed on an existing site: adjusting colours, adding alt text, labelling form fields, restoring focus styles, fixing headings and rewriting link text. A rebuild makes sense if the site is built on an old theme or page builder that makes accessibility hard to achieve, but it is rarely the first step.

A priority table for small businesses

If you cannot fix everything at once, fix things in this order:

Priority Problem Who it affects Effort to fix
1 Contact or booking form that cannot be used with a keyboard Keyboard and screen reader users Usually moderate
2 Missing form labels and unclear error messages Screen reader users, everyone Low
3 Low colour contrast on text and buttons People with low vision, everyone outdoors Low
4 Images without useful alt text Screen reader users Low
5 Headings used for styling rather than structure Screen reader users Low to moderate
6 Vague link text such as "click here" Screen reader users Low
7 Videos without captions Deaf and hard of hearing people, people watching without sound Moderate

Most of the low-effort fixes can be done in an afternoon by whoever edits the site. The form fixes may need a developer.

Accessibility and tenders

Suppliers to councils, the NHS and large companies are increasingly asked about website accessibility in tender documents. Having an audit report and an accessibility statement that says honestly where the site stands, and what you are fixing, gives a clear answer. Our accessibility audit covers this, and our Haverhill page discusses why it matters for manufacturers who supply larger customers.

Make it part of the routine

Accessibility is not a one-off project. Every new page, image and form is a chance to get it right or wrong. A short checklist for whoever updates the site, covering alt text, headings, link text and contrast, prevents most new problems. If you are planning a new site, make accessibility part of the brief from the start; it costs far less than fixing it afterwards.

The takeaway

Accessibility is not a separate project bolted onto a website. Most of it comes down to habits: label every form field, describe every meaningful image, keep contrast strong, use headings in order and test with a keyboard. Start with your contact form, because that is where barriers cost you customers directly. Then work through the priority table above, one row at a time, and add the checks to whatever routine you use when publishing new pages. If you want an independent view, an audit gives you a clear list in priority order.

Next

Got a site that isn't pulling its weight?

Tell us what the business does and what the website should be doing for it. We reply within one working day with honest thoughts and a rough price.

Start a project →