Skip to content
Web Development11 min read

Website Accessibility: A Practical Guide to Building More Accessible Websites

Build and check an accessible website: WCAG principles, a two-tier pre-launch audit checklist, what scanners miss, web app patterns and where the law applies.

01

Quick answer

Website accessibility means building a site so people with a wide range of abilities can perceive, understand, navigate and interact with it, guided by the W3C's Web Content Accessibility Guidelines (WCAG). In practice: semantic HTML, a logical heading structure, meaningful alt text, full keyboard access, visible focus, sufficient contrast, accessible forms and errors, and careful handling of motion and media. Before launch, combine an automated scan with manual checks, because tools find only part of the problems. Whether accessibility is a legal requirement for your business depends on your market and sector; verify that separately.

02

Key takeaways

  • Target WCAG 2.2 Level AA unless you have a reason to choose otherwise.
  • Build accessibility in from the start; retrofitting after launch costs more.
  • Automated scanners help, but many barriers can only be found by a person.
  • Web apps need extra care with dynamic content, focus and status messages.
  • Legal duties differ by market; check the triage table, then get advice.
03

What web accessibility covers

Accessibility covers a wide range of needs, not just screen reader support: visual differences (low vision, colour blindness), motor differences (difficulty using a mouse, reliance on keyboard or switch devices), auditory differences (needing captions) and cognitive differences (needing clear, predictable structure).

WCAG organises this around four principles. Content must be Perceivable (available through sight, sound or touch, in more than one way where needed), Operable (usable through different input methods, including keyboard only), Understandable (predictable and clear) and Robust (compatible with current and future assistive technology). It defines three conformance levels, A, AA and AAA, with AA the common practical target for business websites.

04

The building blocks

Semantic HTML. Use elements for their intended purpose: real headings, buttons, lists and landmarks rather than styled generic elements. This gives assistive technology the structure it needs and is one of the lowest-effort improvements when built in from the start.

Headings and structure. One H1, then properly nested H2s and H3s, so screen reader users can navigate by heading the way sighted users scan. Do not skip levels or use headings purely for styling.

Labels and alternative text. Every form field needs an associated label, and every meaningful image needs alt text that describes its content or purpose. Mark decorative images so assistive technology skips them.

Keyboard navigation and focus. Every link, button, field and custom widget must work with a keyboard alone, in a logical order, with a visible focus indicator. Removing default focus outlines without a clear replacement is a common, avoidable failure.

Colour contrast. Text needs sufficient contrast against its background; WCAG sets specific contrast ratios. Do not convey meaning, such as an error, through colour alone.

Forms and errors. Error messages should be specific, tied to the relevant field and written in text, not just a red border.

Buttons and links. Use descriptive text ("Submit order", not "Click here"), because screen reader users often move through a list of links or buttons out of context.

Zoom and responsive layout. Content should stay usable when text is enlarged or the page is zoomed, which many people with low vision rely on.

Motion and media. Caption video, let users pause moving content, and respect the operating system's reduced-motion setting for decorative animation.

Navigation. Keep navigation consistent and provide a skip link so keyboard users can jump to the main content. For the design decisions behind all of this, see accessible UI/UX design.

05

Pre-launch accessibility audit checklist

Use two tiers. Tier 1 is a first review that anyone on the team can do in about a day, based on the W3C's Easy Checks plus an automated scan of each key template. The W3C is clear that a page "could seem to pass these checks, yet still have significant accessibility barriers", so Tier 1 finds obvious problems; it does not prove conformance. Tier 2 is a structured audit, usually by a specialist, of a sample of pages and complete journeys. The W3C's WCAG Evaluation Methodology (WCAG-EM) 2.0, published as a W3C Group Note on 23 July 2026, sets out five steps: define the scope, explore the product, select a representative sample, evaluate it and report the findings.

The scanner column is general guidance: "partly" means a tool can flag that something is missing or wrong in code, but a person has to judge whether it works.

