Every year, thousands of potential customers leave websites frustrated. They can’t read the text clearly. The navigation confuses them. Images have no descriptions. Videos lack captions. Some of these visitors are using assistive technology—screen readers, voice commands, keyboard-only navigation. Others simply have aging eyes or are in bright sunlight.

The reality? Over 93% of websites fail basic accessibility standards. In the UK alone, approximately 14.6 million people have a disability. That’s 1 in 4 adults. For London businesses, this represents a massive market opportunity—and a significant legal liability.

Website accessibility isn’t a nice-to-have feature. It’s a legal requirement. The UK Equality Act 2010 mandates that digital services must be accessible to people with disabilities. Businesses that ignore these requirements risk costly lawsuits, regulatory fines, and reputational damage. Meanwhile, accessible websites convert better, rank higher in search results, and expand your customer base.

We’ve helped 200+ London businesses achieve WCAG compliance and build websites that work for everyone. This guide explains what you need to know about accessibility standards, why they matter for your business, and exactly how to implement them. Whether you’re just starting your accessibility journey or refining existing systems, you’ll find actionable steps to protect your business and serve your customers better.

Understanding Website Accessibility and WCAG Standards

Website accessibility means designing and building websites that work for everyone—regardless of ability, disability, technology, or circumstance. It’s about removing barriers that prevent people from accessing your content, making purchases, booking services, or finding information.

The Web Content Accessibility Guidelines (WCAG) are the internationally recognized standard for digital accessibility. Developed by the World Wide Web Consortium (W3C), WCAG provides technical requirements that ensure websites are perceivable, operable, understandable, and robust. These aren’t vague suggestions. They’re specific, measurable criteria.

WCAG has three compliance levels:

1. Level A (Basic) – Addresses the most critical accessibility issues. Meets minimum legal requirements in most jurisdictions.
2. Level AA (Enhanced) – The recommended standard for most organizations. Provides substantial accessibility improvements and is mandated by UK law for public sector websites.
3. Level AAA (Advanced) – The highest standard. Often exceeds typical business requirements but may be necessary for specific sectors.

In the UK, the Public Sector Bodies Accessibility Regulations 2018 requires Level AA compliance for all government and public sector websites. While this doesn’t legally mandate private businesses to meet Level AA, the Equality Act 2010 requires equal access to services. Courts increasingly view WCAG Level AA as the baseline for legal compliance. Failing to meet this standard exposes your business to discrimination claims.

For a London business, this means WCAG Level AA compliance should be your minimum target. It’s achievable, cost-effective, and protects you legally while improving user experience for all visitors.

Common accessibility barriers your website might have:

– Text too small or low contrast (hard to read for people with low vision)
– Images without alt text (inaccessible to screen reader users)
– Videos without captions (inaccessible to deaf users)
– Forms that can’t be navigated with keyboard alone
– Colors used alone to communicate information (problematic for colorblind users)
– Moving content that can’t be paused (triggers issues for people with vestibular disorders)
– Complex navigation that confuses assistive technology users
– PDF documents that aren’t tagged or structured properly

These aren’t edge cases. They directly impact user experience for millions of potential customers. And they’re all fixable.

Legal Requirements and Compliance Framework for London Businesses

Understanding the legal landscape is essential. Accessibility isn’t just ethical—it’s legally required in the UK, and enforcement is increasing.

The Equality Act 2010 is your primary obligation. This law makes it illegal to discriminate against people with disabilities. It applies to all service providers, including businesses. Your website is considered a “service” under this act. If your website discriminates against disabled users, you’re breaking the law.

The act requires “reasonable adjustments” to ensure disabled people can access your services. For websites, this means meeting recognized accessibility standards. Courts have consistently interpreted WCAG Level AA as the reasonable standard. Several high-profile lawsuits against major brands have resulted in settlements of £100,000+ for accessibility failures.

The Public Sector Bodies Accessibility Regulations 2018 specifically requires public sector organizations to meet WCAG 2.1 Level AA. While this doesn’t directly apply to private businesses, it establishes Level AA as the accepted standard across the UK. Many local authorities and government agencies are now checking if their suppliers’ websites are accessible—meaning private businesses working with public sector clients face indirect pressure to comply.

What this means for your London business:

If you operate in the UK and provide goods or services online, you have a legal obligation to ensure reasonable access for disabled people. Non-compliance exposes you to:

