REAL SAMPLE REPORT — LIVE CHECK, NOVEMBER 15, 2026

ADA Site Check™ · Accessibility Audit Report · Real Sample

Real Sample Report: skillquesters.com home page, November 15, 2026

Page checked: https://skillquesters.com/ (home page; 304,739 bytes of HTML as delivered on November 15, 2026) — our own site, checked with the same automated pass we sell, with the real counts published below.
Product: ADA Site Check full dated report ($15 one-time) · Method: automated checks of the page’s HTML and CSS against WCAG 2.2 A/AA success criteria: image text alternatives, form labels, page language, heading structure, skip link, link purpose, and contrast ratios computed from the site’s own stylesheet colors. Every number below was counted from the page on the date above.

Result at a glance (real numbers)

CheckMeasured resultVerdict
Images — text alternatives119 images: 119 with alt text, 0 missing the alt attribute, 0 with empty altPass
Page language<html lang="en-US"> declaredPass
Title & meta descriptionTitle present (63 characters); meta description present (124 characters)Pass
Skip linkPresent: “Skip to content” linking to #mainPass
Link purpose313 links; 0 with generic text (“click here”, “read more”, “more”)Pass
Heading structure2 × H1, 16 × H2, 215 × H3; one skipped level (H1 → H3)2 findings
Form labels2 forms, 5 fields; 0 <label for> elements; 2 fields with aria-label; 2 fields relying on placeholder text only1 finding
Contrast (from the site’s CSS)Body text 11.44:1; muted gray #718096 only 3.83:1 on the page background1 finding

Four real findings on our own home page — listed in detail below with the WCAG rule and the fix for each. The checks that passed are listed with their counts after the findings.

Findings in detail REAL

1. Two form fields rely on placeholder text as their only label • Serious

Where: Home page message form — the “Name (optional)” field and the “Your message to the future” textarea. The page contains no <label for> elements at all; these two fields have neither a label nor an aria-label, only a placeholder.
WCAG rule: 1.3.1 Info and Relationships (Level A) and 3.3.2 Labels or Instructions (Level A).
What it means: A placeholder disappears as soon as a customer starts typing, and assistive technology cannot rely on it as the field’s name. A screen-reader user tabbing into these fields may hear only “edit text” with no purpose.
Fix: Give both fields a persistent visible <label> tied with for/id (or an aria-label), keeping the placeholder as a hint.

2. The palette’s muted gray fails contrast for normal text • Serious

Where: Site-wide — the muted-text gray in the site’s own CSS palette, #718096, measures 3.83:1 against the page background #F7FAFC and 4.02:1 against white.
WCAG rule: 1.4.3 Contrast (Minimum) (Level AA) — normal text needs at least 4.5:1.
What it means: Small muted text (dates, captions, secondary notes) set in this gray is hard to read for customers with low vision. It passes the 3:1 minimum for large text only.
Fix: Darken the muted gray until it reaches 4.5:1 on both backgrounds (the palette’s secondary gray #4A5568 already measures 7.18:1), or reserve #718096 for large text and decorative elements.

3. The page has two H1 headings • Moderate

Where: Home page — the heading outline contains 2 H1 elements, 16 H2 and 215 H3.
WCAG rule: 1.3.1 Info and Relationships (Level A) — heading structure should describe the page outline.
What it means: Headings are the table of contents for assistive technology. Two competing top-level headings make the page outline ambiguous about what the page’s single main topic is.
Fix: Keep one H1 for the page’s main topic and demote the second H1 to H2.

4. A heading level is skipped once • Moderate

Where: Home page — directly after the first H1, the outline jumps to an H3 with no H2 in between (one occurrence in the measured outline).
WCAG rule: 1.3.1 Info and Relationships (Level A).
What it means: A skipped level makes the structure sound broken to a screen-reader user navigating by headings — as if a section were missing.
Fix: Change that H3 to an H2, or place it under an existing H2 section.

Checks that passed — with the measured numbers

Honest limits — printed in every report

Automated scans detect roughly 30–40% of accessibility issues; some barriers can only be found by a person using assistive technology. This report is a first-line automated check and a dated record of your good-faith effort — it is not a certification of compliance with the ADA, WCAG, or Section 508, and no scan can guarantee that a website is barrier-free or lawsuit-proof. What it does give you: the exact barriers an automated check can find, ranked, with fixes your developer can apply right away.

Get your own dated report — $15 →

REAL SAMPLE — every count above was measured from the live skillquesters.com home page on November 15, 2026. Your report is generated from your real website the same way and delivered by email as a dated PDF.