---
title: Quick start
description: Go from a fresh install to a checked site in 15 minutes. Scan your content, fix the most common issues, set up the editor and create an accessibility statement.
---

# Quick start

This walkthrough takes you from a fresh install to a checked site, with the biggest problems fixed, in about 15 minutes.

## 1. Check everything you've published

Go to <span class="screen-path">Accessibility → Overview</span> and click **Check all content**. You'll get:

- an **Average automated score** (see [Scores & severities](/scoring))
- **Errors**: problems Lumtera is confident about
- **Needs review**: things a person should confirm
- **Coverage**: how much of your content has been checked

## 2. Fix the most common issues first

Start with the **Fix once, clear many** card, if you see it. It lists the same problem in the same markup on several items, such as a vague "Read more" link in a synced pattern, or a missing label in a form used on every page. Fix it in the theme, pattern or block it comes from, and every item clears.

The **Most common issues** card lists the checks that fire most often across your site. Click an issue to see every post that has it in the [Content report](/site-report#content-report). Then click **Issues** on a row to see what to fix. The report's **By issue** view groups the same finding across pages.

## 3. Describe your images

Missing alt text is usually the most common error. Go to <span class="screen-path">Accessibility → Alt text</span>. Describe each image once, then click **Add it to those posts** to fill in the posts that show it without a description. See [Alt text manager](/alt-text).

## 4. Fix issues in the editor

Open a post from **Needs attention** on the Overview. In the editor's **Accessibility** sidebar:

- Click **Select block** to jump to the problem.
- Use the **quick fix** button where there is one, such as **Change to H3** or **Convert to a list**. You can undo it like any edit.
- For items that need review, decide. If it's fine, click **Dismiss…** and add a short reason.

See [Block editor sidebar](/block-editor).

## 5. Check a live page, theme included

Open any published page while logged in, and click **Accessibility** in the admin bar. The **Whole page** tab checks your header, menus and footer, and measures real color contrast. See [Review mode](/review-mode).

## 6. Decide how strict to be

In <span class="screen-path">Accessibility → Settings</span>:

- **Before publishing**: choose whether authors see a summary of errors before they publish (the default), or must confirm to publish anyway.
- **Checks**: make any check stricter or softer, or switch it off.
- **Permissions**: choose which roles see the reports, dismiss errors and use review mode. See [Roles & permissions](/permissions).

See [Settings](/settings).

## 7. Publish an accessibility statement

Go to <span class="screen-path">Accessibility → Statement</span>, fill in your details, and click **Create draft statement**. Review the draft, publish it, and link to it from your footer. See [Accessibility statement](/statement).

## 8. Test the rest by hand

A score of 100 means "no automated issues found", not "compliant". Spend five minutes on the [manual check](/manual-testing#the-five-minute-manual-check) on your key pages. For a fuller pass, work through the [guided manual checks](/manual-checks) in the block editor and record the results on each page.