This is a sample for a fictional town, so you can see what our free scan gives you. Get a free report for your own website.

Accessibility report for www.town-of-example.test

Scanned September 26, 2026. We checked 3 pages and 2 PDF documents against the legal standard, WCAG 2.1 level AA.

Summary

31 problems found on web pages
8 that can block people completely
3 of 3 pages with problems
2 of 2 PDFs screen readers cannot read reliably

Your legal deadline

April 26, 2028, 578 days from the date of this scan. ADA Title II rule, local governments serving fewer than 50,000 people and special districts.

What we found, most serious first

Blind visitors cannot understand pictures or graphics if they lack descriptive alternative text for screen readers.

Can block people completely Found 4 times on 1 page.
Technical detail for your web developer

Rule: image-alt (Images must have alternate text)

First place found: https://www.town-of-example.test/
```
<img class="hero" src="/img/townhall.jpg">
```
Keyboard and screen reader users do not know what information to enter into form fields missing descriptive labels.

Can block people completely Found 3 times on 1 page.
Technical detail for your web developer

Rule: label (Form elements must have labels)

First place found: https://www.town-of-example.test/pay-a-bill
```
<input id="acct" name="account" placeholder="Account number">
```
People who use a keyboard instead of a mouse cannot reach some buttons or links, so they cannot use them at all.

Can block people completely Found 1 time on 1 page.
Technical detail for your web developer

Rule: keyboard-unreachable (Something you can click cannot be reached with the keyboard)

First place found: https://www.town-of-example.test/
```
<div class="menu-toggle" onclick="openMenu()">Menu</div>
```
People with low vision cannot read text or distinguish buttons if colors lack sufficient brightness difference.

Major barrier Found 11 times on 1 page.
Technical detail for your web developer

Rule: color-contrast (Elements must meet minimum color contrast ratio thresholds)

First place found: https://www.town-of-example.test/
```
<span class="news-date">Sept 12</span>
```
People who use a keyboard cannot see where they are on the page, because nothing highlights the button or link they are on.

Major barrier Found 6 times on 1 page.
Technical detail for your web developer

Rule: focus-not-visible (Keyboard focus is not visible)

First place found: https://www.town-of-example.test/
```
<a class="nav-link" href="/services">Services</a>
```
Screen reader users do not know where a link goes if it lacks descriptive text or an image alternative.

Major barrier Found 2 times on 1 page.
Technical detail for your web developer

Rule: link-name (Links must have discernible text)

First place found: https://www.town-of-example.test/
```
<a class="social-fb" href="https://facebook.example/town"><i class="icon-fb"></i></a>
```
Blind visitors hear a useless description, such as a file name or the word "image", instead of what the picture shows.

Major barrier Found 1 time on 1 page.
Technical detail for your web developer

Rule: alt-text-poor (Image description says nothing useful)

First place found: https://www.town-of-example.test/council/agendas
```
<img class="seal" src="/img/seal.png" alt="image">
```
Screen reader users hear links like "click here" or "read more" that do not say where they go.

Makes the site harder to use Found 2 times on 1 page.
Technical detail for your web developer

Rule: link-purpose (Link text does not say where the link goes)

First place found: https://www.town-of-example.test/pay-a-bill
```
<a class="more" href="/utilities/rates">Click here</a>
```
Heading levels should only increase by one

Makes the site harder to use Found 1 time on 1 page.
Technical detail for your web developer

Rule: heading-order (Heading levels should only increase by one)

First place found: https://www.town-of-example.test/council/agendas
```
<h4>Upcoming meetings</h4>
```

PDF documents

2 documents out of 2 checked cannot be read properly by a screen reader:

council-minutes-2026-09.pdf: not built for screen readers (no reading structure), 6 pages.
building-permit-form.pdf: a scanned picture of a page with no readable text, 2 pages.

Fix all of this

Our fixed-price packages write the fixes for the problems in a report like this, rebuild PDFs that lack tags or real text, and give you a written test report. See the packages.

About this report

This report lists the results of our automated WCAG 2.1 AA tests. No automated test finds every accessibility problem. This report is information, not legal advice.

Accessibility report for www.town-of-example.test

Summary

Your legal deadline

What we found, most serious first

Blind visitors cannot understand pictures or graphics if they lack descriptive alternative text for screen readers.

Keyboard and screen reader users do not know what information to enter into form fields missing descriptive labels.

People who use a keyboard instead of a mouse cannot reach some buttons or links, so they cannot use them at all.

People with low vision cannot read text or distinguish buttons if colors lack sufficient brightness difference.

People who use a keyboard cannot see where they are on the page, because nothing highlights the button or link they are on.

Screen reader users do not know where a link goes if it lacks descriptive text or an image alternative.

Blind visitors hear a useless description, such as a file name or the word "image", instead of what the picture shows.

Screen reader users hear links like "click here" or "read more" that do not say where they go.

Heading levels should only increase by one

PDF documents

Fix all of this

About this report