ProofHive← Run the free accessibility check

A complete example report: www.debian.org

This is a real, unedited report on a public website, produced by running the same scanner you get — every score, finding, piece of evidence and fix below came out of that one scan, unedited and unabridged. Nothing on this page has been chosen for show. Run the same scan again today and a few numbers can shift: pages change, servers answer differently, and a link that worked last week can break. Expect small differences, not a different story.

Site scanned
www.debian.org
https://www.debian.org/
Scanned
25 Sept 2026, 02:01 UTC
one pass, on the live page
This report contains
16 findings
41 of 42 checks ran

No relationship with this site: its owner did not commission this report, is not a customer, and has not endorsed ProofHive. It was chosen as a public example — check the findings yourself with www.debian.org open in another tab.

Re-run this scan live now →Printing this page (Cmd/Ctrl-P) or saving it as a PDF gives you the client-ready document.

Full report

www.debian.org

https://www.debian.org/

64

overall score (needs attention)

Accessibility
64/100
5 finding(s), 15 check(s) ran, 0 skipped
Security headers
64/100
2 finding(s), 8 check(s) ran, 1 skipped
SEO basics
50/100
6 finding(s), 9 check(s) ran, 0 skipped
Speed & weight
58/100
3 finding(s), 7 check(s) ran, 0 skipped
Broken links
100/100
0 finding(s), 1 check(s) ran, 0 skipped
0 critical4 serious4 moderate8 minor16 findings in total

Scanned 25 Sept 2026, 02:01 UTC · 15.5 KB of HTML · 38 ms server response · 10 of 19 same-origin assets weighed

Fix these first

Ordered by severity, then by how much the category weighs in the overall score (accessibility 30%, security 25%, SEO 20%, speed 15%, links 10%), then by how often the problem appears. Your own judgement and your client's priorities come first — this is a starting order, not a rule.

  1. 12 form fields with no label (serious, Accessibility, ×2)Give each field a real <label for="field-id">Field name</label> pointing at its id (or aria-label). A placeholder is not a label — it disappears as soon as someone types, and screen readers announce fields by their label.
  2. 2No <main> landmark on the page (serious, Accessibility)Wrap the page's primary content in <main>. It gives screen-reader and keyboard users a one-step "skip to content" region.
  3. 3No Content-Security-Policy header (serious, Security headers)Add a Content-Security-Policy that limits scripts and frames to sources you trust. It is the main defence against injected or third-party script running on your pages.
  4. 43 images over 200 KB (serious, Speed & weight)Resize each image to the largest size it is displayed at and compress it. Oversized hero images are usually the single biggest cause of a slow mobile page.
  5. 58 ARIA problems found (moderate, Accessibility, ×8)Fix the ARIA values flagged above. Incorrect ARIA is worse than no ARIA: it overrides what the browser works out by itself. Remove any aria-* attribute you are not deliberately using.

Accessibility

5 findings

