# AccessPulse report: demo-dental-clinic (demo)

> Demo report on a fictional sample site.

**Compliance score:** 63/100 (Moderate risk) · 13/18 checks passed · Scanned 2026-10-26T16:27:22.033Z

1 high lawsuit-trigger risk and 4 other issues found. Fix the high risks first: they are the issues most often cited in ADA demand letters.

## High lawsuit-trigger risks
### Form fields without labels (high, WCAG 1.3.1, 3.3.2, 4.1.2): 2 found
Booking, contact and checkout fields have no label a screen reader can announce, so blind customers cannot complete the form.

Found:
```html
<input type="tel" name="phone" placeholder="Phone">
```
Fix:
```html
<label for="field-1">Phone</label> <input id="field-1" type="tel" name="phone" placeholder="Phone">
```

Found:
```html
<select name="service">
```
Fix:
```html
<label for="field-2">service</label> <select id="field-2" name="service">
```

## Medium and low issues
### Skipped heading levels (medium, WCAG 1.3.1): 1 found
Headings jump levels (for example H1 to H3), which makes the page structure confusing for screen-reader navigation.

Found:
```html
<h1> … <h3>
```
Fix:
```html
Change <h3> to an <h2> (style it with CSS if it should look smaller).
```

### Contact or checkout fields without autocomplete (medium, WCAG 1.3.5): 1 found
Personal-information fields do not say what they collect, so browsers and assistive tools cannot fill them in for customers with motor or memory disabilities.

Found:
```html
<input type="tel" name="phone" placeholder="Phone">
```
Fix:
```html
<input autocomplete="tel" type="tel" name="phone" placeholder="Phone">
```

### No Accessibility Statement link (medium, WCAG EAA Annex V): 1 found
There is no link to an Accessibility Statement. The European Accessibility Act expects one for consumer-facing services, and it shows good faith to US customers.

Found:
```html
(no accessibility statement link found)
```
Fix:
```html
<a href="/accessibility">Accessibility Statement</a> <!-- in your footer; use the statement generated below -->
```

### Embedded frames without titles (medium, WCAG 4.1.2): 1 found
Embedded maps, videos or booking widgets have no title, so users cannot tell what they contain.

Found:
```html
<iframe src="https://maps.example.com/embed">
```
Fix:
```html
<iframe title="[What this embed shows, e.g. Map to our office]" src="https://maps.example.com/embed">
```

## Your Accessibility Statement (Markdown)
# Accessibility Statement for Demo Family Dental

Demo Family Dental is committed to making demo-dental-clinic.example usable by everyone, including people with disabilities.

## Our standard
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, which is also the basis of the European Accessibility Act (EN 301 549).

## Current status
This website is **partially conformant** with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not yet fully meet the standard.

## Known limitations
- Form fields without labels (WCAG 1.3.1, 3.3.2, 4.1.2). We are working to fix this.
- Skipped heading levels (WCAG 1.3.1). We are working to fix this.
- Contact or checkout fields without autocomplete (WCAG 1.3.5). We are working to fix this.
- No Accessibility Statement link (WCAG EAA Annex V). We are working to fix this.
- Embedded frames without titles (WCAG 4.1.2). We are working to fix this.

## Feedback and contact
If you have trouble using any part of this website, please contact us and we will help you and provide the information in another way:
- Email: accessibility@yourdomain.com

We aim to respond within 2 business days.

## How we checked
This statement was prepared on 2026-10-26 using a read-only automated review, and we review our site regularly. We do not use accessibility overlay widgets.


---
Automated, read-only technical diagnostic. Not legal advice and not a certification of compliance. Automated tools detect only part of WCAG; manual testing is still needed.