Accessibility Report — vitalybook.com

CloviAbleAccessibility Report

📄 Static HTML scan (heuristic)

Score history: 0 → 76 across 9 scans

CloviAble

Web Accessibility Conformance Audit

Report IDCA-20260905-17FBDDB1

Report date2026-09-05

Site audited	vitalybook.com
Standard tested	WCAG 2.1 Level AA (W3C)
Scope	Primary page (homepage) of the domain, automated evaluation
Methodology	static HTML heuristic scan + browser-rendered deep scan (axe-core via Lighthouse). 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 by	CloviAble — 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. CloviAble reports what was measured — no theater.

SECTION 2

Executive summary

Needs workWeighted score

Findings by severity

criteria pass

criteria fail

not tested

total findings

Conformance of tested criteria: 86% (19 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-09-05T21:09:18.194866Z (cached) · static HTML + deep scan of the homepage

SECTION 6 · CHART

Pass rate by WCAG principle (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 (axe-core) 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-tested19 pass3 fail28 not tested

Perceivable

SC	Success criterion	Status
1.1.1	Non-text Content A	Passvia deep scan (axe-core)
1.2.1	Audio-only and Video-only (Prerecorded) A	Not Testedmanual review needed
1.2.2	Captions (Prerecorded) A	Not Testedmanual review needed
1.2.3	Audio Description or Media Alternative (Prerecorded) A	Not Testedmanual review needed
1.2.4	Captions (Live) AA	Not Testedmanual review needed
1.2.5	Audio Description (Prerecorded) AA	Not Testedmanual review needed
1.3.1	Info and Relationships A	Failvia deep scan (axe-core)
1.3.2	Meaningful Sequence A	Not Testedmanual review needed
1.3.3	Sensory Characteristics A	Not Testedmanual review needed
1.3.4	Orientation AA	Not Testedmanual review needed
1.3.5	Identify Input Purpose AA	Not Testedmanual review needed
1.4.1	Use of Color A	Passvia deep scan (axe-core)
1.4.2	Audio Control A	Not Testedmanual review needed
1.4.3	Contrast (Minimum) AA	Failvia deep scan (axe-core)
1.4.4	Resize Text AA	Passvia deep scan (axe-core)
1.4.5	Images of Text AA	Not Testedmanual review needed
1.4.10	Reflow AA	Passvia deep scan (axe-core)
1.4.11	Non-text Contrast AA	Passvia deep scan (axe-core)
1.4.12	Text Spacing AA	Passvia deep scan (axe-core)
1.4.13	Content on Hover or Focus AA	Not Testedmanual review needed

Operable

SC	Success criterion	Status
2.1.1	Keyboard A	Passvia deep scan (axe-core)
2.1.2	No Keyboard Trap A	Passvia deep scan (axe-core)
2.1.4	Character Key Shortcuts A	Not Testedmanual review needed
2.2.1	Timing Adjustable A	Not Testedmanual review needed
2.2.2	Pause, Stop, Hide A	Not Testedmanual review needed
2.3.1	Three Flashes or Below Threshold A	Not Testedmanual review needed
2.4.1	Bypass Blocks A	Passvia deep scan (axe-core)
2.4.2	Page Titled A	Passvia deep scan (axe-core)
2.4.3	Focus Order A	Not Testedmanual review needed
2.4.4	Link Purpose (In Context) A	Passvia deep scan (axe-core)
2.4.5	Multiple Ways AA	Not Testedmanual review needed
2.4.6	Headings and Labels AA	Passvia deep scan (axe-core)
2.4.7	Focus Visible AA	Passvia deep scan (axe-core)
2.5.1	Pointer Gestures A	Not Testedmanual review needed
2.5.2	Pointer Cancellation A	Not Testedmanual review needed
2.5.3	Label in Name A	Failvia static HTML scan
2.5.4	Motion Actuation A	Not Testedmanual review needed

Understandable

SC	Success criterion	Status
3.1.1	Language of Page A	Passvia deep scan (axe-core)
3.1.2	Language of Parts AA	Passvia deep scan (axe-core)
3.2.1	On Focus A	Not Testedmanual review needed
3.2.2	On Input A	Not Testedmanual review needed
3.2.3	Consistent Navigation AA	Not Testedmanual review needed
3.2.4	Consistent Identification AA	Not Testedmanual review needed
3.3.1	Error Identification A	Not Testedmanual review needed
3.3.2	Labels or Instructions A	Passvia deep scan (axe-core)
3.3.3	Error Suggestion AA	Not Testedmanual review needed
3.3.4	Error Prevention (Legal, Financial, Data) AA	Not Testedmanual review needed

Robust

SC	Success criterion	Status
4.1.1	Parsing A	Passvia deep scan (axe-core)
4.1.2	Name, Role, Value A	Passvia deep scan (axe-core)
4.1.3	Status Messages AA	Passvia deep scan (axe-core)

SECTION 4

Legal & litigation-exposure overview

High riskMultiple Level AA failures detected, including high-litigation-risk barriers.

Law	Applies to	Standard	Key dates	Your status
ADA Title II — Web & Mobile Accessibility Rule United States	State and local government entities (public entities): cities, counties, public universities, courts, transit, public schools, libraries, and their contractors/online services.	WCAG 2.1 AA	rule published: 2024-04-24; compliance large entities: 2026-04-24 (public entities with population ≥ 50,000); compliance small entities: 2027-04-26 (public entities with population < 50,000, and special district governments)	At risk
Section 508 of the Rehabilitation Act United States (federal)	U.S. federal agencies and vendors selling ICT (information and communication technology) to the federal government. Drives demand for VPAT/ACR documents.	WCAG 2.0 AA (via Revised 508 Standards / harmonized with EN 301 549)	revised standards effective: 2018-01-18	At risk
European Accessibility Act (EAA) / EN 301 549 European Union	Private-sector products and services sold in the EU: e-commerce, banking, e-books, ticketing, transport, telecoms, computers, smartphones, ATMs/terminals. Microenterprises (<10 staff and ≤€2M turnover) providing services are largely exempt.	EN 301 549 → WCAG 2.1 AA	directive adopted: 2019-04-17; member state transposition: 2022-06-28; enforcement begins: 2025-06-28; transition for certain service contracts: 2030-06-28	At risk
Accessibility for Ontarians with Disabilities Act (AODA) — IASR Information & Communications Standard Ontario, Canada	Ontario public-sector organizations and private/non-profit organizations with 50+ employees. (Smaller orgs have reduced obligations.)	WCAG 2.0 AA	wcag 2 0 aa deadline: 2021-01-01 (all applicable internet websites and web content); compliance reporting: ongoing periodic accessibility compliance reports to the Ontario government	At risk

Failing criteria that map to these legal requirements: 1.3.1 Info and Relationships, 1.4.3 Contrast (Minimum), 2.5.3 Label in Name.

What this means for you: the failing criteria above are the same barriers cited in accessibility demand letters and regulatory actions. We map your measured failures to the laws that may apply — we do not claim compliance or grant safe harbor. Only a qualified audit plus remediation can establish legal compliance.

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 96% 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:

div.vc_column-inner > div.wpb_wrapper > a.nectar-button > span

div.vc_col-sm-12 > div.vc_column-inner > div.wpb_wrapper > h1.vc_custom_heading

div.vc_column-inner > div.wpb_wrapper > div.nectar-highlighted-text > h2

div.col > div.post-header > span.meta-category > a.identity-belonging-memoirs-stories

div.col > div.post-header > span.meta-category > a.poems-trauma-identity

div.col > div.post-header > span.meta-category > a.mental-strength-emotional-fitness

/* fail: #999 on #fff = 2.85:1 */
color:#595959; /* pass: 7:1 on #fff */

2seriousInteractive 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:

div.col > div.post-header > span.meta-category > a.identity-belonging-memoirs-stories

div.col > div.post-header > span.meta-category > a.poems-trauma-identity

div.col > div.post-header > span.meta-category > a.mental-strength-emotional-fitness

div.col > div.post-header > span.meta-category > a.healing-recipes-ukrainian-food

div.menu-category-menu-container > ul#menu-category-menu > li#menu-item-12290 > a

div.menu-category-menu-container > ul#menu-category-menu > li#menu-item-12291 > a

.icon-btn{ min-width:24px; min-height:24px; padding:8px; }

3moderateHeading 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:

div.wpb_wrapper > div.wpb_text_column > div.wpb_wrapper > h5

div.wpb_wrapper > div.nectar-fancy-box > div.inner > h4

div.row > div.col > div.post-header > h5

div.vc_column-inner > div.wpb_wrapper > div.nectar-cta > h6

<h2>Section</h2>
  <h3>Sub-section</h3>  <!-- not <h4> -->

4moderateFocused 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.

/* CSS */
:target, :focus { scroll-margin-top: 80px; /* height of sticky header */ }

5moderateAccessible 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:

<button class="smodal-close" id="smodalClose" aria-label="Close">

<!-- Wrong: -->
<button aria-label="Submit form">Send</button>
<!-- Right: -->
<button aria-label="Send message">Send</button>

DEEP SCAN · AXE-CORE

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: lighthouse · 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):

div.vc_column-inner > div.wpb_wrapper > a.nectar-button > span

div.vc_col-sm-12 > div.vc_column-inner > div.wpb_wrapper > h1.vc_custom_heading

div.vc_column-inner > div.wpb_wrapper > div.nectar-highlighted-text > h2

div.col > div.post-header > span.meta-category > a.identity-belonging-memoirs-stories

div.col > div.post-header > span.meta-category > a.poems-trauma-identity

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):

