Accessibility Report
📄 Static HTML scan (heuristic)
Score history: 76 → 64 across 12 scanssince last scan: 1 new
SAMPLE REPORT

Our own site’s real report, with the details blurred

This is the full report a customer gets, run on vitalybook.com by the same engine: score, WCAG conformance matrix, the laws that apply, and a prioritised fix plan. The element-level details (affected selectors, page snippets and copy-paste fixes) are blurred until you confirm an email address you can open.

We check that the address can receive mail before anything is sent; temporary inboxes are refused. You get one email with your link. No account, no subscription unless you tick the box.

Web Accessibility Conformance Audit
Report IDCA-••••••••
Report date2026-10-14
Site auditedvitalybook.com
Standard testedWCAG 2.1 Level AA (W3C)
ScopePrimary page (homepage) of the domain, automated evaluation
Methodologystatic HTML heuristic scan + browser-rendered deep scan. Automated tooling can verify only a subset of WCAG success criteria; criteria that require human judgement are explicitly marked Not Tested (manual review needed) rather than assumed to pass.
Prepared byWideramp — automated accessibility audit engine

This is an automated conformance audit, not a legal certification of compliance. Full WCAG conformance can only be established by a qualified manual audit. Wideramp reports what was measured — no theater.

SECTION 2

Executive summary

64/ 100At riskWeighted score
1 serious4 moderate5findingsFindings by severity
18
criteria pass
4
criteria fail
28
not tested
5
total findings

Conformance of tested criteria: 81% (18 of 22 machine-tested criteria pass; 28 of 50 total criteria require manual review and are excluded from this figure).

How this score was computed

The weighted score reflects automated findings penalised by severity (critical > serious > moderate > minor). The conformance percentage is the share of machine-tested WCAG 2.1 A/AA criteria that pass — criteria we could not test by machine are reported separately as Not Tested and are never silently counted as passing. This is a deliberate departure from overlay-vendor "compliance %" figures, which do not disclose what was actually measured.

Scanned 2026-10-14T05:27:30.344545Z (cached) · static HTML + deep scan of the homepage

SECTION 6 · CHART

Pass rate by WCAG principle (POUR)

POUR

Each axis shows the share of machine-tested criteria that pass within that principle. Perceivable · Operable · Understandable · Robust. A short axis flags where the site is weakest.

SECTION 3

WCAG 2.1 Level AA conformance matrix

Every WCAG 2.1 Level A and AA success criterion is enumerated below and marked Pass, Fail, or Not Tested (manual review needed). Unlike overlay-vendor reports, we do not hide untested criteria or count them as passing. A browser-rendered deep scan was run, extending machine coverage to contrast, ARIA and keyboard criteria. WCAG Level AAA criteria are out of scope for AA conformance and are not tested.

50 criteria (A+AA)22 machine-tested18 pass4 fail28 not tested

Perceivable

SCSuccess criterionStatus
1.1.1Non-text Content APassvia deep scan
1.2.1Audio-only and Video-only (Prerecorded) ANot Testedmanual review needed
1.2.2Captions (Prerecorded) ANot Testedmanual review needed
1.2.3Audio Description or Media Alternative (Prerecorded) ANot Testedmanual review needed
1.2.4Captions (Live) AANot Testedmanual review needed
1.2.5Audio Description (Prerecorded) AANot Testedmanual review needed
1.3.1Info and Relationships AFailvia deep scan
1.3.2Meaningful Sequence ANot Testedmanual review needed
1.3.3Sensory Characteristics ANot Testedmanual review needed
1.3.4Orientation AANot Testedmanual review needed
1.3.5Identify Input Purpose AANot Testedmanual review needed
1.4.1Use of Color APassvia deep scan
1.4.2Audio Control ANot Testedmanual review needed
1.4.3Contrast (Minimum) AAFailvia deep scan
1.4.4Resize Text AAPassvia deep scan
1.4.5Images of Text AANot Testedmanual review needed
1.4.10Reflow AAPassvia deep scan
1.4.11Non-text Contrast AAPassvia deep scan
1.4.12Text Spacing AAPassvia deep scan
1.4.13Content on Hover or Focus AANot Testedmanual review needed