CheckTierCan a scanner catch it?
Each page has a unique, descriptive title1Partly: missing titles yes, quality no
Images have appropriate alt text; decorative images are hidden1Partly: missing alt yes, whether it is meaningful no
Headings form a logical outline1Partly
Text contrast meets WCAG ratios1Mostly, except text over images and gradients
Page language is set1Yes
Text resized to 200% stays readable and usable1No
Every control works by keyboard, in a logical order, with visible focus1No
Form fields have labels; errors are clear and linked to the field1Partly: missing labels yes, error quality no
Moving, flashing or auto-playing content can be paused1No
Video has accurate captions; audio has transcripts1Partly: a missing track at best, accuracy no
Key journeys (enquiry, sign-up, checkout, booking) work with a screen reader on desktop and mobile2No
Content reflows on a narrow screen and at high zoom without horizontal scrolling2No
Focused elements are not hidden behind sticky headers or banners (WCAG 2.2: 2.4.11)2No
Small or crowded tap targets meet the minimum size or spacing (2.5.8)2Partly
Anything done by dragging has a single-pointer alternative (2.5.7)2No
Help options appear in a consistent place (3.2.6)2No
Users are not asked to re-enter information already given in the same process (3.3.7)2No
Login does not depend on a memory or puzzle test without an alternative, and allows paste and password managers (3.3.8)2No
Third-party widgets (cookie banner, chat, payment, booking, maps) pass the same checks2Partly
PDFs and downloadable documents are accessible, or have an accessible alternative2Partly
Dynamic updates and status messages are announced (see web app patterns)2No
An accessibility statement is published and up to date2No

Pro tip

Log each barrier with the page, the WCAG success criterion, who it affects, severity, the fix, an owner and a date. Fix blockers in critical journeys first, then retest.

06

What WCAG 2.2 added and why scanners are not enough

WCAG 2.2 added nine success criteria. Six apply at Level A or AA and appear in the checklist above: Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication (Minimum). The other three are AAA. The old 4.1.1 Parsing criterion is "obsolete and removed". Our list of accessibility testing tools covers what each scanner, checker and screen reader is good for.

Most of the new criteria need a person to judge them, which is the wider point. The W3C states that evaluation tools "can not determine accessibility, they can only assist in doing so". In a 2017 test by the UK Government Digital Service, a page built with 143 barriers was run through 10 automated tools: the most effective single tool found 41% (counting its prompts for manual checks), and all 10 together found about 71%, leaving 29% that no tool detected. That was one deliberately broken page, not a general detection rate, and tools have changed since, but the lesson holds.

Scanners are still worth running. WebAIM's 2026 scan of the top one million home pages found detectable WCAG failures on 95.9% of them, most often low-contrast text, missing alt text, missing form labels and empty links. WebAIM adds that the "absence of detected errors does not indicate that a page is accessible or conformant".

07

Web app patterns: dynamic content, focus and live regions

Web apps update parts of the page without reloading it, which a screen reader user may not notice unless the app tells them. Check these patterns in any logged-in product, dashboard or multi-step form.

  • Status messages. Announce results that appear without a page load, such as "Saved", "3 results found" or "Item added to basket", using a polite live region (WCAG 4.1.3 Status Messages). Keep announcements short and do not announce every keystroke.
  • Dialogs and modals. Move focus into the dialog when it opens, keep it there while it is open, close it with Escape, and return focus to the control that opened it.
  • Route changes. In a single-page app, update the page title and move focus to the new page's heading or main area, so the change is announced as a real page change would be.
  • Form errors. On submit, move focus to an error summary or the first invalid field, and link each message to its field.
  • Loading and infinite scroll. Tell users when content is loading and when it has arrived; offer a "load more" button rather than relying only on infinite scroll.
  • Data tables. Use real table markup with header cells, not a grid of styled boxes, so screen readers can announce row and column headers.
  • Custom widgets. Prefer native elements (button, select, details). If you build a custom tab set, combobox or menu, give it the correct roles, states and keyboard behaviour, and test it with a screen reader.
08

Which rules apply where: a quick triage

One line per market, as a starting point only. Legal duties depend on your sector, size and customers; take advice for your situation. Accessibility as good practice applies everywhere.

MarketWhat we verified
IndiaGIGW 3.0 applies to websites and apps owned by government organisations and draws on WCAG 2.1. Duties for private websites are not covered here; take advice.
UAEWe did not verify a general accessibility rule for private-sector websites; check sector and emirate requirements with a local adviser.
UKService providers must make reasonable adjustments under the Equality Act 2010 (Disability Discrimination Act 1995 in Northern Ireland). Public sector bodies must meet WCAG 2.2 AA and publish an accessibility statement.
AustraliaThe Disability Discrimination Act 1992 applies to goods and services, and the Australian Human Rights Commission has published guidelines on equal access to digital goods and services; see website accessibility in Australia.
EUThe European Accessibility Act covers e-commerce services to consumers, through each country's national law. The Directive exempts micro-enterprises that provide services (Luxembourg's government toolkit says such businesses are "not affected"); check the national rules where you sell.
09