– Discrimination complaints through the Equality and Human Rights Commission
– Individual lawsuits (claimants can pursue damages through civil court)
– Regulatory action (local authorities can investigate and enforce compliance)
– Reputational damage (accessibility failures are increasingly publicized)
– Loss of customers (inaccessible sites exclude potential buyers)

The good news? Achieving compliance is a straightforward process with the right guidance and tools.

Your compliance checklist:

– Audit your website against WCAG 2.1 Level AA criteria
– Fix critical issues (contrast, alt text, keyboard navigation, form labels)
– Test with real assistive technology users (not just tools)
– Document your accessibility effort (demonstrates good faith if challenged)
– Maintain compliance as you update your site
– Display an accessibility statement on your website
– Provide contact information for accessibility concerns

We’ve helped countless London businesses move from “maybe we should do this” to fully compliant within 3-6 months.

Step-by-Step: Conducting an Accessibility Audit

Before you fix accessibility issues, you need to understand what’s broken. An accessibility audit is a comprehensive review of your website against WCAG standards. It identifies barriers and creates a roadmap for improvement.

Step 1: Choose your audit approach

You have three options. Automated tools (fast, inexpensive, but limited). Manual testing (thorough, requires expertise). Hybrid approach (combines both, most practical for most businesses).

Automated tools like WAVE, Axe, or Lighthouse can scan hundreds of pages in minutes. They catch obvious issues like missing alt text, low contrast, and broken form labels. But they miss nuanced problems that require human judgment. A tool might say your navigation structure is correct, but a real screen reader user might find it confusing.

Manual testing by an accessibility specialist involves actually using your website with assistive technology. They’ll test with a screen reader, keyboard only, text enlargement, and speech recognition. They’ll check if your content makes sense when you strip away visual design. This catches real-world problems automated tools miss.

The hybrid approach is recommended: Run automated tools to catch obvious issues, then have a specialist manually test critical journeys (finding products, making a purchase, submitting forms, accessing key content). This gives you comprehensive insights without excessive expense.

Step 2: Test with automated tools

Start with free tools:

– WAVE (WebAIM): Browser extension that highlights accessibility errors directly on your page. Great for quick reviews.
– Axe DevTools: Chrome extension that identifies violations and provides remediation guidance.
– Lighthouse: Built into Chrome DevTools. Provides an accessibility score and specific recommendations.
– WCAG Color Contrast Checker: Tests if your text colors meet standards (minimum 4.5:1 ratio for normal text).

Run these tools on every major page type (homepage, product pages, contact forms, blog posts). Document what you find. Don’t worry if the numbers look bad initially—most sites have 100+ issues to fix. The automated scan is just your starting point.

Step 3: Conduct manual testing with assistive technology

This is where you find real-world problems. Assistive technology includes screen readers (JAWS, NVDA), speech recognition software, and keyboard-only navigation.

If you’ve never used a screen reader, try this: Close your eyes and visit your website using NVDA (free, Windows) or VoiceOver (built into Mac). Can you understand the page without seeing it? Does it make sense in the order things are read? Are images described? Are form fields labeled clearly?

With keyboard-only navigation, unplug your mouse and try to complete a full task on your website (find a product, fill out a form, navigate to a page). Can you do it? Can you see which element has focus? Are there any keyboard traps (places where you get stuck)?

Common issues you’ll find:

– Form fields aren’t labeled or labels aren’t associated correctly
– Buttons and links have generic text (“click here” instead of descriptive labels)
– Headings are skipped or misused (H1 to H4, then H6 – breaks structure)
– Images lack alt text or have unhelpful alt text (“image123.jpg”)
– Color alone conveys meaning (red for error, green for success with no text)
– Interactive elements aren’t keyboard accessible or don’t show focus
– Content organization is confusing when visual design is removed
– Skip links to main content are missing
– Time limits on forms or transactions exist without warning

Step 4: Create your remediation roadmap

Categorize issues by severity and effort:

Critical (fix immediately):
– Missing alt text on important images
– Broken form labels
– No keyboard navigation
– Text contrast below 4.5:1 for body text
– Missing page headings

High (fix within 1-2 months):
– Generic link text
– Misstructured headings
– Missing form instructions
– Color-only meaning
– Missing page title or confusing title

Medium (fix within 2-3 months):
– Missing heading hierarchy
– Redundant links
– Unclear language
– Missing language declaration
– Complex tables without proper markup

