All insights
Website Strategy8 min read

Accessibility is part of a usable website, not a last polish pass

An inaccessible website quietly turns people away: customers who cannot tab through a form, read a contrast-poor button, or play a video without captions. Accessibility is how you keep the door open. It is also how search engines, mobile users and older customers experience the same pages.

01

Treat access as a business requirement

If a visitor cannot complete a booking, send an enquiry or read a price, the site has failed its job, whether or not anyone files a complaint. Accessibility is not a niche preference. It covers people using screen readers, keyboards, zoom, captions, reduced motion, and older hardware. It also covers anyone with a temporary injury, bright sunlight on a phone, or a slow connection.

Laws and procurement rules make this sharper. Public bodies and many suppliers already have to meet published standards. Private businesses face growing legal expectations: in the EU, the European Accessibility Act has applied to many consumer products and services since June 2025, and in the UK and US, accessibility claims under equality and disability laws are increasingly common. The useful stance is not panic. It is to treat WCAG-aligned work as part of quality, the same way you treat HTTPS and mobile layout.

A site that is easy to use with a keyboard and a screen reader is usually easier for everyone else too. Clear labels, visible focus, honest errors and readable type reduce support tickets as well as legal risk.

02

See who the current site quietly excludes

Walk the real journeys, not the homepage. Try to book, buy, log in, download a PDF or contact sales using only the keyboard. Then try the same with browser zoom at 200 percent. If a menu traps focus, a cookie banner has no close path, or a date picker cannot be used without a mouse, you have found a blocked customer, not a cosmetic issue.

Media and documents hide problems. Product photos without alternative text, decorative images announced as noise, PDFs that are scans, and videos with no captions all fail people who cannot see or hear the original. So do autoplaying carousels and pop-ups that steal focus.

Ask the team who answers the phone which pages generate confused calls. Those pages are often the same ones that fail accessibility checks: forms, pricing tables, location details and login.

03

What WCAG actually asks you to do

WCAG, the Web Content Accessibility Guidelines, is the shared language most audits use. Version 2.2 at levels A and AA is the usual commercial target. The four principles are simple: content should be perceivable, the interface operable, the information understandable, and the whole thing robust enough to work with assistive technology.

You do not need to memorise every success criterion. You do need a short list that matches your site: text alternatives, captions, colour contrast, keyboard access, visible focus, skip links, form labels, error identification, page titles, language of the page, and name, role and value for custom controls.

AA is a floor, not a trophy. A perfect automated score can still hide a booking widget that cannot be used. Manual checks on the journeys that make money matter more than a badge in the footer.

04

Keyboard, focus, forms and the parts that convert

If it cannot be done with a keyboard, it cannot be done by many assistive-technology users. Every interactive control needs a visible focus state that is not removed in CSS. Tab order should follow the visual order. Modals, menus and cookie banners must trap or restore focus on purpose, then let people leave.

Forms are where accessibility meets revenue. Every field needs a visible label, not only a placeholder. Errors should be text, tied to the field, and announced. Required fields need more than a colour. Autocomplete attributes help people fill names and addresses. Do not rely on hover-only instructions.

Custom dropdowns, date pickers and sliders are frequent failure points. Prefer native HTML where it works. If you build a custom control, it needs the right roles, keyboard behaviour and accessible name. An agency that skips this will produce a pretty form that does not take orders from part of the audience.

05

Content, media, language and documents

Editors own as much accessibility as developers. Headings must follow a real outline, not a visual size. Links should make sense out of context: “Download the 2026 price list” beats “click here”. Lists, tables and quotes should use the right HTML so a screen reader can announce them.

Images that convey meaning need alternative text that states the meaning, not the file name. Decorative images should be empty alternatives so they are skipped. Complex charts need a short summary nearby. Videos need captions; important audio needs a transcript. Do not autoplay sound.

PDFs, slide decks and embedded maps often sit outside the HTML you tested. If a contract, menu or brochure is the real product, it needs to be accessible too, or offered as a usable HTML alternative. Language of the page, and of passages in another language, should be marked so pronunciation is not guessed.

06

Colour, type, motion and visual design

Contrast is the accessibility issue most people can see. Text and interface components need enough contrast against their background, including placeholders and disabled-looking buttons that are still clickable. Do not use colour alone to show error, success or required state.

Type should be resizable. Line length and spacing should stay readable when someone zooms. Avoid text in images for key messages. Touch targets need space. Hover content that disappears when the pointer moves is hostile on a phone and for motor impairments.

Motion can make people ill. Respect prefers-reduced-motion. Do not require a timed puzzle to submit a form. Parallax and looping background video are optional decoration; they are not worth excluding a customer over.

07

Audit, fix and prove progress without a rewrite

Start with an inventory of templates and the five journeys that matter. Run an automated check for the easy misses, then a keyboard pass and a screen-reader pass on those journeys. Record issues with the page, the criterion, the severity and a suggested fix. That list is the backlog, not a PDF that sits in a drawer.

Fix in layers. First remove blockers: keyboard traps, missing labels, unusable cookie banners, contrast failures on primary buttons. Then repair headings, alternative text, skip links and focus styles in the design system so every new page inherits the improvement. Third-party widgets need owners: replace them if the vendor will not meet the bar.

Publish an accessibility statement that is honest: the standard you aim for, known gaps, how to contact you, and when you last tested. Over-claiming “fully compliant” is worse than describing work in progress. Retest after each release that touches navigation, forms or checkout.

08

Make accessibility a habit, not a launch task

The cheapest accessibility work happens at the briefing stage. Ask for WCAG 2.2 AA on the templates that convert, native controls where possible, and a test plan that includes keyboard and a screen reader. Put the same bar in content guidelines so editors do not undo the engineering.

Roles matter. Design owns contrast, focus and target size. Development owns semantics, names and keyboard behaviour. Content owns headings, links and alternatives. QA owns the journeys. Someone named must accept or reject third-party scripts that break the experience.

If you are buying a redesign, make accessibility a deliverable with evidence: sample screen-reader notes, a contrast report on the palette, and a form that can be completed without a mouse. That is how the next site stays open to the people you already want as customers.

Start a project

Need a clearer direction for your website?

Start a project