Try to complete an important task on your firm's website using a keyboard alone. Enlarge the page to 200%. Listen to a service page with a screen reader. Submit the enquiry form without relying on colour to identify an error.

Do this with permission and basic guidance; switching on a screen reader and closing your eyes does not reproduce the lived experience of a skilled blind user. It can reveal obvious barriers and, more importantly, show leaders that the default way they use the site is only one way.

This article retains the perspective of Nichola Hudson, Distinction's UX lead: accessibility is a design-quality and trust question. Legal compliance matters, and it is a floor rather than the whole case.

What the experience communicates

A professional firm asks clients to trust it with sensitive information and consequential work. Its digital service communicates how carefully it has considered the person at the other end.

Clear headings, meaningful labels, usable focus states and understandable error messages help disabled people complete tasks. They also demonstrate disciplined design. A client encountering an unlabelled form or a keyboard trap cannot infer the quality of the firm's advice from that defect. They can reasonably infer that this part of the service was not tested for people who interact differently.

Accessibility should not be sold through fear or a claim that every defect causes lost revenue. The stronger argument is direct: excluding people from information and services is harmful, and a firm that promises client focus should design for the range of clients it serves.

Compliance needs current, specific advice

In Great Britain, the Equality Act 2010 contains duties concerning reasonable adjustments in services and public functions. The application to a particular organisation and digital service depends on facts and legal interpretation. The legislation and the official services code of practice are useful starting points; obtain legal advice for the firm's actual obligations.

The European Accessibility Act entered into application in June 2025 for covered products and services in the EU, with scope, exemptions and national enforcement that need specific assessment. A professional-services website is not automatically in or out merely because the firm has European clients. The European Commission's accessibility overview should be read alongside relevant national implementation and legal advice.

Other jurisdictions impose different duties. Avoid transplanting US lawsuit counts or requirements into a UK investment paper without relevance and a current authoritative source.

WCAG is a technical accessibility standard, rather than a complete statement of legal compliance. W3C recommends WCAG 2.2 for current accessibility efforts. Conformance still does not address every user need, and automated scans cannot establish it on their own.

Accessible design can remain distinctive

WCAG does not prescribe a brand palette or layout. It sets testable success criteria concerning whether content is perceivable, operable, understandable and robust.

A designer can use expressive type, colour, motion and composition within those constraints. The work becomes more demanding because aesthetic decisions need to survive contrast, zoom, reflow, focus, reduced motion and assistive technology.

The best analogy is not that constraints disappear inside good design. It is that good design treats them as part of the problem from the beginning. A pale brand colour may remain useful for large surfaces and decoration while another colour carries small text. A complex visual can include a meaningful alternative. Motion can be purposeful and respect user preferences.

Named examples such as Apple, GOV.UK or Stripe change and should not be presented as blanket claims of conformance without a defined audit. Study individual patterns and their tested behaviour instead.

Six places to begin

Colour and non-colour cues

Check text and interactive controls against the relevant WCAG 2.2 criteria. The commonly cited Level AA ratios are 4.5:1 for normal text and 3:1 for large text, subject to the standard's definitions and exceptions.

Contrast tools help assess colour values. They cannot determine whether information is conveyed by colour alone, whether text sits over a changing image or whether the selected state is understandable. Inspect the rendered component in every important state.

Heading and page structure

Use headings to communicate a meaningful hierarchy, rather than to achieve a visual size. The blanket rule “one H1 per page” is a useful convention for many sites and not itself a WCAG requirement.

Test whether users can navigate landmarks and headings to understand the page. Fix the design system so editors can choose semantic structure without losing the intended appearance.

Images and alternatives

Meaningful images need an alternative that serves the same purpose in context. Decorative images should be ignored by assistive technology. A filename or generic “photo” label adds noise.

The right alternative may be short text, a nearby explanation, a data table or a long description. Do not force every complex diagram into one alt attribute.

Keyboard operation and focus

Every interactive function should be operable without a mouse where the standard requires it. Users need visible focus and a logical order. Menus, dialogs, cookie controls, carousels and custom selects deserve particular attention.

Test opening, operating, closing and recovering. A user who can enter a modal and cannot escape has encountered a severe barrier even if the automated score is high.

Forms, errors and authentication

Give controls persistent labels and programmatic names. Explain required formats, identify errors, preserve entered information and associate messages with the relevant field. Placeholder text alone is inadequate as a label.

WCAG 2.2 also added criteria concerning accessible authentication. Review password, puzzle and one-time-code journeys, including recovery. Security and accessibility should be designed together; weakening authentication is not the objective.

Link and control purpose

"Read more" can be understandable with sufficient programmatic context. Repeated ambiguous links still create work. Prefer text that helps users predict the destination when the design allows it.

A control that expands content should be identified and expose its state. Visual text, accessible name and behaviour should agree.

Benefits beyond the original user need

Accessibility improvements can help people in bright light, with a temporary injury, under time pressure or using an unfamiliar device. Clear content can help readers with differing language or cognitive needs.

Keep disabled people at the centre of the case. If every benefit is reframed for non-disabled users or search performance, inclusion becomes secondary again. Search effects also vary and should not be promised as a return from fixing headings or alternative text.

Good accessibility frequently supports usability. The terms are related and not interchangeable. A task can technically conform to a standard and remain confusing; user research and service design must continue beyond the checklist.

An audit needs more than an automated score

Automated tools are valuable for repeatable checks and can find a subset of issues. Combine them with expert manual assessment, keyboard testing, assistive-technology testing and research with disabled people.

Define the sample. Include high-value journeys, templates, components, states, breakpoints, documents, video and third-party services. A homepage-only scan says little about onboarding or portal use.

The report should include:

  • the affected user and task;
  • relevant standard criterion where applicable;
  • evidence and reproduction steps;
  • severity and reach;
  • recommended remediation;
  • component or content owner;
  • retest result;
  • known limits and third-party dependencies.

Do not promise a universal two-day audit. Time depends on the estate and assurance required. A focused assessment can establish priorities quickly; a conformance claim needs a defined scope and more rigorous evidence.

Embed accessibility into delivery

An audit repairs the current service. Governance prevents the same defects from returning.

Include accessibility in research, design critique, component acceptance, content guidance, procurement, quality assurance and release checks. Give people appropriate training and named support. Add accessible patterns to the design system with code examples and test expectations.

Third-party tools remain part of the user journey. Ask suppliers for current accessibility evidence, test critical tasks and include remediation and exit terms in procurement. A conformance report is input to due diligence, not a guarantee.

Monitor after launch. Content changes, platform upgrades and new integrations can introduce barriers. Give users an accessible route to report problems and respond with a useful timescale.

Start with the journey that matters

Choose one important journey and test it with the relevant standard, assistive technologies and people. Fix the most severe barriers, retest them and move the learning into the design system and content process.

This is more credible than chasing a perfect automated score or treating accessibility as an end-of-project certificate. It improves the service now and changes how the next feature is built.

Because accessibility isn't the thing that makes your website less interesting. It's the thing that makes it actually work - for everyone. And for a firm that sells expertise and attention to detail, that's not a nice-to-have.

That's the whole point.