If you are wondering how to check website accessibility, start with a small, recorded review rather than an unsupported claim that the whole site is accessible. W3C’s introductory video shows how people who are new to the subject can begin. The useful next step for a small business is to turn observations into clear questions and assigned work.
Watch W3C’s introduction
Easy Checks: A First Review of Web Accessibility was uploaded by W3C Web Accessibility Initiative on 14 May 2020. A transcript and the accompanying checks are also available from W3C.
What the video explains
The video introduces a preliminary review that can be carried out without extensive technical knowledge. It uses a page title as an example of a simple check and explains that most checks can be done in a browser. Its central limitation matters: an initial review is not a complete accessibility evaluation.
Use the video to begin a conversation with the people responsible for your website. Do not treat watching it, or completing one easy check, as evidence that every visitor can use every feature.
Choose a useful first sample
Start with a small set of pages that represent important visitor journeys. For a service business, that might be a main service page, its contact route and a document customers need. Write down why you chose them. This makes the scope visible and prevents a small sample being described later as a review of the whole website.
Include something beyond the homepage. A polished opening page can hide problems in a booking form, an older download or an information page added by a different editor. Ask staff which areas generate repeated customer questions.
Record observations someone else can reproduce
For each concern, record the page address, what you tried, what happened and what you expected. Add the browser or device where relevant. Avoid a note such as “the form is bad”; explain the specific obstacle you encountered.
| Record | Illustrative example |
|---|---|
| Page and task | Contact page: send a service enquiry |
| Observation | The confirmation did not explain whether the message was sent |
| Question for the team | How should the result be communicated to visitors? |
| Next action | Agency to investigate, then business owner to repeat the check |
This example is a reporting format, not a diagnosis of a particular website or a claim about a specific accessibility standard.
Assign work and request the right assessment
Separate corrections your content team can make from issues that need design or development investigation. Give each item an owner and a review date. Ask the agency which further assessment is appropriate, what it will cover and what evidence it will provide.
Be cautious about a single score presented without context. Ask what was tested, which pages were included and what remained outside the review. A useful handover makes uncertainty visible instead of concealing it behind a badge.
Use findings to improve the next brief
Keep a short record of recurring problems and include it when commissioning changes. The record can help the agency understand what visitors need to accomplish and where the current site gets in their way.
For the wider project discussion, see our guide to choosing web-design services and explanation of hosting and domain registration. An initial review is a starting point for practical work, followed by a suitable assessment and checks that the agreed changes helped.
