Accessibility (WCAG) for Service Websites

Accessibility (WCAG) for Service Websites: Making Your Site Usable for All Potential Customers

Introduction

Accessibility isn't just a legal consideration — it's a business opportunity. Approximately 16 million people in the UK live with a disability, and a significant proportion of those use assistive technologies to browse the web. If your service business website isn't accessible, you're excluding a substantial portion of your potential customer base before they've had the chance to enquire.

Beyond the ethical and commercial case, web accessibility also improves search engine performance. The principles that make a website usable for someone with a screen reader — clear structure, descriptive content, fast loading, keyboard navigability — are the same principles that help Google crawl and rank your site effectively.

This guide explains the Web Content Accessibility Guidelines (WCAG), which elements matter most for UK service businesses, and how to implement them practically without a complete website rebuild.

What Is WCAG and Why Does It Apply to You?

The Web Content Accessibility Guidelines (WCAG) are an internationally recognised set of technical standards developed by the World Wide Web Consortium (W3C). They define how web content should be made accessible to people with visual, auditory, motor, and cognitive disabilities.

In the UK, the Equality Act 2010 requires businesses to make "reasonable adjustments" to ensure their services are accessible to people with disabilities. For websites, WCAG 2.1 Level AA is widely accepted as the benchmark for reasonable compliance. While enforcement against private sector SMEs has historically been limited, the legal framework exists — and accessibility lawsuits in the US (where the ADA applies) have served as a warning for UK businesses operating digital services.

WCAG is organised around four principles: content must be Perceivable, Operable, Understandable, and Robust — often abbreviated as POUR.

The WCAG Principles Applied to Service Business Websites

Perceivable

Information must be presentable to users in ways they can perceive — meaning it can't be invisible to all of their senses.

Alt text for images — Every image on your website should have descriptive alt text explaining what it shows. For a plumbing website, an image of a boiler installation should have alt text like "New Worcester Bosch combi boiler installed in a Leeds kitchen." This benefits screen reader users and provides keyword-rich context for Google.

Sufficient colour contrast — Text must have adequate contrast against its background (minimum ratio of 4.5:1 for normal text at WCAG AA). Low-contrast light grey text on white backgrounds fails both accessibility and readability standards. Use a contrast checker tool to verify all text combinations.

Captions for video — If you use video testimonials or project walkthroughs, captions make them accessible to deaf and hard-of-hearing users and improve comprehension for users watching without sound (common on mobile).

Responsive text sizing — Text should scale correctly when a user increases their browser font size or zoom level. Fixed-pixel font sizes that break layouts when zoomed are a WCAG failure.

Operable

Users must be able to operate the interface — including those who don't use a mouse.

Keyboard navigation — All interactive elements (forms, buttons, navigation menus, dropdown menus) must be operable using a keyboard alone. Test by tabbing through your website — every interactive element should receive focus in a logical order and be activatable with Enter or Space.

Focus indicators — When a user tabs to a link or button, a visible focus indicator (usually a border or highlight) should appear. Many designs remove this for aesthetic reasons — don't. It's a WCAG failure and makes keyboard navigation unusable.

No keyboard traps — If a user tabs into a modal, popup, or widget, they must be able to tab out again. Keyboard traps strand users who rely on keyboard navigation.

Skip navigation link — Add a "Skip to main content" link at the top of each page (can be visually hidden unless focused) that lets screen reader users bypass the navigation menu and jump straight to the page content.

Understandable

Content and interface operation must be understandable.

Plain English — Use clear, jargon-free language. While this is primarily a content quality principle, WCAG also requires that the language of the page be declared in the HTML lang attribute so screen readers use the correct pronunciation.

Descriptive form labels — All form fields must have explicit, descriptive labels. Placeholder text alone (text inside the field that disappears when you type) is insufficient — users with cognitive disabilities and screen reader users both struggle with placeholder-only labels.

Error identification — When a form submission fails (e.g., missing required field), the error must be described in text and the relevant field clearly identified. A red border with no text explanation isn't sufficient.

Consistent navigation — Navigation menus should appear in the same location and use the same labels across all pages. Inconsistent navigation increases cognitive load and confuses users with memory or attention difficulties.

Robust

Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies.

Valid HTML — Properly structured, valid HTML ensures assistive technologies can parse your content correctly. Common issues include duplicate IDs, missing ARIA landmark roles, and improperly nested elements.

ARIA labels where needed — Where HTML semantics aren't sufficient, ARIA (Accessible Rich Internet Applications) labels can add context for screen readers. Icon-only buttons (e.g., a search icon with no visible text) must have an aria-label attribute explaining their function.

Practical Steps to Improve Your Service Website's Accessibility

You don't need a full rebuild to make meaningful accessibility improvements. Start with these actions:

1. Run an automated accessibility audit — Tools like WAVE (wave.webaim.org), Axe DevTools, or Google Lighthouse's Accessibility score will identify common issues quickly.

2. Fix colour contrast issues — Adjust your CSS to ensure all text meets the 4.5:1 contrast ratio minimum. This is often a quick CSS change.

3. Add alt text to all images — Go through every image on your site and add meaningful, descriptive alt text. Prioritise service pages and the homepage.

4. Label all form fields properly — Replace placeholder-text-only labels with proper <label> elements linked to their input fields via the for attribute.

5. Test keyboard navigation — Tab through your website and confirm that every interactive element is reachable and operable without a mouse.

6. Add focus styles — If your CSS removes the default browser focus outline (via outline: none), add a custom focus style that provides equivalent visibility.

Accessibility and SEO: The Overlap

Many accessibility improvements directly benefit SEO:

• Alt text improves image search rankings and helps Google understand page content

• Descriptive heading structure (H1, H2, H3 used logically) improves both screen reader usability and keyword relevance signals

• Fast page load times benefit both users with cognitive disabilities and Core Web Vitals scores

• Clear, well-structured HTML is easier for Googlebot to crawl and index

Treating accessibility as a foundation of good web development — rather than an afterthought — produces websites that are better for users, better for search engines, and more legally defensible.

Conclusion

Accessibility isn't a box-ticking exercise. For service businesses, it's about ensuring that every potential customer — regardless of disability — can find your services, trust your reputation, and contact you. The improvements are often straightforward, the SEO benefits are real, and the customer reach is significantly broader.

Audit your website's accessibility today using the WAVE tool and prioritise the quick wins: alt text, colour contrast, form labels, and keyboard navigation.

Need help making your service business website fully accessible and high-converting? Zava Build builds WCAG-compliant, conversion-focused websites for UK service businesses. Book a free strategy session →