Markup-level WCAG checks: images, labels, headings, links, ARIA, landmarks.

  • SeriousAccessibility×2 on this page

    2 form fields with no label

    <input name="P" value="" size="14">  |  <select onchange="location = this.value;"> <option value="" disabled selected>Select your language</option> <option value="index.ca.html" title="Catalan" lang=…

    Fix: Give each field a real <label for="field-id">Field name</label> pointing at its id (or aria-label). A placeholder is not a label — it disappears as soon as someone types, and screen readers announce fields by their label.

  • SeriousAccessibility

    No <main> landmark on the page

    Neither <main> nor role="main" appears in the delivered HTML.

    Fix: Wrap the page's primary content in <main>. It gives screen-reader and keyboard users a one-step "skip to content" region.

  • ModerateAccessibility

    1 link with non-descriptive text

    "Download" → https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-13.7.0-amd64-n…

    Fix: Rewrite link text so it says where the link goes ("View our pricing" rather than "click here"). Screen-reader users often jump link to link out of context.

  • ModerateAccessibility×4 on this page

    The page has 4 <h1> headings

    "Debian"  |  "The Community"  |  "The Operating System"  |  "Project News"

    Fix: Keep one <h1> for the page's main heading and demote the others to <h2>. Multiple top-level headings make the page outline ambiguous.

  • ModerateAccessibility×8 on this page

    8 ARIA problems found

    aria-hidden="true" on a focusable <a> — it stays keyboard-reachable while hidden from screen readers; aria-hidden="true" on a focusable <a> — it stays keyboard-reachable while hidden from screen readers; aria-hidden="true" on a focusable <a> — it stays keyboard-reachable while hidden from screen readers; aria-hidden="true" on a focusable <a> — it stays keyboard-reachable while hidden from screen …

    Fix: Fix the ARIA values flagged above. Incorrect ARIA is worse than no ARIA: it overrides what the browser works out by itself. Remove any aria-* attribute you are not deliberately using.

Security headers

2 findings

HTTPS and the response headers browsers use to protect visitors.

  • SeriousSecurity headers

    No Content-Security-Policy header

    The response had no Content-Security-Policy header.

    Fix: Add a Content-Security-Policy that limits scripts and frames to sources you trust. It is the main defence against injected or third-party script running on your pages.

  • MinorSecurity headers

    Strict-Transport-Security does not cover subdomains

    Strict-Transport-Security: max-age=15552000

    Fix: Add includeSubDomains once every subdomain is HTTPS-only, so the protection cannot be bypassed through a subdomain.

SEO basics

6 findings

