# AccessPulse report: demo-ecommerce-store (demo)

> Demo report on a fictional sample site.

**Compliance score:** 0/100 (High risk) · 3/18 checks passed · Scanned 2026-11-02T02:46:44.276Z

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

## High lawsuit-trigger risks
### Images missing alt text (high, WCAG 1.1.1): 2 found
Screen-reader users cannot tell what these images show. Missing alt text on product and service images is one of the most common triggers in ADA demand letters.

Found:
```html
<img src="/logo.png">
```
Fix:
```html
<img alt="[Describe this image, e.g. product name and colour]" src="/logo.png">
```

Found:
```html
<img src="/tent.jpg">
```
Fix:
```html
<img alt="[Describe this image, e.g. product name and colour]" src="/tent.jpg">
```

### 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="email" name="email" placeholder="Email for 10% off">
```
Fix:
```html
<label for="field-1">Email for 10% off</label> <input id="field-1" type="email" name="email" placeholder="Email for 10% off">
```

Found:
```html
<input type="text" name="card_number" placeholder="Card number">
```
Fix:
```html
<label for="field-2">Card number</label> <input id="field-2" type="text" name="card_number" placeholder="Card number">
```

### Buttons with no accessible name (high, WCAG 4.1.2): 1 found
Some buttons (often icon-only buttons like cart, menu or close) have no text, so assistive technology announces just "button".

Found:
```html
<button><svg viewBox="0 0 10 10"></svg></button>
```
Fix:
```html
<button aria-label="[What this button does, e.g. Open cart]"><svg viewBox="0 0 10 10"></svg></button>
```

### Links with no accessible name (high, WCAG 2.4.4, 4.1.2): 2 found
Some links (often social icons or image links) have no readable text, so users cannot tell where they go.

Found:
```html
<a href="/"><img src="/logo.png"></a>
```
Fix:
```html
<a aria-label="[Where this link goes, e.g. Our Instagram]" href="/"><img src="/logo.png"></a>
```

Found:
```html
<a href="https://instagram.com/demo"><i class="icon-instagram"></i></a>
```
Fix:
```html
<a aria-label="[Where this link goes, e.g. Our Instagram]" href="https://instagram.com/demo"><i class="icon-instagram"></i></a>
```

### Missing page language (high, WCAG 3.1.1): 1 found
The page does not declare its language, so screen readers may read it with the wrong pronunciation.

Found:
```html
<html>
```
Fix:
```html
<html lang="en">
```

### Mobile zoom is disabled (high, WCAG 1.4.4): 1 found
The viewport blocks pinch-zoom, so customers with low vision cannot enlarge text on their phone.

Found:
```html
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no">
```
Fix:
```html
<meta name="viewport" content="width=device-width, initial-scale=1">
```

### Accessibility overlay widget detected (high, WCAG n/a (legal risk)): 1 found
An automated overlay widget was found. Overlays do not fix the underlying code, have been named in many lawsuits, and one vendor was fined $1M by the FTC over its claims. Fix the HTML instead.

Found:
```html
<script src="https://cdn.userway.org/widget.js">
```
Fix:
```html
Remove the overlay script and fix the issues listed in this report directly in your theme or templates.
```

## 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
<h2> … <h4>
```
Fix:
```html
Change <h4> to an <h3> (style it with CSS if it should look smaller).
```

### No main heading (H1) (medium, WCAG 1.3.1, 2.4.6): 1 found
The page has no H1, so assistive technology users cannot quickly find the main topic.

Found:
```html
(no <h1> found)
```
Fix:
```html
<h1>[Your main page heading, e.g. Family Dentistry in Austin]</h1>
```

### No "skip to main content" link (medium, WCAG 2.4.1): 1 found
Keyboard users must tab through the whole menu on every page before reaching the content.

Found:
```html
(no skip link found)
```
Fix:
```html
<a class="skip-link" href="#main">Skip to main content</a> <!-- and on your content wrapper: <main id="main"> -->
```

### Invalid ARIA roles (medium, WCAG 4.1.2): 1 found
Some elements use ARIA roles that do not exist, which confuses assistive technology.

Found:
```html
<nav role="navgation">
```
Fix:
```html
<nav role="[valid role, e.g. button or navigation]">
```

### Contact or checkout fields without autocomplete (medium, WCAG 1.3.5): 2 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="email" name="email" placeholder="Email for 10% off">
```
Fix:
```html
<input autocomplete="email" type="email" name="email" placeholder="Email for 10% off">
```

Found:
```html
<input type="text" name="card_number" placeholder="Card number">
```
Fix:
```html
<input autocomplete="cc-number" type="text" name="card_number" placeholder="Card number">
```

### Keyboard focus indicator removed (medium, WCAG 2.4.7, 2.4.11): 1 found
The styles remove the focus outline, so keyboard users cannot see where they are on the page.

Found:
```html
*:focus{outline:none}
```
Fix:
```html
*:focus:focus-visible { outline: 3px solid #1a56db; outline-offset: 2px; }
```

### 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 -->
```

### Media that plays automatically with sound (medium, WCAG 1.4.2): 1 found
Video or audio starts on its own with sound, which interferes with screen readers.

Found:
```html
<video src="/promo.mp4" autoplay>
```
Fix:
```html
<video src="/promo.mp4" controls>
```

## Your Accessibility Statement (Markdown)
# Accessibility Statement for Demo Outdoor Gear Shop

Demo Outdoor Gear Shop is committed to making demo-ecommerce-store.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
- Images missing alt text (WCAG 1.1.1). We are working to fix this.
- Form fields without labels (WCAG 1.3.1, 3.3.2, 4.1.2). We are working to fix this.
- Buttons with no accessible name (WCAG 4.1.2). We are working to fix this.
- Links with no accessible name (WCAG 2.4.4, 4.1.2). We are working to fix this.
- Missing page language (WCAG 3.1.1). We are working to fix this.
- Mobile zoom is disabled (WCAG 1.4.4). We are working to fix this.
- Skipped heading levels (WCAG 1.3.1). We are working to fix this.
- No main heading (H1) (WCAG 1.3.1, 2.4.6). We are working to fix this.
- No "skip to main content" link (WCAG 2.4.1). We are working to fix this.
- Invalid ARIA roles (WCAG 4.1.2). We are working to fix this.
- Contact or checkout fields without autocomplete (WCAG 1.3.5). We are working to fix this.
- Keyboard focus indicator removed (WCAG 2.4.7, 2.4.11). We are working to fix this.
- No Accessibility Statement link (WCAG EAA Annex V). We are working to fix this.
- Media that plays automatically with sound (WCAG 1.4.2). We are working to fix this.
- Accessibility overlay widget detected (WCAG n/a (legal risk)). 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-11-02 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.