Low (fix within 3-6 months):
– Placeholder text in forms
– Overly long paragraphs
– Missing section headings
– Inconsistent navigation structure

This approach prevents overwhelm. You’re not fixing everything at once. You’re tackling critical issues first, then systematically improving over time. Most businesses achieve Level AA compliance within 3-6 months using this method.

Implementing Core Accessibility Features

Once you’ve identified problems, implementation begins. The good news? Most accessibility fixes are straightforward. They don’t require redesigning your website or massive development work.

Alt Text for Images

This is non-negotiable. Every image needs a descriptive alt text that conveys its meaning and purpose.

Don’t write: “image,” “picture,” “photo,” or “photo of building”

Do write: “Modern office workspace in central London with diverse team collaborating at large wooden table”

For decorative images (spacers, borders, design flourishes), use null alt text (alt=””) so screen readers skip them. For images containing text, transcribe the text in the alt attribute. For graphs or charts, describe the data: “Bar chart showing website traffic increase from 10,000 to 50,000 monthly visitors over 12 months.”

Alt text should be concise (under 125 characters typically) but informative. Imagine describing the image to someone over the phone—that’s your benchmark.

Text Contrast

Readable text requires minimum contrast ratios:

– Normal text: 4.5:1 (Level AA)
– Large text (18pt+): 3:1 (Level AA)
– Graphics and UI components: 3:1

Use a contrast checker tool to test your colors. Many design tools have built-in contrast checkers, or use WebAIM’s online tool. If your current color scheme doesn’t meet standards, you have options: darken backgrounds, lighten text, or find a different color combination that works with your branding.

This isn’t cosmetic. Low contrast literally makes content inaccessible to people with low vision. It also helps in bright sunlight and on small screens. Everyone benefits.

Keyboard Navigation

Not everyone uses a mouse. Some people have motor disabilities that make precise pointing difficult. Others use voice control software. All depend on keyboard navigation.

Test your website: Tab through every interactive element (links, buttons, form fields). Can you reach everything? Is focus visible (can you see which element is selected)? Is the tab order logical?

Common issues:
– Links or buttons that aren’t keyboard accessible
– No visible focus indicator
– Tab order jumps around illogically
– Keyboard traps (you get stuck in a modal or menu)

Fixes typically involve HTML changes (making elements focusable) and CSS (styling focus states so they’re clearly visible). Most modern web frameworks handle this automatically if built correctly.

Form Accessibility

Forms are critical customer touchpoints. If they’re not accessible, you lose customers.

Every form field needs:
– A properly associated `` element
– Clear instructions (placeholder text alone isn’t enough)
– Error messages linked to the field
– Autocomplete hints for common fields (email, password, name)
– Visible focus state

Don’t rely on color alone to show required fields—use an asterisk and label text. Don’t hide error messages in red without text—always provide clear text explaining what’s wrong.

Page Structure and Headings

Screen reader users navigate pages using heading structure. Headings create an outline that helps people understand your content hierarchy.

Structure should be logical:
– H1 (page title) – usually one per page
– H2 (main sections)
– H3 (subsections)
– H4 (smaller subsections)

Don’t skip levels (H1 to H4, skipping H2-H3). Don’t use headings for styling. Use them for structure.

This also improves SEO. Search engines use heading structure to understand your content. Proper heading hierarchy helps both accessibility and ranking.

Videos and Audio

If you have videos, provide captions for all dialogue and important sounds. Provide transcripts for audio-only content. Videos should also have audio descriptions of important visual content (you can do this as a separate audio track).

Many video hosting platforms include auto-captioning, but review the results. Automatic captions often have errors, especially with technical terms or accents.

Tools, Resources, and Cost Breakdown

Building and maintaining an accessible website requires the right tools and expertise. Here’s what you need and what it costs.

Automated Testing Tools

| Tool | Cost | Best For |

Most London businesses start with free tools. As your practice matures, paid tools provide better reporting and integration with development workflows.

Manual Testing

Hiring an accessibility specialist for a professional audit runs £1,500-3,000 for a comprehensive website review. Ongoing testing (monthly or quarterly) costs £500-1,500 per session.

This investment is essential. No automated tool catches everything. A specialist will test with real assistive technology and identify issues tools miss.

Remediation Costs

This varies massively based on your website’s current state.

Small business website (5-20 pages, few accessibility issues): £2,000-5,000 to achieve Level AA compliance. Timeline: 4-8 weeks.

**Medium business website (20-50 pages,