Here’s the honest answer, laid out plainly, so you can decide whether it’s worth ten minutes of your time: no catch, no pressure, and you’ll walk away with something useful even if you never hire us for anything else.
What We Actually Check
A free audit covers one web page or one PDF document, your choice, whichever one matters most to you right now. Maybe that’s your homepage, your checkout flow, a landing page you’re worried about, or a PDF form your team has been distributing for years without ever checking whether a screen reader can read it. You pick.
That one page or document gets a real look, not a five-second scan. We’re not running it through an automated tool and forwarding you the results with our logo slapped on top, the same manual methods we use on full projects (keyboard navigation, screen reader testing, zoom and contrast checks, structure review) get applied here too, just scoped to a single page instead of an entire site. It’s a genuine sample of what a full audit looks like, not a teaser with the good parts held back.
What “Manual” Actually Means, Even for One Page
It’s worth being specific about this, because the word “manual” gets used loosely across the industry. When we test your page, someone unplugs the mouse and tabs through every link, button, and form field on it, checking whether the keyboard focus is always visible and never gets stuck. Someone else, or the same person, on a second pass, turns on a screen reader and listens to how your headings, images, and form fields actually get announced, which is often wildly different from how the page looks on screen. We zoom the page to 200% and beyond to check whether text overlaps or gets cut off. We check the actual color pairings that appear on your page, not theme defaults, the real text-on-background combinations a visitor sees, against the WCAG contrast thresholds.
None of that happens from an automated scanner glancing at your HTML. A scanner can tell you an image is missing alt text; it can’t tell you whether your keyboard focus disappears inside a dropdown menu, or whether your screen reader announces your “Submit” button as just “button.” Those are exactly the kinds of things a five-minute page-level test tends to surface, and they’re often the difference between a site that looks fine and a site that’s actually usable.
What a Typical Finding Looks Like
To make this less abstract: a common pattern we run into on a first page test is a contact form where the input fields have no labels connected to them in the code, visually, the word “Email” sits right above the box, so it looks perfectly clear. But a screen reader doesn’t see visual proximity; it only knows what’s connected in the code. Without that connection, a blind visitor hears “edit text, blank” with no idea what they’re supposed to type. It’s an easy fix once someone knows to look for it, and it’s exactly the kind of gap that a quick automated scan sometimes catches and sometimes completely misses, depending on how the form was built. Either way, you’d know about it, in plain terms, within two business days.
What You Get Back, and When
You’ll have something in hand within two business days. That’s not a “we’ll get back to you eventually” promise, it’s the actual turnaround for a single-page or single-document review.
The report itself comes in whichever format is more useful to you:
A developer-ready report, if you have someone on your team who’s going to fix the issues themselves. This version names the specific problems, points to where they live in the code, and explains what needs to change and why, written so a developer can act on it without needing a translator.
A high-level stakeholder report, if you’re the one who needs to understand the situation and decide what to do next, rather than the one writing code. This version explains the same findings in plain language: what’s wrong, why it matters, and what the risk or impact looks like, without assuming any technical background.
Just let us know which one fits your situation when you request the audit, and that’s what you’ll get. If you’re honestly not sure which one you need, default to the stakeholder version, it’s written clearly enough that a developer can still extract the technical specifics from it, while a non-technical reader won’t get lost in jargon they don’t need.
Two Reports, Same Findings, Different Audiences
It’s the same underlying testing either way, nothing about the findings changes based on which report you request, only how they’re presented. The developer-ready version reads more like a bug report: specific elements, specific code-level issues, specific fixes, organized so someone can work through it top to bottom and check items off. The stakeholder version reads more like a briefing: what we found, why it matters for actual visitors, and what the general path forward looks like, without assuming the reader knows what “ARIA” or “focus order” mean going in.
Neither version is the “real” one and the other a simplified copy, they’re both accurate, just aimed at different jobs. A lot of accessibility reports we’ve seen from other vendors make the mistake of writing only for one audience, which means either the developer has to translate jargon-free prose back into actionable tasks, or the non-technical stakeholder has to sit through a report full of terms they’ve never heard. We’d rather just ask upfront which one you need.
Why We Don’t Charge for This
Partly because it’s genuinely useful for us too, showing you real findings on your real page is a much better conversation starter than asking you to trust a sales pitch. And partly because we think you deserve to see, concretely, what “manual testing” actually turns up before you commit any money to a larger project. A lot of accessibility vendors sell audits sight unseen. We’d rather you see the work first.
What a Free Audit Doesn’t Cover
To keep this honest: a free audit is a sample, not a substitute for a full site review. It covers one page or one document, thoroughly, it does not cover your entire website, every PDF in your document library, or ongoing monitoring as your site changes over time. If your homepage comes back clean but your checkout flow has serious problems, a homepage-only audit won’t tell you that, because it was never scoped to look there.
It also isn’t a certification. Nothing we hand you says “compliant” or “certified,” because no single-page snapshot can honestly make that claim about an entire website, and any accessibility vendor who tells you otherwise is overselling what a page-level review can prove. What you get is an accurate, detailed picture of one page or document, from which you can reasonably infer whether the rest of your site likely has similar patterns, most sites are built consistently, for better or worse, so one page’s issues are often a preview of what’s elsewhere too.
Who This Is Actually Useful For
You don’t need to be far along in an accessibility journey to get value from this, and you don’t need to already suspect something is wrong. A few situations where it tends to be worth the ten minutes it takes to request one:
You’ve received a demand letter or complaint and want a clear, honest read on what’s actually happening on the page in question before you respond to it or hire anyone. You’re evaluating whether to invest in a larger remediation project and want to see real findings before committing budget. You inherited a website or a PDF workflow from a previous team and genuinely don’t know its condition. You’re simply curious what “manual testing” turns up, versus whatever automated scanner your team may have run before. You’re a developer or agency doing work for a client and want a second opinion on a page before you sign off on it. You’re deciding between two vendors and want to see how one of them actually tests, rather than take their word for it.
In every one of these cases, the answer you get is the same either way: specific, accurate, and written for the audience you tell us it’s for.
What We Need From You
Just the page URL or the PDF file, and a note on which report format you’d like, developer-ready or stakeholder-friendly. That’s it. No credit card, no long intake form, no obligation to do anything with what we send back.
Frequently Asked Questions
Is this really free, with no obligation afterward?
Yes. You’ll get the report either way, and what you do with it afterward, nothing, fix it yourselves, or come talk to us about a larger project, is entirely up to you.
Can I request a free audit for more than one page?
The free audit covers one web page or one PDF. If you have several pages or documents you’d like reviewed, that’s exactly what our full manual website audit and PDF remediation services are for, and we’re happy to talk through pricing for those.
What if the audit doesn’t find anything wrong?
That happens, and it’s genuinely good news if it does, we’ll tell you plainly that the page tested clean, rather than manufacturing problems to justify the report. An honest “this looks solid” is worth just as much as a list of findings.
Which report format should I choose if I’m not sure?
If you’re not sure who on your team will end up reading it, the stakeholder-friendly version is usually the safer choice, it’s written so a non-technical reader can follow it completely, and a developer can still act on the specifics inside it if needed. You can always ask for the developer-ready version afterward if it turns out you need the deeper technical detail.
Will you try to sell me something after I get the report?
We’ll mention what a fuller remediation project could look like if the findings suggest there’s more to fix beyond the one page, because that’s honestly useful information, but there’s no follow-up call you’re obligated to take, and no pressure attached to the report itself. If you’d rather just take the findings and go, that’s completely fine.
Do you keep testing my page after the two days, or is it a one-time snapshot?
It’s a one-time snapshot of the page as it exists when we test it. If you make changes afterward and want to confirm they worked, or if your site changes significantly down the line, that’s a good moment to request a new audit or talk to us about ongoing monitoring as part of a larger project.
Ready to See What’s Actually on Your Page?
Pick the one page or PDF that matters most to you right now, and request your free audit. You’ll have real findings in two business days, in whichever format actually helps you, no sales call required to get there. If you already know you want a broader look, our website audit and remediation and pricing pages have the details on full projects.
