Why accessibility compliance needs ongoing attention

A website can look polished, load quickly and still prevent people from completing essential tasks. A customer may be unable to submit an enquiry form using a keyboard. A visitor with low vision may not be able to read text over a background image. A screen-reader user may hear a row of unlabelled buttons with no indication of what they do. This guide to website accessibility compliance explains how to identify those barriers and build accessibility into the way your website is managed.

For businesses, charities and public-facing organisations, accessibility is not a cosmetic extra or a one-off technical exercise. It affects who can get information, buy products, request support, make an appointment or contact your team. Done properly, it also improves usability, search visibility, content quality and the long-term reliability of your digital platform.

Why accessibility compliance needs ongoing attention

Website accessibility means designing and maintaining a site so people with a broad range of disabilities can use it. That includes people who are blind or have low vision, are deaf or hard of hearing, have motor impairments, experience cognitive differences, or rely on assistive technology such as screen readers, speech recognition and keyboard navigation.

In the UK, the Equality Act 2010 is relevant to businesses and service providers because it requires reasonable adjustments to avoid substantial disadvantage for disabled people. Public-sector bodies have additional duties under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, including publishing an accessibility statement and meeting applicable accessibility requirements.

Legal obligations are context-specific, so this article is not legal advice. The practical business point is clearer: if your website is a route to your services, inaccessible journeys can create operational, reputational and commercial risk. Waiting for a complaint is a poor way to discover that a core online process excludes part of your audience.

Accessibility standards also change, and websites change even faster. A compliant launch can drift out of shape after a new page builder, marketing landing page, third-party booking tool or PDF upload is added without review. Compliance is best treated as part of routine website governance, alongside security updates, backups, performance monitoring and content maintenance.

Guide to website accessibility compliance: start with WCAG

The Web Content Accessibility Guidelines, usually referred to as WCAG, are the main technical framework used to assess website accessibility. WCAG is organised around four principles: content must be perceivable, operable, understandable and robust. In practical terms, users need to be able to access content, operate controls, understand what is happening and use the site with current assistive technologies.

WCAG 2.2 Level AA is widely used as the working target for organisations. Level A covers fundamental barriers, while Level AA addresses many of the issues that materially affect everyday website use. Level AAA can be valuable for certain content or audiences, but it is not realistic or appropriate as a blanket requirement for every page and feature.

The target should match the nature of your organisation and audience. A council, school, healthcare provider or organisation delivering critical public information may need a more formal programme than a small professional-services firm. However, both should ensure that core journeys work for keyboard users and assistive technology, and that basic content is readable and understandable.

Audit the journeys that matter to your organisation

A useful accessibility audit does more than return a long list of errors. It tests the routes that create value for your users and business. Start with high-traffic and high-consequence pages: the home page, service pages, contact forms, checkout, account areas, booking flows, document libraries and key campaign landing pages.

Automated scanning tools are a sensible first pass. They can identify common faults such as missing alternative text, empty form labels, low colour contrast and incorrect heading structures. They are efficient, but they cannot judge whether alternative text is meaningful, whether a process makes sense or whether a form error message gives useful instruction.

Manual testing fills that gap. Navigate important journeys using only the keyboard. The Tab key should move through interactive elements in a predictable order, and the current focus should be clearly visible. Every menu, modal, form field, button and checkout control should be usable without a mouse.

Screen-reader testing is equally valuable, particularly on forms, navigation and custom components. Headings should describe page structure, labels should explain fields and controls, and status updates should be announced where necessary. A screen reader should not turn a simple enquiry into a guessing exercise.

It helps to record issues by severity and business impact. A missing decorative-image description may be lower priority than an inaccessible payment field or an enquiry form that cannot be submitted. This does not mean minor issues should be ignored. It means your remediation plan should reduce the most serious barriers first while setting clear deadlines for the rest.

Fix the foundations before the finishing touches