div.col > div.post-header > span.meta-category > a.identity-belonging-memoirs-stories

div.col > div.post-header > span.meta-category > a.poems-trauma-identity

div.col > div.post-header > span.meta-category > a.mental-strength-emotional-fitness

div.col > div.post-header > span.meta-category > a.healing-recipes-ukrainian-food

div.menu-category-menu-container > ul#menu-category-menu > li#menu-item-12290 > a

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):

div.wpb_wrapper > div.wpb_text_column > div.wpb_wrapper > h5

div.wpb_wrapper > div.nectar-fancy-box > div.inner > h4

div.row > div.col > div.post-header > h5

div.vc_column-inner > div.wpb_wrapper > div.nectar-cta > h6

How to fix: Use heading levels sequentially.

Performance & Core Web Vitals

Performance score

SEO score

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.

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.

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:

h2→h4

h2→h4

How to fix: Use heading levels in order (h1 → h2 → h3) without skipping.

<h2>Section</h2>
  <h3>Sub-section</h3>  <!-- not <h4> -->

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.

/* CSS */
:target, :focus { scroll-margin-top: 80px; /* height of sticky header */ }

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:

<button class="smodal-close" id="smodalClose" aria-label="Close">

How to fix: Ensure the aria-label contains the visible text as a substring. Prefer aria-labelledby or descriptive visible text instead.