Operable

SCSuccess criterionStatus
2.1.1Keyboard APassvia deep scan
2.1.2No Keyboard Trap APassvia deep scan
2.1.4Character Key Shortcuts ANot Testedmanual review needed
2.2.1Timing Adjustable ANot Testedmanual review needed
2.2.2Pause, Stop, Hide ANot Testedmanual review needed
2.3.1Three Flashes or Below Threshold ANot Testedmanual review needed
2.4.1Bypass Blocks APassvia deep scan
2.4.2Page Titled APassvia deep scan
2.4.3Focus Order ANot Testedmanual review needed
2.4.4Link Purpose (In Context) APassvia deep scan
2.4.5Multiple Ways AANot Testedmanual review needed
2.4.6Headings and Labels AAPassvia deep scan
2.4.7Focus Visible AAPassvia deep scan
2.5.1Pointer Gestures ANot Testedmanual review needed
2.5.2Pointer Cancellation ANot Testedmanual review needed
2.5.3Label in Name AFailvia static HTML scan
2.5.4Motion Actuation ANot Testedmanual review needed

Understandable

SCSuccess criterionStatus
3.1.1Language of Page APassvia deep scan
3.1.2Language of Parts AAPassvia deep scan
3.2.1On Focus ANot Testedmanual review needed
3.2.2On Input ANot Testedmanual review needed
3.2.3Consistent Navigation AANot Testedmanual review needed
3.2.4Consistent Identification AANot Testedmanual review needed
3.3.1Error Identification ANot Testedmanual review needed
3.3.2Labels or Instructions AFailvia static HTML scan
3.3.3Error Suggestion AANot Testedmanual review needed
3.3.4Error Prevention (Legal, Financial, Data) AANot Testedmanual review needed

Robust

SCSuccess criterionStatus
4.1.1Parsing APassvia deep scan
4.1.2Name, Role, Value APassvia deep scan
4.1.3Status Messages AAPassvia deep scan
SECTION 5

Severity-prioritized remediation plan

Ordered by severity, then by how commonly each issue appears across sites we scan, then by local occurrences. Each item lists the affected elements, a copy-paste fix and an effort estimate. Fixing the top 3 issues resolves 86% of all detected occurrences.

1seriousText color contrast meets minimum ratioWCAG 1.4.3 Level AAModerate· 25 occurrences Real-world prevalence: seen on 40% of sites scanned · 75 occurrences observed
Fix: Compute the contrast ratio from rendered/computed foreground and background colors and raise it to ≥4.5:1 (3:1 for large text). Requires resolving CSS cascade + computed styles, so a headless browser is needed.
Affected elements:
Element details are hidden in this sample.Blurred in this sample · unlock with your email
Code fix hidden in this sample.
2seriousForm fields without labelsWCAG 3.3.2Moderate· 1 occurrence Real-world prevalence: seen on 40% of sites scanned · 10 occurrences observed
Fix: Associate every input with a <label for>, or add aria-label/aria-labelledby.
Affected elements:
Element details are hidden in this sample.Blurred in this sample · unlock with your email
Code fix hidden in this sample.
3seriousInteractive targets are large enoughWCAG 2.5.8 Level AAModerate· 20 occurrences
Fix: Increase the rendered hit area to ≥24×24px (48×48 recommended) or add spacing.
Affected elements:
Element details are hidden in this sample.Blurred in this sample · unlock with your email
Code fix hidden in this sample.
4moderateHeading levels skipWCAG 1.3.1 Level AModerate· 5 occurrences Real-world prevalence: seen on 40% of sites scanned · 8 occurrences observed
Fix: Use heading levels sequentially.
Affected elements:
Element details are hidden in this sample.Blurred in this sample · unlock with your email
Code fix hidden in this sample.
5moderateFocused elements may be obscured by sticky/fixed elementsWCAG 2.4.11Moderate· 1 occurrence
Fix: Ensure focused elements are not hidden behind sticky or fixed positioned elements. Use scroll-margin-top or scroll-padding-top to offset scroll position.
Code fix hidden in this sample.
6moderateAccessible name does not contain visible label textWCAG 2.5.3Moderate· 1 occurrence
Fix: Ensure the aria-label contains the visible text as a substring. Prefer aria-labelledby or descriptive visible text instead.
Affected elements:
Element details are hidden in this sample.Blurred in this sample · unlock with your email
Code fix hidden in this sample.
DEEP SCAN · BROWSER RENDER

