# Complete a testing step

> Testing steps in sitebrunch Accessibility always follow the same structure. Here you learn how to complete a testing step.

[Video: https://youtu.be/LF-waPaq9UY](https://youtu.be/LF-waPaq9UY)

## Requirements:

- You have an account and can log in.

- You have at least the Solo plan.

- You have created a project for your website.

- You have created an audit (see the guide “[Create an audit](/en/hilfecenter/accessibility/audits/create-an-audit)”)

## Start a testing step

Open the audit you created. It shows a list of all testing steps. Pick a testing step and click the “Start check” link to open it.

Each testing step in the audit has:

- a title

- a short description with an illustration

- a status indicator: passed, failed, not applicable or not checked yet

- Tags:

Complexity: How hard is it to test?

- Duration: quick or long?

- Role: Who will probably have to fix it? Design, development or editorial?

- Which requirement in EN 301 549 asks for this? (e.g. 9.2.4.2; this is the number of the official requirement for this testing step in the European accessibility standard)

![Screenshot of a testing step in the audit list with labels for title, short description, tags and status. The step is “Titel der Seite sinnvoll” (meaningful page title) with tags for complexity, duration, role and the requirement number 9.2.4.2, an illustration and the “Start check” button.](https://website-assets.sitebrunch.com/storage/hilfecenter/audit/prufschritt-durchfuhren/prufschritt-beschreibung.jpg)

To start the testing step, click the “Start check” link. 

## The audit tool

The audit tool consists of the page you are testing and several toolbars that help you test.

![Screenshot of the open audit tool on a test website. Labels mark the list of all testing steps at the top, the toolbar on the right, the current testing step in the side panel, the pages at the bottom left, the rating buttons at the bottom and the helper tool at the bottom right.](https://website-assets.sitebrunch.com/storage/hilfecenter/audit/prufschritt-durchfuhren/prufschritt-offenes-pruftool.jpg)

### Page navigation and page rating

You find the page navigation at the bottom, in the lower toolbar. Each page you chose as a test page appears as a colored status circle.

- Not tested yet

- In progress 

- Passed

- Failed

- Not applicable

Click a circle to jump to that page.

![Screenshot of the lower toolbar in the audit tool. On the left are the status circles for the pages, on the right the rating buttons “Failed”, “Not applicable” and “Passed”. The options menu of one button is open and shows “For all pages”.](https://website-assets.sitebrunch.com/storage/hilfecenter/audit/prufschritt-durchfuhren/prufschritt-seitennavigation-und-bewertung.jpg)

You find the rating tools next to the page navigation. Use them to mark a page as:

- Failed

- Not applicable

- Passed

If you want to give all pages the same status, click the rating options next to that status button and choose “For all pages”.

After you rate a page, sitebrunch Accessibility takes you to the next page to test.

### The tools

On the right edge you find the tools that support you while testing.

#### Cursor selection

You can switch between three cursors: 

- **Default cursor**: Use the default cursor when you want to move around the website and use it

- **New comment**: Use the comment cursor when you want to comment on something on the website

- **Element info**: Use the element info to learn more about how an element is built (e.g. heading level, roles, ARIA attributes).

You can switch cursors with the keyboard: the v key for the default cursor, the c key for the comment cursor, the x key for the element info.

![Screenshot of the cursor with element info over a link. Information such as size, contrast, name, role and keyboard operability is shown in an overlay.](https://website-assets.sitebrunch.com/storage/hilfecenter/audit/prufschritt-durchfuhren/prufschritt-elementinfos.jpg)

#### Helpers

- **Comments**: The comment list shows all comments that you and others wrote for this page. The comments always refer only to the current testing step.

- **Testing tools**: A list of helper tools, such as a contrast checker. These tools help you find typical accessibility problems faster.

- **Accessibility check**: Here you can have the page scanned automatically for certain technical accessibility problems.

- **Show testing step**: Learn how to test the testing step.

![Screenshot of automated tools in the test. No errors were found.](https://website-assets.sitebrunch.com/storage/hilfecenter/audit/prufschritt-durchfuhren/prufschritt-hilfsmittel.png)

#### Show testing step

This section explains exactly how to test the testing step. You learn:

- What is checked?

- How is it checked? (With video, illustrations and text descriptions)

- Are there notes and exceptions?

You also get a matching helper tool so you can start right away. For the testing step “Language of page specified” you get the “Show language” tool. One click shows you which language is set on the website.

![Screenshot of the side panel for the testing step “Language of page specified”. Under “How is it checked” there is a video, an illustration and numbered instructions. At the bottom the “Show language” helper tool is highlighted.](https://website-assets.sitebrunch.com/storage/hilfecenter/audit/prufschritt-durchfuhren/prufschritt-prufschritt-erlernen-&-selber-testen.png)

### The page you are testing

The actual check happens on the page you are testing. Use the helpers in the audit tool to analyze the page step by step, and place comments with the comment cursor right where the problem is.

#### Place comments

When you notice a problem on the page, place a comment at that spot with the comment cursor. In the comment field you can describe what you noticed.

#### Use automatic suggestions

To make testing as easy and efficient as possible, we analyzed many real audit reports and built the most common issues right into sitebrunch Accessibility. As soon as you create a comment, the tool suggests possible violations that fit.

If one of the suggestions fits, you can select it. sitebrunch then fills in the problem description and a proposed solution for you. The proposed solutions follow the official WCAG recommendations.

![Screenshot of a new comment on the test website. Below the problem description field, the comment form lists matching problem and solution suggestions, each marked as an error.](https://website-assets.sitebrunch.com/storage/hilfecenter/audit/prufschritt-durchfuhren/prufschritt-kommentar-setzen.jpg)

#### Document issues yourself

You can also record any finding by hand:

- In the “Problem Description” field, describe exactly what the problem is (e.g. “The ‘Next’ button has no visible focus outline.”).

- In the “Proposed Solution” field, add how the problem can be fixed (e.g. “Define a clearly visible focus state for all interactive elements.”).

![Screenshot of the comment form with the fields for problem description, proposed solution, severity, departments, attachments and the testing step selection.](https://website-assets.sitebrunch.com/storage/hilfecenter/audit/prufschritt-durchfuhren/prufschritt-kommentar-schreiben.jpg)

#### Set the severity of the problem

Besides the description, you can choose how severe the finding is:

- **Note**: General accessibility notes that help improve content but are not a direct violation of WCAG or EN 301 549.

- **Error**: A violation of the requirements that must be fixed to comply with the relevant laws (e.g. BFSG, BGG, BITV).

- **Critical**: A particularly serious violation that creates a major barrier and should be fixed as early as possible.

This classification is an addition specific to sitebrunch, so you can prioritize your findings better.

#### Add the responsible role and files

Under “Departments” you can say who will probably have to solve the problem, for example design, development or editorial. You can also select several.

You can also upload extra files, such as screenshots, design files or explanatory documents that describe the finding in more detail.

#### Assign a comment to a different testing step

If you notice something while testing that really belongs to a different testing step, you do not have to switch steps. In the comment form, choose the right testing step in the “Testing step” field to move the comment there. This keeps your findings neatly sorted by topic, even if you spot them somewhere else.

#### Automatic screenshot

After you save the comment, sitebrunch automatically takes a screenshot of the spot you commented on. The affected spot is highlighted.

This screenshot appears in the audit report together with your problem description. That way the people responsible can later see exactly where the problem is on the page and what to do.

### Switch testing steps

The toolbar at the top of the audit tool lets you switch between testing steps. In the testing step field you can search for a term to quickly find the step you need.

The toolbar also offers more options:

- **Copy URL**: Copy the address of the page you are testing, for example to share it with your team.

- **Switch view**: View your website at different screen sizes (desktop, tablet or smartphone).

- **Zoom**: Zoom in or out of the page to look at individual areas more closely.

#### How the test flow is meant to work

The audit is set up so that you usually test all pages one after another for the same testing step. For example, once you have checked the criterion “Language of page specified” on all pages, sitebrunch automatically takes you to the next testing step.

So you do not have to switch testing steps by hand, but you can do so at any time if that suits you better.

You can also pause the test at any time: just close the audit tool. Later you can reopen the audit tool from the audit overview and pick up where you left off.

### Finish the audit

Once you have worked through all testing steps, you can finish the audit. You find the **“Finish Audit” **button in the audit overview, at the very bottom below the list of testing steps.

![Screenshot of the audit overview in the sitebrunch dashboard. At the bottom right, below the list of testing steps, the “Finish Audit” button is highlighted.](https://website-assets.sitebrunch.com/storage/hilfecenter/audit/prufschritt-durchfuhren/prufbericht-abschliessen.png)

Make sure you are really done with the audit before you click “Finish Audit”, because you cannot reopen a finished audit.

You can, however, create a re-audit from a finished audit. A re-audit is a copy of your previous audit, including all findings. It lets you start again “from the top” later and check which problems have been fixed in the meantime.

You can find more in the article **“Create a re-audit”**.

---

- Previous article: [Create an audit](https://www.sitebrunch.com/en/hilfecenter/accessibility/audits/create-an-audit.md)
- Next article: [The audit report](https://www.sitebrunch.com/en/hilfecenter/accessibility/audits/the-audit-report.md)

## Help Center: contents

- [Accessibility](https://www.sitebrunch.com/en/hilfecenter/accessibility.md)
  - [Getting started](https://www.sitebrunch.com/en/hilfecenter/accessibility/getting-started.md)
    - [Create a project](https://www.sitebrunch.com/en/hilfecenter/accessibility/getting-started/create-a-project.md)
    - [Set up WCAG monitoring](https://www.sitebrunch.com/en/hilfecenter/accessibility/getting-started/set-up-wcag-monitoring.md)
    - [Check a PDF](https://www.sitebrunch.com/en/hilfecenter/accessibility/getting-started/check-a-pdf.md)
  - [WCAG monitoring](https://www.sitebrunch.com/en/hilfecenter/accessibility/wcag-monitoring.md)
    - [The monitoring overview](https://www.sitebrunch.com/en/hilfecenter/accessibility/wcag-monitoring/the-monitoring-overview.md)
    - [Add pages to monitoring](https://www.sitebrunch.com/en/hilfecenter/accessibility/wcag-monitoring/add-pages-to-monitoring.md)
    - [Email notifications](https://www.sitebrunch.com/en/hilfecenter/accessibility/wcag-monitoring/email-notifications.md)
  - [Audits](https://www.sitebrunch.com/en/hilfecenter/accessibility/audits.md)
    - [Create an audit](https://www.sitebrunch.com/en/hilfecenter/accessibility/audits/create-an-audit.md)
    - [Complete a testing step](https://www.sitebrunch.com/en/hilfecenter/accessibility/audits/complete-a-test-step.md) (this article)
    - [The audit report](https://www.sitebrunch.com/en/hilfecenter/accessibility/audits/the-audit-report.md)
    - [Create a re-audit](https://www.sitebrunch.com/en/hilfecenter/accessibility/audits/create-a-re-audit.md)
- [User Experience](https://www.sitebrunch.com/en/hilfecenter/user-experience.md)
  - [Getting started](https://www.sitebrunch.com/en/hilfecenter/user-experience/getting-started.md)
    - [Set up a project](https://www.sitebrunch.com/en/hilfecenter/user-experience/getting-started/set-up-a-project.md)
    - [Install the snippet](https://www.sitebrunch.com/en/hilfecenter/user-experience/getting-started/install-the-snippet.md)
    - [From install to first visit](https://www.sitebrunch.com/en/hilfecenter/user-experience/getting-started/from-install-to-first-visit.md)
    - [Read the weekly overview](https://www.sitebrunch.com/en/hilfecenter/user-experience/getting-started/read-the-weekly-overview.md)
  - [Metrics](https://www.sitebrunch.com/en/hilfecenter/user-experience/metrics.md)
    - [The Metrics overview](https://www.sitebrunch.com/en/hilfecenter/user-experience/metrics/the-metrics-overview.md)
    - [Filter and compare](https://www.sitebrunch.com/en/hilfecenter/user-experience/metrics/filter-and-compare.md)
    - [Pages and sections](https://www.sitebrunch.com/en/hilfecenter/user-experience/metrics/pages-and-sections.md)
    - [Analyze campaigns](https://www.sitebrunch.com/en/hilfecenter/user-experience/metrics/analyze-campaigns.md)
  - [Conversions](https://www.sitebrunch.com/en/hilfecenter/user-experience/conversions.md)
    - [Set up events and goals](https://www.sitebrunch.com/en/hilfecenter/user-experience/conversions/set-up-events-and-goals.md)
    - [The Conversions overview](https://www.sitebrunch.com/en/hilfecenter/user-experience/conversions/the-conversions-overview.md)
    - [Analyze interactions](https://www.sitebrunch.com/en/hilfecenter/user-experience/conversions/analyze-interactions.md)
    - [Create a funnel](https://www.sitebrunch.com/en/hilfecenter/user-experience/conversions/create-a-funnel.md)
  - [Journeys](https://www.sitebrunch.com/en/hilfecenter/user-experience/journeys.md)
    - [Journeys at a glance](https://www.sitebrunch.com/en/hilfecenter/user-experience/journeys/journeys-at-a-glance.md)
    - [See where visits go](https://www.sitebrunch.com/en/hilfecenter/user-experience/journeys/see-where-visits-go.md)
    - [Create a route](https://www.sitebrunch.com/en/hilfecenter/user-experience/journeys/create-a-route.md)
    - [Read backwards from a goal](https://www.sitebrunch.com/en/hilfecenter/user-experience/journeys/read-backwards-from-a-goal.md)
  - [Live Heatmaps](https://www.sitebrunch.com/en/hilfecenter/user-experience/live-heatmaps.md)
    - [Live Heatmaps at a glance](https://www.sitebrunch.com/en/hilfecenter/user-experience/live-heatmaps/live-heatmaps-at-a-glance.md)
    - [Read clicks](https://www.sitebrunch.com/en/hilfecenter/user-experience/live-heatmaps/read-clicks.md)
    - [Scroll depth and devices](https://www.sitebrunch.com/en/hilfecenter/user-experience/live-heatmaps/scroll-depth-and-devices.md)
    - [Filter by source and goal](https://www.sitebrunch.com/en/hilfecenter/user-experience/live-heatmaps/filter-by-source-and-goal.md)