Common mistakes before launch

  • Treating a clean automated scan as a pass.
  • Testing only the home page, not the journeys that matter (forms, sign-up, checkout, booking).
  • Forgetting third-party widgets, which are part of your site to your users.
  • Relying on an overlay plugin instead of fixing the markup.
  • Removing focus outlines for visual reasons.
  • Leaving accessibility to the last week, when fixes to components are most expensive.
10

Limits of this checklist

This checklist is for a pre-launch review of a business website or web app. It does not replace a full conformance audit, testing with disabled users, or legal advice. For stores, the ecommerce accessibility checklist goes page by page through product, cart and checkout; for test methods and reporting in depth, see the accessibility testing guide. If your site is mostly documents or complex data visualisations, those need specialist review beyond what is listed here.

11

Sources

W3C: Easy Checks: a first review of web accessibility; WCAG Evaluation Methodology (WCAG-EM) 2.0, W3C Group Note, 23 July 2026; What's new in WCAG 2.2; WCAG 2.2; Selecting web accessibility evaluation tools; Developing an accessibility statement.

Evidence on tools: GOV.UK accessibility blog: what we found when we tested tools (24 February 2017); WebAIM Million 2026 (data from February 2026).

Law and policy: GOV.UK: accessibility requirements for public sector websites and apps; Guidelines for Indian Government Websites and Apps: scope; Luxembourg government EAA toolkit: micro-enterprises providing services.

Accessed 14 October 2026. Laws and guidance change; nothing here is legal advice.

12

Conclusion

Most of the real-world impact of accessibility comes from the basics: semantic HTML, keyboard access, visible focus, contrast and clear forms, built in from the start. Before launch, run the Tier 1 checks on every key template, commission a Tier 2 audit of your main journeys, fix blockers first and publish an honest accessibility statement. Then check which legal duties apply in your markets. Our website development page explains how we build accessibility into delivery and pre-launch QA.

Get a pre-launch accessibility review

ZSpace Labs is a remote-first technology studio that works with clients globally on website development and UI/UX design. If useful, we can talk through your pre-launch checklist and which journeys to test first.

Start a Project
FAQ

Common questions.

Building a website so people with a wide range of abilities and disabilities, including visual, auditory, motor and cognitive differences, can perceive, understand, navigate and interact with it. This benefits far more users than people using assistive technology; clear structure and good contrast help everyone.

The Web Content Accessibility Guidelines, published by the W3C's Web Accessibility Initiative (WAI). They are the widely referenced standard for web accessibility, organised around four principles (Perceivable, Operable, Understandable and Robust) with conformance levels A, AA and AAA. The current version is WCAG 2.2.

Level AA is the commonly referenced practical target for most business websites, balancing meaningful accessibility with achievability, though the right target can depend on your context and jurisdiction.

It varies by jurisdiction and by the nature of the business. Some regions and sectors have specific legal accessibility requirements; others do not have the same explicit obligations. The triage table on this page gives a one-line starting point per market, but treat it as a question to verify for your situation.

No. Accessible design and good design overlap heavily. Clear hierarchy, sufficient contrast and predictable navigation improve the experience for every user, not just those using assistive technology.

Semantic HTML and meaningful alt text for images are both foundational, relatively low-effort improvements with an outsized impact on how well assistive technology can interpret and navigate a page.

Not reliably. Genuine accessibility has to be built into the site's markup, structure and interaction design; automated overlays are not a substitute for that underlying work.

No. It also covers keyboard-only navigation, sufficient colour contrast for low vision, captions for multimedia, and reduced-motion support for users sensitive to animation, among other needs.

Run an automated scan on your key templates, then test manually: the W3C's Easy Checks, keyboard-only navigation, zoom, and a screen reader on the main journeys. The W3C says tools "can not determine accessibility, they can only assist", so manual testing is not optional. For a formal audit, a specialist samples pages and journeys using a structured method such as WCAG-EM.

The W3C's guidance says a statement should at least include your commitment to accessibility, the standard you apply (for example WCAG 2.2 Level AA) and contact details for people who meet barriers. It is also good practice to list known limitations and when you plan to fix them. UK public sector bodies must publish one.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.