<!-- Wrong: -->
<button aria-label="Submit form">Send</button>
<!-- Right: -->
<button aria-label="Send message">Send</button>

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.

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.

PASS

Form fields are labelled

WCAG 3.3.2

No issues found for this check.

PASS

Help/contact link present for consistent help (3.2.6)

WCAG 3.2.6

No issues found for this check.

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: 76/100

Your score: 76/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

CloviAble 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:

Color-contrast ratios — Computing text/background contrast needs rendered, computed CSS colors — not available from raw HTML.
Keyboard tab order & operability — Whether every control is reachable and in a logical order requires actually tabbing through the live page.
Visible focus indicators — Focus styling is defined in CSS and only observable when an element is focused in a browser.
Dynamic ARIA states — aria-expanded, aria-pressed, live-region updates etc. change at runtime via JavaScript.
Screen-reader announcement quality — How content is actually announced depends on the AT + browser pairing and must be tested manually.
Meaningful reading/DOM order — Whether the visual order matches the DOM order needs a rendered layout to confirm.
Media captions & transcripts — Presence and accuracy of captions for audio/video cannot be judged from markup alone.

🛡️ Also check Security with CloviScan

Accessibility is only half the picture. CloviScan audits SSL, security headers, DNS email auth, and performance — all free, instant, no signup.

Free Security Scan →

Export this report

Pro reports can be saved and shared.

Download PDF Download 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 the axe-core ruleset (via Lighthouse), 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. CloviAble reports only what was measured — real accessibility, no theater.

Report ID: CA-20260905-17FBDDB1Generated: 2026-09-05T21:09:18.194866ZStandard: WCAG 2.1 Level AAPrepared by CloviAble

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

Powered by CloviAble 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.