Title, description, canonical, indexability, robots.txt, sitemap, structured data.

  • MinorSEO basics

    Meta description is long (163 characters) and will be truncated

    "Debian is an operating system and a distribution of Free Software. It is maintained and updated through the work of many users who volunteer their time and eff…"

    Fix: Trim to about 155 characters; search engines cut off anything longer.

  • MinorSEO basics

    No canonical link

    No <link rel="canonical"> was found.

    Fix: Add <link rel="canonical" href="…"> with the one preferred URL for this page, so variants (tracking parameters, http vs https) do not compete in search results.

  • MinorSEO basics

    No Open Graph tags

    None of og:title, og:description, og:image or og:url were found.

    Fix: Add og:title, og:description, og:image (1200×630) and og:url. These control how the page looks when someone shares it in Slack, LinkedIn, WhatsApp or Facebook.

  • MinorSEO basics

    No robots.txt file

    https://…/robots.txt returned HTTP 404.

    Fix: Add a robots.txt at the site root that allows crawling and points at your sitemap (Sitemap: https://example.com/sitemap.xml). It is how you tell crawlers what to do.

  • MinorSEO basics

    No sitemap.xml at the site root

    https://…/sitemap.xml returned HTTP 404.

    Fix: Publish an XML sitemap at /sitemap.xml listing your pages and reference it from robots.txt. It speeds up discovery of new pages by search engines.

  • MinorSEO basics

    No structured data

    No <script type="application/ld+json"> block was found.

    Fix: Add JSON-LD describing the business or page type (Organization, LocalBusiness, Article, Product). It is what search engines use for rich results like ratings, prices and opening hours.

Speed & weight

3 findings

Response time and the measured size of the page and a sample of its assets.

  • SeriousSpeed & weight

    3 images over 200 KB

    debconf26_group_photo.jpg — 370.9 KB; mini-dc26-campinas.jpg — 843.3 KB; calamares-installer.png — 275.5 KB

    Fix: Resize each image to the largest size it is displayed at and compress it. Oversized hero images are usually the single biggest cause of a slow mobile page.

  • ModerateSpeed & weight

    The page's own resources weigh about 1.77 MB

    15.5 KB HTML plus 10 of 19 same-origin resources weighted, from mini-dc26-campinas.jpg 843.3 KB, debconf26_group_photo.jpg 370.9 KB, calamares-installer.png 275.5 KB.

    Fix: Compress images, serve them at the size they are displayed, and split large scripts. Heavy pages load slowly on mobile connections, which is where most of a client's traffic comes from.

  • MinorSpeed & weight

    8 images in a legacy format

    openlogo-50.png, debconf26_group_photo.jpg, mini-dc26-hamburg.jpg, mini-dc26-campinas.jpg

    Fix: Re-export these as WebP or AVIF (typically 25–50% smaller at the same quality). Keep a JPEG/PNG fallback only if you must support very old browsers.

How agencies use this

1. Hand it to the client as a paid extra

Run the check on a client's live page, print it or save it as a PDF — the print view drops the navigation and buttons and puts the audited URL and check date at the top of every page — then send it on. Charge for the audit as its own line on the invoice, or bundle it into a care plan; the price you charge is your call. Nothing here runs on a schedule and there are no change alerts: you start each check yourself, when you want it, and what you get is a snapshot of the page at that moment. Run it again next month and you get a fresh report to compare against.

2. Use it to open the pitch

Send the free scan when you pitch a new site — scores, counts and the first few findings are enough to start a conversation. When the client asks what it would take to fix, order the full document: the priority list is your scope, and the plain-English fixes are the work you (or their developer) will do.

Automation only goes so far, and we say so on every report: colour contrast, keyboard use, screen-reader behaviour and content quality are not tested here. Use the report to find and prioritise work, not to promise a client that a site is WCAG or ADA compliant — it is a readiness audit, not a certification.

How this scan was run

  • • Fetched https://www.debian.org/ — HTTP 200 in 38 ms, 15864 bytes of HTML read.
  • • Checked that www.debian.org resolves to a public address before fetching: 140.211.166.200, 128.31.0.62.
  • • 41 of 42 checks ran. Skipped checks are listed by name with the reason, and are left out of the score rather than counted as passes.
  • • Weighed 10 of 19 same-origin resources the page references (sampling cap 10); sizes come from the server's Content-Length header where it sent one.
  • • Requested 19 of 19 same-origin links found in the HTML (cap 20 per scan). External links are not tested.
  • • These are automated checks on the page as delivered to us, once. Accessibility findings come from the markup only — no colour contrast, focus or keyboard testing — and this is a readiness audit, not a WCAG or ADA conformance certification.

41 of 42 checks ran.

Checks that couldn't run (1) — not counted as passes

  • Cookie flags (Secure, HttpOnly, SameSite) — this response set no cookies, so there were no cookie flags to check

These are automated checks on the page as delivered to our scanner at the moment it ran. Accessibility findings come from the markup only — we do not test colour contrast, keyboard use or screen-reader behaviour — so this is a readiness audit and a prioritised to-do list, not legal advice and not a guarantee or certification of WCAG, ADA or any other compliance standard.

Want this for your own client's site?

The free scan shows the scores, the counts and a few example findings. The $49 report is this document — every issue, its evidence and a plain-English fix, prioritised, on one site, printable and emailable. It is a one-off payment, not a subscription.

How you get it: Stripe takes the payment and asks for the website address to audit on its own page — we then run the audit on that page and email the report to the address on your payment. The email carries the report itself — every finding, its evidence and its fix, in full — and a private link that opens the same report as a document you can read, print or save as a PDF. Nothing is unlocked in your browser, because we store nothing.

We email your report within one working day of your payment. If we can't produce your report, you get your money back in full.

Run the free accessibility check on your client's site →Get the full report by email — $49

These are automated checks on the page as delivered to our scanner at the moment it ran. Accessibility findings come from the markup only — we do not test colour contrast, keyboard use or screen-reader behaviour — so this is a readiness audit and a prioritised to-do list, not legal advice and not a guarantee or certification of WCAG, ADA or any other compliance standard.