Browser-rendered accessibility scan

Run with the industry-standard open-source accessibility ruleset (via a headless-browser render of the page, ~50+ automated WCAG 2.1/2.2 checks). This detects barriers the static scan cannot: color contrast (1.4.3), ARIA validity (4.1.2/4.1.3), keyboard operability (2.1.1) and target size (2.5.8). Accessibility score: 91/100. Source: browser render · 2026-06-15T19:35:11.447897Z.

DETECTED

color-contrast

seriousWCAG 1.4.3 Level AA

Normal text needs at least 4.5:1 contrast against its background; large text (≥24px, or ≥19px bold) needs 3:1.

25 occurrences detected.

Affected elements (CSS selector):
Element details are hidden in this sample.Blurred in this sample · unlock with your email
How to fix: Compute the contrast ratio from rendered/computed foreground and background colors and raise it to ≥4.5:1 (3:1 for large text). Requires resolving CSS cascade + computed styles, so a headless browser is needed.
DETECTED

target-size

seriousWCAG 2.5.8 Level AA

Clickable/tappable controls should be at least 24×24 CSS pixels (with spacing exceptions).

20 occurrences detected.

Affected elements (CSS selector):
Element details are hidden in this sample.Blurred in this sample · unlock with your email
How to fix: Increase the rendered hit area to ≥24×24px (48×48 recommended) or add spacing.
DETECTED

Heading levels skip

moderateWCAG 1.3.1 Level A

Headings go in order (h1 → h2 → h3) without jumping levels.

5 occurrences detected.

Affected elements (CSS selector):
Element details are hidden in this sample.Blurred in this sample · unlock with your email
How to fix: Use heading levels sequentially.

Performance & Core Web Vitals

25
Performance score
85
SEO score
73
Best practices

Detailed results by WCAG principle

Each automated check below is grouped under one of the four WCAG 2.1 principles. Passing checks are shown alongside failures for full transparency.

P

Perceivable

Information and UI must be presentable in ways users can perceive.

PASS

Images have alt text

WCAG 1.1.1

No issues found for this check.

PASS

Responsive viewport is set

WCAG 1.4.10

No issues found for this check.

PASS

Pinch-zoom is allowed

WCAG 1.4.4

No issues found for this check.

O

Operable

UI components and navigation must be operable.

PASS

Page has a descriptive title

WCAG 2.4.2

No issues found for this check.

PASS

Title length is reasonable

WCAG 2.4.2

No issues found for this check.

PASS

Page has one H1

WCAG 2.4.6

No issues found for this check.

PASS

No duplicate H1s

WCAG 1.3.1

No issues found for this check.

FAIL

Heading levels skip

moderateWCAG 1.3.1Real-world prevalence: seen on 40% of sites scanned · 6 occurrences observed

Skipped heading levels break the logical document outline for screen readers.

2 occurrences detected.

Sampled from the page:
Element details are hidden in this sample.Blurred in this sample · unlock with your email
How to fix: Use heading levels in order (h1 → h2 → h3) without skipping.
Code fix hidden in this sample.
PASS

Links have readable text

WCAG 2.4.4

No issues found for this check.

FAIL

Focused elements may be obscured by sticky/fixed elements

moderateWCAG 2.4.11

Sticky headers or fixed footers can cover a keyboard-focused element, making it impossible for keyboard-only users to see what they are interacting with.

1 occurrence detected.

