Accessibility Report
📄 Static HTML scan (heuristic)
Web Accessibility Conformance Audit
Report IDCA-20260818-9C03D89D
Report date2026-08-18
Site auditedflipbook.clovitek.com
Standard testedWCAG 2.1 Level AA (W3C)
ScopePrimary page (homepage) of the domain, automated evaluation
Methodologystatic HTML heuristic 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 byCloviAble — 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

34/ 100At riskWeighted score
5 serious1 moderate6findingsFindings by severity
8
criteria pass
3
criteria fail
39
not tested
6
total findings

Conformance of tested criteria: 72% (8 of 11 machine-tested criteria pass; 39 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-08-18T16:11:02.722047Z · static HTML analysis 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. No browser-rendered deep scan was available for this domain, so contrast, keyboard and focus criteria are reported as Not Tested. Run a deep scan for fuller machine coverage. WCAG Level AAA criteria are out of scope for AA conformance and are not tested.

50 criteria (A+AA)11 machine-tested8 pass3 fail39 not tested

Perceivable

SCSuccess criterionStatus
1.1.1Non-text Content APassvia static HTML 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 static HTML 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 ANot Testedmanual review needed
1.4.2Audio Control ANot Testedmanual review needed
1.4.3Contrast (Minimum) AANot Testedmanual review needed
1.4.4Resize Text AAPassvia static HTML scan
1.4.5Images of Text AANot Testedmanual review needed
1.4.10Reflow AAPassvia static HTML scan
1.4.11Non-text Contrast AANot Testedmanual review needed
1.4.12Text Spacing AANot Testedmanual review needed
1.4.13Content on Hover or Focus AANot Testedmanual review needed

Operable

SCSuccess criterionStatus
2.1.1Keyboard ANot Testedmanual review needed
2.1.2No Keyboard Trap ANot Testedmanual review needed
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 ANot Testedmanual review needed
2.4.2Page Titled APassvia static HTML scan
2.4.3Focus Order ANot Testedmanual review needed
2.4.4Link Purpose (In Context) AFailvia static HTML scan
2.4.5Multiple Ways AANot Testedmanual review needed
2.4.6Headings and Labels AAPassvia static HTML scan
2.4.7Focus Visible AANot Testedmanual review needed
2.5.1Pointer Gestures ANot Testedmanual review needed
2.5.2Pointer Cancellation ANot Testedmanual review needed
2.5.3Label in Name ANot Testedmanual review needed
2.5.4Motion Actuation ANot Testedmanual review needed

Understandable

SCSuccess criterionStatus
3.1.1Language of Page APassvia static HTML scan
3.1.2Language of Parts AANot Testedmanual review needed
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 APassvia 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 static HTML scan
4.1.2Name, Role, Value AFailvia static HTML scan
4.1.3Status Messages AANot Testedmanual review needed
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 100% of all detected occurrences.

1seriousButtons with no accessible nameWCAG 4.1.2Moderate· 2 occurrences Real-world prevalence: seen on 60% of sites scanned · 5 occurrences observed
Fix: Add visible text or an aria-label to every <button>.
Affected elements:
<button @click="open=!open" class="md:hidden p-2 text-gray-700">
<button @click="annual=!annual" class="relative w-14 h-7 rounded-full bg-brand transition-colors">
<button aria-label="Close dialog">×</button>
2seriousLinks with no readable textWCAG 2.4.4Moderate· 3 occurrences
Fix: Provide visible link text, or an aria-label / alt text on an inner image.
Affected elements:
<a href="#" class="w-9 h-9 rounded-lg bg-white/5 hover:bg-brand flex items-center justify-center transition-colors">
<a href="#" class="w-9 h-9 rounded-lg bg-white/5 hover:bg-brand flex items-center justify-center transition-colors">
<a href="#" class="w-9 h-9 rounded-lg bg-white/5 hover:bg-brand flex items-center justify-center transition-colors">
<a href="/cart" aria-label="View cart">
  <svg aria-hidden="true">…</svg>
</a>
3moderateHeading levels skipWCAG 1.3.1Moderate· 1 occurrence Real-world prevalence: seen on 40% of sites scanned · 8 occurrences observed
Fix: Use heading levels in order (h1 → h2 → h3) without skipping.
Affected elements:
h2→h4
<h2>Section</h2>
  <h3>Sub-section</h3>  <!-- not <h4> -->

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.

1 occurrence detected.

Sampled from the page:
h2→h4
How to fix: Use heading levels in order (h1 → h2 → h3) without skipping.
<h2>Section</h2>
  <h3>Sub-section</h3>  <!-- not <h4> -->
FAIL

Links with no readable text

seriousWCAG 2.4.4

Icon-only or empty links are announced as just "link", giving no destination context.

3 occurrences detected.

Sampled from the page:
<a href="#" class="w-9 h-9 rounded-lg bg-white/5 hover:bg-brand flex items-center justify-center transition-colors">
<a href="#" class="w-9 h-9 rounded-lg bg-white/5 hover:bg-brand flex items-center justify-center transition-colors">
<a href="#" class="w-9 h-9 rounded-lg bg-white/5 hover:bg-brand flex items-center justify-center transition-colors">
How to fix: Provide visible link text, or an aria-label / alt text on an inner image.
<a href="/cart" aria-label="View cart">
  <svg aria-hidden="true">…</svg>
</a>
PASS

Focused elements not obscured by sticky elements (2.4.11)

WCAG 2.4.11

No issues found for this check.

PASS

Accessible name contains visible text (2.5.3)

WCAG 2.5.3

No issues found for this check.

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.

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.

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.

FAIL

Buttons with no accessible name

seriousWCAG 4.1.2Real-world prevalence: seen on 60% of sites scanned · 5 occurrences observed

A button with no text or label is announced only as "button", with no purpose.

2 occurrences detected.

Sampled from the page:
<button @click="open=!open" class="md:hidden p-2 text-gray-700">
<button @click="annual=!annual" class="relative w-14 h-7 rounded-full bg-brand transition-colors">
How to fix: Add visible text or an aria-label to every <button>.
<button aria-label="Close dialog">×</button>
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.

Significant accessibility work needed: 34/100

Your score: 34/100 — Multiple serious barriers detected. Full remediation and a qualified manual audit are required to meet EAA requirements.

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:

🛡️ 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.

SECTION 7

Methodology & formal disclaimer

This report combines a static-HTML heuristic scan (20 checks on the server-fetched homepage) (no browser-rendered deep scan was available for this domain). 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-20260818-9C03D89DGenerated: 2026-08-18T16:11:02.722047ZStandard: 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.