In its 2025 automated analysis of one million home pages, WebAIM found detectable WCAG failures on 94.8%. It detected an average of 51 errors per page.

That result does not mean 94.8% of the sites failed a complete accessibility audit. Automated tools can find only some barriers, and WebAIM says that an absence of detected errors does not establish conformance. The scale still shows how often basic problems such as low contrast, missing alternative text and missing form labels reach live websites.

For a professional services firm, those barriers affect more than compliance. They can prevent a prospective client, job candidate or existing customer from obtaining information or completing a task. They also contradict the attention to detail the firm sells.

Accessibility is part of the service

Legal, financial and consulting firms ask clients to trust them with complex, consequential work. A website contributes to that judgement before anyone speaks to a partner.

Consider a visitor with low vision trying to read credentials, find relevant experience or contact the firm. Low-contrast text slows them down. A keyboard user may be unable to reach the navigation. A screen-reader user may encounter an unlabelled form. The firm may never receive a complaint because the person simply leaves.

I reviewed a law firm's website that looked polished but had poor contrast, missing alternative text and a heading structure that jumped from H1 to H4. When I raised it, the managing partner replied, in words I am paraphrasing only slightly: “Our clients don't use screen readers.”

That assumption is impossible to support. It also treats accessibility as a special accommodation for a visible group instead of a quality of the service. Clients and colleagues do not necessarily disclose disability, and people use assistive features for many reasons.

The latest official Family Resources Survey estimates that 16.7 million people in the UK were disabled in 2024 to 2025, around one in four people. That scale makes accessibility a mainstream service-design issue, rather than a provision for a small, easily identified audience.

The legal position depends on the service and market

Accessibility law is more specific than a general claim that every private website must meet one technical standard.

In Great Britain, service providers have duties towards disabled people under the Equality Act 2010, including a duty to make reasonable adjustments. Government guidance on the Act says it applies to service providers and those providing goods and facilities in Great Britain. Northern Ireland has separate disability-discrimination legislation. What is reasonable depends on the circumstances, and a firm should take legal advice on its own service and digital estate.

Public sector websites and mobile applications are also covered by the Public Sector Bodies Accessibility Regulations. Those rules and their monitoring regime should not be presented as though they apply unchanged to every private professional services firm.

In the EU, the European Accessibility Act has applied since 28 June 2025 to specified products and consumer services, including areas such as banking services and e-commerce. The European Commission's summary gives the broad categories, while national implementing law determines enforcement and detail. Having an EU client or office does not by itself settle whether a particular website or service is in scope. Firms operating across markets should obtain advice on the exact service, customer and jurisdiction.

Regulatory scope is one reason to act. Equal access, service quality and commercial performance remain relevant even where a particular technical standard is not directly mandated.

Use WCAG as a practical standard

The current W3C Recommendation is Web Content Accessibility Guidelines 2.2. WCAG is organised around content being perceivable, operable, understandable and robust, with testable criteria at A, AA and AAA levels.

WCAG conformance requires more than a plug-in or an automated scan. Some issues need human judgement and testing with assistive technologies. The appropriate target should be agreed for the site and its legal context, with WCAG 2.2 AA providing a widely used reference point.

Treat the standard as a way to improve the service rather than a badge. A site can pass many technical checks and still contain confusing content or an unusable journey. Conversely, a team can make valuable progress before every historic page has been remediated if it prioritises barriers by user impact and risk.

Accessible design usually helps more people

Accessibility improvements often make an experience easier beyond the group that first exposed the issue.

Clear contrast helps someone with low vision and someone reading a phone in bright light. Captions support deaf users, people in a noisy environment and people who cannot play audio. A visible keyboard focus helps keyboard users and makes the state of the interface clearer. Descriptive link text helps a screen-reader user and anyone scanning a long page.

The commercial mechanism is straightforward: more people can perceive the information, understand what to do and complete the task. Do not turn that mechanism into a guaranteed conversion or search-ranking claim. The effect will depend on the existing barrier, traffic, proposition and measurement.

In one professional services rebuild we worked on, accessibility remediation was included within a broader programme. After launch, the firm's recorded bounce rate fell by 40% and quote requests nearly doubled. Those figures cannot isolate accessibility from the other changes in the rebuild. They show why the team should measure the complete experience rather than treating remediation as a technical exercise with no commercial context.

Five areas to examine first

You do not need to wait for a full redesign before fixing meaningful barriers. Start with frequent, consequential tasks and test them across content, design and code.

1. Colour and contrast

WCAG 2.2 Level AA sets a minimum contrast ratio of 4.5:1 for normal text, with exceptions including large text, incidental text and logotypes. The W3C contrast criterion contains the exact definitions.

Check body copy, links, form text, error states, disabled controls and text placed over images. A brand palette can remain distinctive while using combinations that people can read.

2. Images and other non-text content

Meaningful images need a text alternative that serves the equivalent purpose. Decorative images should usually be hidden from assistive technology. The right alternative depends on context; repeating the filename or stuffing it with keywords does not help the user.

Charts, diagrams, video and audio need their own treatment. A complex chart may need a summary or data table. Video may need captions, a transcript or audio description depending on the content and user need.

3. Headings, links and page structure

Headings should describe the page hierarchy and help people navigate. Do not choose a heading level solely for its visual size. Use link text that makes sense in context, especially where several links would otherwise all be announced as “read more”.

Landmarks, page titles and a sensible reading order also matter. Visual layout can hide a confusing document structure that becomes obvious through a screen reader.

4. Keyboard access and focus

Try the priority journeys using only a keyboard. Can you reach and operate every link, button, menu, dialog and form control? Is the focus visible? Does it follow a sensible order? Can you escape a pop-up or menu without becoming trapped?

This test is quick, although diagnosis and remediation may require experienced development work. Repeat it after changes; components can reintroduce the same problem across many pages.

5. Forms and error recovery

Every field needs an accessible name or label. Instructions should be available before they are needed. When a submission fails, identify the affected field and explain how to correct it. Do not rely on colour alone.

Test the whole route, including validation, confirmation and any document upload. Forms are where a motivated visitor becomes an enquiry, application or service user, so a small barrier can have an immediate consequence.

Audit with people as well as tools

An automated scan is useful for coverage and repeatability. It can identify missing labels, some contrast failures and structural problems across a large site. It cannot determine whether alternative text is useful, whether instructions make sense or whether a journey works well with assistive technology.

A proportionate audit can combine:

  • Automated testing across representative templates.
  • Manual keyboard and screen-reader checks.
  • Review of content and document formats.
  • Testing of high-value journeys such as contact, application, login and payment.
  • Input from disabled users where the service and risk justify it.
  • A remediation backlog with owners, priority and retest dates.

Make accessibility part of design review, content production and component acceptance so the same problems do not return after a one-off audit.

Decide what the website should communicate

Accessibility is a practical expression of who the service is designed to include. For a firm that sells care, accuracy or sound judgement, avoidable barriers weaken the claim.

If you want to know where your site stands, use the existing quick self-assessment covering contrast, image alternatives, headings, keyboard access and forms. It takes about ten minutes, gives you an initial pass or fail in each area, and can be shared with your web agency as a starting brief. Follow it with expert testing where the result, service or legal exposure requires more confidence.

The relevant question is whether the people you want to serve can use the experience. Test that directly, fix the barriers with the greatest consequence and make accessibility part of the way the site is run.