---
title: "How to make a website accessible: practical tests · Lyntev"
description: "Plan an accessibility review covering keyboard use, zoom, content and forms. Includes a barrier log, a worked example and retest criteria."
url: "https://lyntev.com/en/guides/make-website-accessible"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. How to make a website accessible: assess journeys and remove barriers

# How to make a website accessible: assess journeys and remove barriers

Accessibility needs to be present in reading, navigation and actions. A form may look clear yet remain impossible to correct with a keyboard; a menu may open and hide the focused option. The following method organises an initial review with concrete evidence and a correction list, without confusing an automated tool with a complete evaluation.

By [Lyntev](<https://lyntev.com/en/company>). Updated on 17 November 2026.
About 5 minutes to read.

[Start reading](<https://lyntev.com/en/guides/make-website-accessible#leitura>)[Download worksheet](<https://lyntev.com/recursos/en/tornar-site-acessivel.txt>)

**From review to publication**A process with approval criteria at every stage.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/tornar-site-acessivel>); source revision 17 November 2026.

By the end, you can:

- Choose journeys and states to evaluate
- Document reproducible barriers
- Correct and confirm the complete journey

In this guide

1. [Choose tasks, components and states](<https://lyntev.com/en/guides/make-website-accessible#ambito-da-avaliacao>)
2. [Go through the actions without a mouse](<https://lyntev.com/en/guides/make-website-accessible#teclado-e-foco>)
3. [Check reading, contrast and reflow](<https://lyntev.com/en/guides/make-website-accessible#leitura-e-ampliacao>)
4. [Make information understandable without depending on the design](<https://lyntev.com/en/guides/make-website-accessible#estrutura-e-conteudo>)
5. [Test errors, confirmation and motion](<https://lyntev.com/en/guides/make-website-accessible#formularios-e-movimento>)
6. [Combine tools, manual review and users](<https://lyntev.com/en/guides/make-website-accessible#priorizar-correcoes>)
7. [Record the barrier so it can be reproduced](<https://lyntev.com/en/guides/make-website-accessible#ficha-barreira>)
8. [Sources and criteria](<https://lyntev.com/en/guides/make-website-accessible#fontes>)

## Choose tasks, components and states

Start with the main journey: find a service, open information, complete an enquiry and confirm the result. Include repeated components such as the menu, header, storage notice and footer. Then choose pages with different features: tables, video, filters or dialogues. Do not restrict the review to the homepage; many barriers appear only when someone tries to act.

Also record states a screenshot does not show: an open menu, a field with an error, loading, confirmation and enlarged content. Define the browser, device and assistive technologies used in the test. The evaluation should state its scope so the team knows what was examined and what remains. W3C distinguishes initial checks, tools and more complete methodologies; combine approaches according to the required depth.

- [W3C: accessibility evaluation](<https://www.w3.org/WAI/test-evaluate/>)

## Go through the actions without a mouse

Start at the top and use Tab to move forward, Shift+Tab to go back and the appropriate keys for each control. Observe whether you can identify the focused element and whether the order makes sense. When opening a dialogue, check that focus moves somewhere useful and returns to the control that opened it when closed. Try leaving each component; a person should not become trapped in a sequence with no way out.

In the fictitious example of a visit request, the “Add information” button opens a panel. The test finds that focus remains behind the panel and the close button responds only to the mouse. The log describes the steps, element and expected result. The correction includes focus behaviour and keyboard operation, followed by a retest of the complete submission rather than just the corrected button.

Go through the actions without a mouse

| Test | Observable barrier | Retest |
| --- | --- | --- |
| Open the menu by keyboard | Focus disappears behind the header | All options remain identifiable |
| Close the dialogue | Focus jumps to the start of the page | It returns to the point that initiated the action |
| Correct the form | The error only changes the border colour | An understandable message associated with the field |

## Check reading, contrast and reflow

Enlarge the page and text, reduce the width and work through the essential content. Observe headings, tables, buttons and long messages. A fixed element can occupy almost all the available space as text grows. The test aims to find overlaps, clipping and inaccessible actions; confirming that the layout still looks similar to the original design is not enough.

Measure contrast against the background actually shown, including focus and error states and colour modes. Check whether colour is the only way to distinguish a condition. WCAG criteria have specific requirements and exceptions, so the team should record the applicable criterion and measured result. Avoid declaring an overall pass based only on the main text colour while leaving icons, useful borders and states unevaluated.

- [W3C: WCAG 2.2 reference](<https://www.w3.org/WAI/WCAG22/quickref/>)

## Make information understandable without depending on the design

Read headings in sequence and check that they describe the sections. Use list elements for lists and appropriate headers in data tables. The page title and language need to be identified. An impressive visual hierarchy can conceal a confusing structure; the implementation should make main content, navigation and supplementary information recognisable.

Review image alternatives and instructions such as “click the green button on the right”. Name an action by what it does, because position and colour can change. For audio and video, prepare the resources needed to communicate information in other ways, according to the content and evaluation scope. A decorative video and an explanation with spoken instructions have different needs.

- [W3C: page structure](<https://www.w3.org/WAI/tutorials/page-structure/>)
- [W3C: image alternatives](<https://www.w3.org/WAI/tutorials/images/>)

## Test errors, confirmation and motion

Fields need names and instructions that remain available while completing them. Submit an incomplete form, correct an error and confirm success. Observe whether messages reach people using assistive technology and whether they can find what needs correcting. Text appearing far from a field may be visible yet still difficult to discover in the actual journey.

Try the reduced-motion preference and available pause controls. The experience can retain its visual identity through composition, colour and subtle transitions while preserving reading. Avoid hiding the main action until an animation finishes. Also test carousels and moving backgrounds while completing fields: content should remain stable and actions should retain a usable position.

- [W3C: accessible forms](<https://www.w3.org/WAI/tutorials/forms/>)
- [W3C: WCAG 2.2 reference](<https://www.w3.org/WAI/WCAG22/quickref/>)

## Combine tools, manual review and users

An automated tool can find markup and contrast problems, but it cannot decide whether alternative text makes sense or a task is understandable. Review results before turning them into work. Group failures of the same component to correct their common cause, then retest a representative sample, including contexts where the component behaves differently.

Prioritise blocked journeys and shared components. Where possible, include people who use assistive technologies, with clear tasks and respectful conditions. Frequent mistakes include treating a badge as sufficient evidence, correcting only the homepage and confusing the absence of alerts with the absence of barriers. A conformance evaluation requires its own scope, criteria and methodology; this work log helps prepare for it.

- [W3C: accessibility evaluation](<https://www.w3.org/WAI/test-evaluate/>)

## Record the barrier so it can be reproduced

A good log lets another person find the same problem without an additional meeting. Describe observed and expected behaviour, avoiding vague phrases such as “improve accessibility”. After correcting it, repeat the steps and the subsequent journey. Keep retest evidence and update the status to distinguish an implemented correction from one actually confirmed.

### Worksheet for your project

```
Page, version and component:
Task and interface state:
Device, browser and assistive technology:
Steps to reproduce:
Observed behaviour:
Expected behaviour and reference criterion:
Impact on the journey:
Screenshot or record without personal data:
Cause and proposed correction:
Person responsible and priority:
Retest steps and result:
Other pages using the same component:
```

## Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

- [W3C: avaliação de acessibilidade](<https://www.w3.org/WAI/test-evaluate/>)
- [W3C: referência WCAG 2.2](<https://www.w3.org/WAI/WCAG22/quickref/>)
- [W3C: estrutura de páginas](<https://www.w3.org/WAI/tutorials/page-structure/>)
- [W3C: alternativas de imagens](<https://www.w3.org/WAI/tutorials/images/>)
- [W3C: formulários acessíveis](<https://www.w3.org/WAI/tutorials/forms/>)

## Continue to your next decision.

- [Prepare a usable form](<https://lyntev.com/en/guides/create-contact-form>)
- [Choose image alternatives and crops](<https://lyntev.com/en/guides/choose-prepare-website-images>)
- [Publication checklist](<https://lyntev.com/en/guides/professional-website-launch-checklist>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Put this decision into practice.

Steps, examples and worksheets to prepare the work in your business.

[Find a reading path](<https://lyntev.com/en/guides#percursos-title>)

### [How to prepare a digital menu that is easy to read and keep up to date](<https://lyntev.com/en/guides/restaurant-digital-menu>)

A menu needs to reflect the service being provided, not merely be accessible via a QR code.

### [How to help Google find your business’s images](<https://lyntev.com/en/guides/help-google-find-business-images>)

Check discovery, context and the destination of visits arriving through images.

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

Technology with context, original analysis and sources you can consult.
