Tool Methodology

AldoMedia publishes several free scanning tools. This page explains exactly what they test, how the scores are produced, what they cannot tell you, and what happens to the information you enter. Last reviewed July 25, 2026 by Aldo Giammusso. Updated October 16, 2026 for the new accessibility engine and scoring changes.

How the scans work

You submit one URL. Our server requests that single page over HTTP and reads the HTML the server sends back. Every check runs against that HTML.

Two consequences follow from this, and they matter:

  • We do not run your JavaScript. The scan sees the HTML your server returns, not the page a browser builds afterwards. If your site renders its content, navigation or alt text with JavaScript, our tools will not see that content and may report it as missing.
  • We scan one page, not your website. Results describe the URL you submitted. Nothing is inferred about the rest of your site.

We also cannot reach anything behind a login, a paywall, a firewall, or a bot-blocking service. When a firewall or bot check answers instead of your page, the tools say so and do not produce a score, rather than grading the block page.

How the score is calculated

Each check passes or fails, and each carries a weight reflecting how much it typically matters. On the AI readiness and SEO tools a check can also come back as a warning, which earns half its weight. The score is the weight you earned divided by the total weight available, expressed as a percentage and rounded to a whole number. If a page tells search engines not to index it, or blocks the crawlers a tool depends on, those two scores are capped at 49, because nothing else on the page helps until that is fixed. A score of 100 means every check we run passed. It does not mean the page is perfect, compliant, or safe, because the score can only reflect the checks listed below.

Website Legal-Risk Signals Scan

The legal-risk scan tests 20 signals: SSL certificate, privacy policy, terms of service, accessibility statement, cookie consent, business address, phone number, email contact, contact form, secure form action, mobile viewport, responsive layout, image alt text, language tag, page title, H1 heading, form labels, copyright notice, mixed content, and ARIA landmarks.

Most of these are presence checks. We can see whether a privacy policy is linked and reachable; we cannot read it and judge whether it describes your actual data practices, covers the right jurisdictions, or says anything accurate. The same applies to your terms of service and accessibility statement. An automated scan cannot determine legal compliance, and nothing it reports is legal advice.

Automated Accessibility Precheck

The accessibility precheck runs axe-core 4.12, the open-source rules engine from Deque Systems that also drives the accessibility audit in Google Lighthouse. It applies the axe rules for WCAG 2.0, 2.1 and 2.2 at Levels A and AA, plus axe's best-practice rules: alt text, colour contrast, form labels, ARIA, heading order, link and button names, landmarks, skip links, language, page title, zoom blocking, tables, frames, video captions, tap target size and more. We add two checks of our own: a timed auto-refresh, and a link to an accessibility statement.

Unlike our other tools, the precheck renders the page. The HTML is loaded with its own stylesheets and images into a sealed-off frame in your browser, with all of its JavaScript removed, so colour contrast and target sizes are measured on the real layout. Text over a photo or a gradient cannot be measured reliably, so it is listed as needing a manual check. The score works like Lighthouse's accessibility score: each rule that applies to the page carries a weight based on its impact (critical 10, serious 7, moderate 3, minor 1), and results that need a manual check are listed but not scored.

Automated tooling can only evaluate a portion of the WCAG 2.1 success criteria. It can tell you an image has no alt attribute; it cannot tell you whether the alt text you wrote is meaningful. It can find a heading-order jump; it cannot tell you whether your focus order makes sense to someone using a keyboard, or whether a screen reader announces your content usefully. Passing this precheck is not a statement of WCAG conformance or of ADA compliance. A manual audit, ideally including testing with assistive technology, is the only way to answer that.

Online Reputation Scanner

The reputation scanner runs three searches for a name through the Tavily search API (a general search, one pairing the name with words like scam or lawsuit, and a news search, plus a fourth for the company if one is entered), and checks Wikipedia. It keeps only results that mention the name or company in the title, description or web address, then groups them: social profiles, professional listings and directories, news and media mentions, review and rating platforms, and possible risk items. A result counts as a possible risk item only when it sits on a complaint, mugshot or court-record site with the name in its title or address, or when its title ties the name to words like scam, lawsuit or arrested.

It reports what Tavily's search returns at the moment you run it, which will not match Google exactly. It cannot confirm that a result refers to you rather than to someone with the same name, so it marks results that also mention your city, field or company as strong matches and shows risk items for review rather than as findings. It does not see private or deleted content.

Other tools

The SEO and AI revenue calculator produces an estimate from the figures you enter. It is arithmetic on your own assumptions, not a forecast, and changing the inputs changes the answer. The code error checker sends the HTML of the page you enter to the W3C Nu Html Checker, or to the same software at validator.nu if W3C is unavailable, and groups what it reports. It then requests up to 30 of the page's CSS and JavaScript files and flags only definite failures: a missing file, a server error, or an error page in place of the file. A file that refuses our request is listed as unverified, not broken. It also lists resources loaded over plain http:// on an https:// page. The SEO score tool and AI readiness scanner follow the same single-page, no-JavaScript approach described above, and also read the site-wide files and records that affect that page, such as robots.txt, your XML sitemap and your domain's email security (SPF and DMARC) records.

What we do with what you enter

The scanning forms ask for your name, email address, phone number, company and the URL to scan. That information is emailed to AldoMedia and written to a log file on our server so we can send you the results and follow up about your website. We use Google reCAPTCHA on the forms to block automated abuse, which means Google receives data about your interaction with the form under its own terms. See our privacy policy for how we handle personal information, and contact us if you want your submission deleted.

Corrections

If one of these tools reports something you believe is wrong about your site, tell us and include the URL you scanned. Misreported checks are a bug and we want to know. Our editorial and corrections policy covers how we handle that.

Are you ready to meet us? make an appointment today.

We have a comfortable office and conference room built to get our conversation going and our creative juices flowing.