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.example.com
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 a blind person cannot read
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.example.com/
<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.example.com/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.example.com/
<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.example.com/
<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.example.com/
<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.example.com/
<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.example.com/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.example.com/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.example.com/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. Some limits are specific enough to name:
- Captions: for video and audio played directly on the page, we check that a caption track exists, not whether the wording is accurate or complete. We do not check for audio description, or for captions on videos embedded from services such as YouTube or Vimeo.
- Reflow at 400% zoom: we check for content that forces side-to-side scrolling at a 400%-zoom-equivalent width, not whether every feature still works at that size.
- Form error handling: this free scan checks that form fields are labeled; it does not press any submit button, so it does not check error messages (a paid audit does).
- Meaningful sequence (reading order): we check the order elements sit in the code, not whether that order actually makes sense to someone using it.
- Timing and flashing content: we check for flashing fast enough to be a seizure risk, not every case of timing that may be too short.
Passing our automated tests is not the same as meeting every legal duty. Title II of the ADA separately requires a written self-evaluation of your programs, services and policies (28 CFR 35.105) and a grievance procedure for accessibility complaints (28 CFR 35.107). Section 504 imposes similar duties on HHS-funded health providers. This report covers neither duty. This report is information, not legal advice.