How to fix: Ensure focused elements are not hidden behind sticky or fixed positioned elements. Use scroll-margin-top or scroll-padding-top to offset scroll position.
Code fix hidden in this sample.
FAIL

Accessible name does not contain visible label text

moderateWCAG 2.5.3

When aria-label differs from visible button/link text, voice-control users cannot activate the element by speaking the text they see on screen.

1 occurrence detected.

Sampled from the page:
Element details are hidden in this sample.Blurred in this sample · unlock with your email
How to fix: Ensure the aria-label contains the visible text as a substring. Prefer aria-labelledby or descriptive visible text instead.
Code fix hidden in this sample.
PASS

Interactive elements meet minimum target size (2.5.8)

WCAG 2.5.8

No issues found for this check.

PASS

No positive tabindex values breaking focus order (2.4.3)

WCAG 2.4.3

No issues found for this check.

U

Understandable

Information and the operation of the UI must be understandable.

PASS

Page language is declared

WCAG 3.1.1

No issues found for this check.

PASS

Language value is valid

WCAG 3.1.1

No issues found for this check.

FAIL

Form fields without labels

seriousWCAG 3.3.2Real-world prevalence: seen on 40% of sites scanned · 10 occurrences observed

Users cannot tell what to enter in unlabeled inputs.

1 occurrence detected.

Sampled from the page:
Element details are hidden in this sample.Blurred in this sample · unlock with your email
How to fix: Associate every input with a <label for>, or add aria-label/aria-labelledby.
Code fix hidden in this sample.
PASS

Help/contact link present for consistent help (3.2.6)

WCAG 3.2.6

No issues found for this check.

R

Robust

Content must be robust enough to work with assistive technologies.

PASS

Character encoding is declared

WCAG 4.1.1

No issues found for this check.

PASS

Buttons have accessible names

WCAG 4.1.2

No issues found for this check.

PASS

No duplicate id attributes

WCAG 4.1.1

No issues found for this check.

European Accessibility Act (EAA) Readiness

The EAA became enforceable June 2025. Websites of businesses operating in the EU must comply with WCAG 2.1 AA minimum. This applies to any business offering digital products or services to EU customers — not just EU-headquartered companies.

Needs fixes before EAA compliance: 64/100

Your score: 64/100 — Significant accessibility barriers were detected. Address the issues in the remediation plan above before the EAA enforcement deadline.

Based on automated WCAG 2.1 AA checks. Manual testing with assistive technology is also required for full EAA compliance. Learn more about EAA →

Manual review recommended

Wideramp scans static HTML, so it reports only what can be verified honestly from markup. The following require a human or a browser-rendered audit and are not reflected in the score above:

Export this report

Pro reports can be saved and shared.

Unlock to download PDF or HTMLRe-scan · available in ~23h
SECTION 7

Methodology & formal disclaimer

This report combines a static-HTML heuristic scan (20 checks on the server-fetched homepage) with a browser-rendered deep scan using an open-source accessibility ruleset, extending machine coverage to contrast, ARIA and keyboard criteria. Findings are mapped to WCAG 2.1 Level AA success criteria and organised by the four POUR principles. The weighted score is penalised by issue severity.

Automated-testing limitations: automated tooling can reliably detect only a subset of WCAG success criteria. Criteria requiring human judgement (alt-text quality, meaningful sequence, captions accuracy, link purpose in context, and others) are reported as Not Tested (manual review needed) in the conformance matrix and are never assumed to pass.

This is an automated audit, not a legal certification. A passing automated result does not by itself establish WCAG conformance or legal compliance; a qualified manual audit is recommended for full conformance. Wideramp reports only what was measured — real accessibility, no theater.

Report ID: CA-••••••••Generated: 2026-10-14T05:27:30.344545ZStandard: WCAG 2.1 Level AAPrepared by Wideramp

Reference: WCAG 2.1 Quick Reference (W3C) · Level AA.

Powered by Wideramp intelligence: a curated knowledge base of 31 accessibility checks and 4 accessibility laws. Real-world prevalence figures are derived from 5 sites scanned so far.