Many accessibility problems originate in the website’s underlying structure. Fixing the foundation is usually more effective than repeatedly patching individual pages.

Use meaningful HTML and page structure

Headings must reflect the logical hierarchy of the page, rather than being selected only for their visual size. A page should normally have one clear main heading, followed by properly nested section headings. This helps screen-reader users scan content and supports better content management across the site.

Buttons should be buttons and links should be links. A clickable graphic styled to look like a button can create confusion if it is not coded to behave like one. Likewise, custom menus, tabs and accordions need appropriate keyboard behaviour and status information. These are common trouble spots on legacy websites and heavily customised templates.

Make forms clear, forgiving and usable

Forms are often the point where accessibility becomes a direct lead-generation issue. Every input needs a visible label. Placeholder text is not a substitute because it often disappears once someone starts typing and may not be read consistently by assistive tools.

When a user makes an error, identify the field and explain how to correct it. “Invalid entry” is not enough. A useful message might state that a telephone number is missing, an email address needs an @ symbol, or a required consent box has not been selected. Where a form includes a time limit, consider whether it can be extended or avoided.

Ensure content is readable in real conditions

Colour contrast needs to be sufficient between text and its background. Light grey body text, text over busy photography and colour-only error messages are frequent failures. Users should not need perfect vision, ideal lighting or a premium monitor to understand your content.

Do not rely on colour alone to communicate meaning. If form fields are highlighted in red, add clear text and an icon or other non-colour cue. Links should be recognisable beyond a subtle colour change, especially within body copy.

Text should remain usable when people zoom in or increase browser text size. Avoid fixed-height containers that crop copy, and test layouts on smaller screens. Responsive design is not automatically accessible, but a site that reflows cleanly gives users more control over how they consume information.

Review media, documents and third-party tools

Images need alternative text when they communicate useful information. The description should reflect the purpose of the image in that context, not simply list visible objects. Decorative images can be left out of the reading order so they do not create noise for screen-reader users.

Videos should have accurate captions. Audio-only content needs a transcript, and visual information in a video may require an audio description or a text equivalent where it is necessary to understand the message. Automatically generated captions can be a starting point, but they need review for names, technical language and accuracy.

Documents deserve the same scrutiny as web pages. An inaccessible PDF may be a serious obstacle if it contains application instructions, policy information, pricing, forms or public notices. Where possible, publish essential information as an accessible HTML page. If a PDF is necessary, ensure it has a logical reading order, tagged headings, meaningful links and accessible tables.

Third-party platforms can introduce risk even when the main website is well built. Booking systems, payment gateways, chat widgets, cookie banners, embedded maps and recruitment portals should be reviewed before they go live. You may not control their code, but you do control whether they are part of your customer journey. If a vendor cannot provide adequate accessibility information or a workable alternative, that should influence the procurement decision.

Build accessibility into your maintenance process

The strongest accessibility programmes are practical. They give staff a clear way to publish content without accidentally introducing avoidable barriers. That may mean a short editorial checklist, approved page components, accessible form templates and a review process for new integrations.

Train the people who edit the website, not just the developers who build it. Content teams should know how to use heading levels, write useful link text, add image descriptions and avoid uploading untagged documents. Marketing teams should understand that an urgent campaign page still needs keyboard testing and readable error messages.

Schedule periodic audits, particularly after a redesign, platform migration, major content refresh or integration change. Keep a record of known issues, remediation work and exceptions. For public-sector organisations, this supports accessibility-statement maintenance. For commercial organisations, it provides accountability and prevents the same faults from returning with every new campaign.

Accessibility work is most effective when it is handled before a feature reaches production. Adding requirements to briefs, design reviews, development acceptance criteria and quality assurance takes less time than repairing customer-facing problems after launch.

A dependable website should work for the widest practical range of people, devices and ways of browsing. Start with the pages that drive enquiries, sales and essential services, correct the barriers that stop people completing those tasks, then make accessibility part of every future website decision.