ADA and privacy as a service, without pretending you are a lawyer.

What you can sell without being a lawyer

You can sell a visible gap on a public page and a draft that tries to close that gap, labeled as a draft that needs professional review. Missing privacy policy in the footer. No cookie notice on a site that sets cookies. An obvious keyboard trap you can reproduce. Those are marketer-visible objects.

You cannot sell a legal opinion, a certification, a promise that lawsuits will stop, or a badge that implies a standard you did not meet. You cannot sell HIPAA coverage this product does not have. You cannot sell SOC 2 you do not have. If a programme is underway, say in progress. If it is not, omit it.

The buyer is the marketer. Owners will ask you to talk like a lawyer because it is cheaper than hiring one. Your job is to refuse the costume and still be useful. Useful is the draft, the gap screenshot, the reviewer in the SOW, and a deploy that does not go live on a hope.

Forge can open a compliance fixer and emit that draft. You can write the same draft in a document. Either way the sentence professional review recommended is part of the file, the email, and the invoice line. If a client asks you to remove it so the page looks official, that is your walk-away moment.

This guide is not legal advice. It will not cite a statute as if the author were counsel. It will tell you how to keep the work inside a marketer’s lane so you can fulfill a week without pretending you passed a bar exam.

If a prospect asks whether you handle ADA, answer with the object. We find the missing policy or the blocked button, we draft, we require a reviewer, we do not certify. If that sentence loses the deal, the deal wanted a costume. There are other detectors on the ranked list.

How to label every draft so the label survives the sale

Label every draft in the filename, the first heading, the email, and the SOW. Draft privacy policy. Professional review recommended. Not final. Not legal advice. If the label exists only in your head, it will not exist in their footer next month.

Put the date and the URL you looked at on the first line. Draft based on the public pages at this URL on 8 September. Reviewers need the snapshot. Owners need to know you did not invent a shop they are not. Supervised means you saw those nouns.

Do not let a portal or a pretty Atlas cover strip the label to look premium. Premium in this lane is the opposite: a cover that says draft. The credibility gate that refuses bare dollars is the same instinct. A bare policy looks like law. A labeled policy looks like work.

If you use a model to draft, you still own every clause. Models invent addresses, officers, and statutes. Read the document as if you will be forwarded to counsel. Because you will. Delete anything you cannot source from their public pages or from a template the reviewer accepts.

Keep a copy of the labeled draft after they publish a revised version. When a staff member pastes an unlabeled rewrite, you can show what you delivered. Steward can hold the artifact. A folder named drafts / do not strip labels can too.

If you brand the draft as Atlas, keep the label on the cover in the same size as the title. A small italic line under a confident headline is how the costume sneaks back. Reviewers read covers first. Owners forward covers. The cover is the product.

How to sell a missing privacy policy as a finding

Sell a missing privacy policy as a footer and a form that collect information with no public policy URL. The proof is the page, the form fields, and the date. The sample is a draft policy built from what the site already does in public.

Stay inside what you saw. If they collect a name and an email on a contact form, the draft can talk about that form. If you did not see card processing, do not write a payments section as if you audited Stripe. Guessing processors is how drafts become fiction.

The first email, if you send one at all, names the gap without a lawsuit story. Your site collects names on the contact form and has no privacy policy linked as of Tuesday. I drafted one from those pages. A reviewer should read it before you publish. That is enough. The ADA lawsuit is coming is a scan.

Do not make this the wedge for a shop with no website. They need a page before they need a policy on the page. Compliance bolted onto a No-Website sequence is a second detector pretending to be urgency.

FEE is the draft plus time to sit with a reviewer or plus a pass-through of the reviewer’s invoice. Do not FEE peace of mind. Peace of mind is a phrase that teaches them they bought immunity. They bought a document.

How to talk about ADA without a certification

Talk about ADA as access problems a visitor can hit, not as a certificate you will hang in their lobby. Can a keyboard user reach the book button. Do images of the menu have text somewhere. Is the phone number a real link on mobile. Those are reproduceable notes.

Write the notes as observations. On Tuesday the book button was not reachable by keyboard in Safari. I changed the DEMO so it is. A reviewer should still test the live site. Observation, fix on the preview, review on production. That chain is honest. We made you ADA compliant is not.

WCAG versions, Title III arguments, and demand-letter tactics are the reviewer’s language. If you speak them to sound expert, you will be asked to defend them. Defend artifacts instead. Before screenshot. After DEMO. Labeled.

Medical and legal verticals need more caution, not more swagger. Do not imply HIPAA. Do not imply a courthouse outcome. If the shop’s reviews discuss health facts, collection and access work both get quieter and more reviewed. When unsure, you sell the site gap and you bring counsel in before you sell the access draft.

There is no badge in this product that means certified accessible. Do not design one for your agency either. Badges are how owners think the work is finished. Access work is not finished. It is tested, then tested again after the next theme change.

What cookie copy is, and what it is not

Cookie copy is a notice and a choice that match the scripts the site actually loads. It is not a European-looking banner you pasted because a competitor had one. If you cannot list the scripts, you cannot write the notice.

Start with a scan you can repeat. What loads on the homepage. Analytics, chat, ads, a map embed. Write those names in the draft. If you did not see an ad pixel, do not confess to one. Confession fiction is still fiction.

Choice has to do something. A banner that says accept and has no reject, or a reject that does nothing, is decoration. Decoration is worse than no banner because it teaches a visitor they were given a choice. If you cannot wire the choice, say the draft is copy only and the implementer still has work. Put that in the SOW.

State and country rules differ. This guide will not pick your regime. If the shop serves one US metro and loads three scripts, your reviewer still decides the notice. You decide not to invent an EU-first residency story, and not to invent a GDPR badge, to make the banner look worldly.

Cookie work is a bad first email. It is a good leftover finding after a site DEMO, when you already know what you installed. If your DEMO added analytics, you created part of the gap. Own that in the draft.

How to put professional review in the SOW so it actually happens

Put professional review in the SOW as a named step with a named role, a named artifact, and a rule that deploy waits. Reviewer: counsel of their choice, or an accessibility specialist you introduce. Artifact: the labeled draft. Rule: Forge deploy, or your host’s publish, stays gated until the reviewer says publish or the owner accepts the risk in writing.

Accepts the risk in writing is not your favorite path. It exists because owners will skip counsel to save a week. If they skip, the email they send you is the record. You still do not strip the label. You still do not add a certified badge.

Introduce a reviewer if you have one. Do not take a cut that depends on them going easy. That cut is how drafts get rubber-stamped. A rubber stamp is the costume again.

Time the FEE so the review is not an unpaid extra. Either the owner pays the reviewer directly, or you pass the invoice through, or you include a fixed review pass from a person who is actually qualified. What you cannot do is include review as a vibe in your day rate and then skip it.

Supervised applies. A model does not publish the policy because the calendar said Friday. Muse and Forge stay gated. If you have no product gates, you are the gate. Friday is not a reason.

What not to put in the first email

Do not put a lawsuit prediction, a demand-letter scare, a fake deadline from a scanner, or a percentage of businesses that get sued. If you have no source, you have no percentage. This site will not invent one for you.

Do not put a dump of every accessibility failure a crawler printed. That dump is a scan. Pick the one gap you can DEMO this week. Park the rest as leftovers on the record.

Do not put we are not lawyers in six-point gray after a hero sentence that promised compliance. The disclaimer cannot save a pitch that sold immunity. Put the lane in the first paragraph, in the same type size as the offer.

Do not attach an unlabeled PDF that looks like a statute summary you copied from a blog. Attach the DEMO or the labeled draft. Sample-first still applies. The sample is the draft or the more accessible preview, not a fear appendix.

If the only detector you have is compliance, and you cannot fulfill it with a reviewer, do not send. Hunt no website, no booking, or a collect-page gap. Those guides exist so you are not tempted to become a scare vendor on a slow Monday.

How to fulfill the draft this week without over-claiming

Fulfill this week by reproducing the gap, writing or generating the labeled draft, putting it on a preview, and booking the reviewer or sending the owner the review step in writing. That is a complete week. Published-and-blessed is a later week.

Reproducing matters. If you cannot tab to the button, write that. If you can, do not invent a failure to have a finding. False ADA findings are how this lane earns a reputation next to review gating: clever, then distrusted.

Keep the DEMO small. One policy page, or one fixed component, not a theme rewrite sold as access. Rebuilds can wait for the sell-a-website motion. Compliance as a theme rewrite is a bait-and-switch.

If you added forms on a site DEMO, you probably added privacy work. Do the draft then, as part of that FEE or as a named extra, not as a surprise after deploy. Surprises in this lane feel like extortion even when you meant well.

Unknown sources stay unknown. If you did not crawl the whole site, do not title the draft sitewide audit. Title it based on the pages you opened. Radar’s deep memo can be wider. Your week-one draft does not have to pretend it was.

When to walk away from the conversation

Walk away when they want the label stripped, when they want a badge you cannot defend, when they want you to ignore a reviewer, when they want a gate on reviews because the reviews mention access, or when they want HIPAA language you cannot support.

Walk away when the first vendor already sold them certified for a flat FEE and they want you to match the lie. Matching the lie is how you inherit the demand letter. Refer them to counsel and go back to a detector you can fulfill.

Walk away from verticals you will not study. A hospital system is not a cafe with a missing cookie banner. Industry pages on this site for medical exist to name inbound voice and reviews, and to say we are not a HIPAA-certified EHR. Your ICP can exclude the rows that would force you to pose.

Do not walk away from a missing footer on a cafe just because the lane has lawyers in it. The cafe still needs a labeled draft and a reviewer. Fear of the lane is how marketers leave obvious gaps sitting, then send a darker scare later.

Write the walk-away in the record so a teammate does not reopen it as a hot lead. Parked: asked us to certify. Not a fit. Pulse can hold that. A sheet can hold that. What it cannot become is a sequence that keeps threatening them.

How to reproduce a keyboard trap before you write the finding

Reproduce a keyboard trap before you write the finding because false ADA findings are how this lane earns a reputation next to review gating: clever, then distrusted. On Tuesday the book button was not reachable by keyboard in Safari. I changed the DEMO so it is. A reviewer should still test the live site. Observation, fix on the preview, review on production. That chain is honest. We made you ADA compliant is not.

Talk about ADA as access problems a visitor can hit, not as a certificate you will hang in their lobby. Can a keyboard user reach the book button. Do images of the menu have text somewhere. Is the phone number a real link on mobile. Those are reproduceable notes. WCAG versions, Title III arguments, and demand-letter tactics are the reviewer's language. If you speak them to sound expert, you will be asked to defend them. Defend artifacts instead. Before screenshot. After DEMO. Labeled.

Keep the DEMO small. One policy page, or one fixed component, not a theme rewrite sold as access. Rebuilds can wait for the sell-a-website motion. Compliance as a theme rewrite is a bait-and-switch. If you cannot tab to the button, write that. If you can, do not invent a failure to have a finding. Unknown sources stay unknown. If you did not crawl the whole site, do not title the draft sitewide audit. Title it based on the pages you opened.

You do not need Nerxus One to reproduce the gap. Forge can open a compliance fixer and emit a labeled draft. You can write the same draft in a document. Either way the sentence professional review recommended is part of the file, the email, and the invoice line. If a client asks you to remove it so the page looks official, that is your walk-away moment.

What to do when the DEMO added the analytics pixel

When the DEMO added the analytics pixel, own that in the cookie draft, because you created part of the gap and a European-looking banner you pasted because a competitor had one is decoration. Cookie copy is a notice and a choice that match the scripts the site actually loads. If you cannot list the scripts, you cannot write the notice. Start with a scan you can repeat. What loads on the homepage. Analytics, chat, ads, a map embed. Write those names in the draft. If you did not see an ad pixel, do not confess to one.

Choice has to do something. A banner that says accept and has no reject, or a reject that does nothing, is decoration. Decoration is worse than no banner because it teaches a visitor they were given a choice. If you cannot wire the choice, say the draft is copy only and the implementer still has work. Put that in the SOW. State and country rules differ. This guide will not pick your regime. Do not invent an EU-first residency story, and do not invent a GDPR badge, to make the banner look worldly.

Cookie work is a bad first email. It is a good leftover finding after a site DEMO, when you already know what you installed. If you added forms on a site DEMO, you probably added privacy work. Do the draft then, as part of that FEE or as a named extra, not as a surprise after deploy. Surprises in this lane feel like extortion even when you meant well.

Staff will paste new chat widgets. Widgets add scripts. Scripts stale the cookie draft. Quarterly opens of the live URL are part of the retainer if you sold a retainer. If you sold a one-time FEE, say that re-checks are extra, or they will not happen and they will still call you when a banner looks wrong. Freshness decays here too. A stale policy is a new finding, still labeled, still reviewed.

How to introduce a reviewer without taking a rubber-stamp cut

Introduce a reviewer without taking a cut that depends on them going easy, because that cut is how drafts get rubber-stamped and a rubber stamp is the costume again. Put professional review in the SOW as a named step with a named role, a named artifact, and a rule that deploy waits. Reviewer: counsel of their choice, or an accessibility specialist you introduce. Artifact: the labeled draft. Rule: Forge deploy, or your host's publish, stays gated until the reviewer says publish or the owner accepts the risk in writing.

Accepts the risk in writing is not your favorite path. It exists because owners will skip counsel to save a week. If they skip, the email they send you is the record. You still do not strip the label. You still do not add a certified badge. Time the FEE so the review is not an unpaid extra. Either the owner pays the reviewer directly, or you pass the invoice through, or you include a fixed review pass from a person who is actually qualified. What you cannot do is include review as a vibe in your day rate and then skip it.

Keep a reviewer name on the record even when the owner has not booked them yet. Blank reviewer fields are how Friday publishes happen. A name or a written refusal is the only finished state. No name means the draft is still sitting, even if the preview looks done. Supervised applies. A model does not publish the policy because the calendar said Friday. Muse and Forge stay gated. If you have no product gates, you are the gate. Friday is not a reason.

If a teammate wants a shorter pitch, give them four words and a next step. Drafts, labeled. Book the reviewer. That is the whole offer. Anything longer is either a finding you can screenshot or a costume you should delete. You can do this with a document, a preview URL, and a reviewer. Nerxus One is the version with a fixer that emits the draft and a gate that still needs a human.

What medical pages must not say even if the footer is missing

Medical pages must not imply HIPAA coverage, an EHR, or a BAA we have not signed, even if the footer is missing a privacy policy, because public signals only is the fence and a detector that mentions a HIPAA-shaped gap is still not coverage. Medical and legal verticals need more caution, not more swagger. Do not imply a courthouse outcome. If the shop's reviews discuss health facts, collection and access work both get quieter and more reviewed. When unsure, you sell the site gap and you bring counsel in before you sell the access draft.

You cannot sell SOC 2 you do not have. If a programme is underway, say in progress. If it is not, omit it. There is no badge in this product that means certified accessible. Do not design one for your agency either. Badges are how owners think the work is finished. Access work is not finished. It is tested, then tested again after the next theme change. Industry pages on this site for medical exist to name inbound voice and reviews, and to say we are not a HIPAA-certified EHR.

Your ICP can exclude the rows that would force you to pose. A hospital system is not a cafe with a missing cookie banner. Walk away from verticals you will not study. Walk away when they want HIPAA language you cannot support. Walk away when the first vendor already sold them certified for a flat FEE and they want you to match the lie. Matching the lie is how you inherit the demand letter. Refer them to counsel and go back to a detector you can fulfill.

Do not walk away from a missing footer on a cafe just because the lane has lawyers in it. The cafe still needs a labeled draft and a reviewer. Fear of the lane is how marketers leave obvious gaps sitting, then send a darker scare later. Write the walk-away in the record so a teammate does not reopen it as a hot lead. Parked: asked us to certify. Not a fit. Pulse can hold that. A sheet can hold that. What it cannot become is a sequence that keeps threatening them.

How quarterly re-checks sit on a one-time FEE

Quarterly re-checks sit on a one-time FEE as extra work you named, or they will not happen and they will still call you when a banner looks wrong, because freshness decays here too and a stale policy is a new finding. After the draft is live, you re-check the pages when the theme changes, when a new form appears, or when a Watchtower-style pass says the policy URL 404s. Still labeled. Still reviewed.

Staff will paste new chat widgets. Widgets add scripts. Scripts stale the cookie draft. If you sold a retainer, quarterly opens of the live URL are part of the FEE conversation. If you sold a one-time FEE, say that re-checks are extra. Keep health bands if you track the account. Healthy, Watch, or At-risk. A missing policy can move health. It does not print their revenue. It does not print a lawsuit probability. Bands plus leftovers are enough for Steward.

Train teammates with the same sentences. Drafts. Review recommended. No badges we do not have. No HIPAA we do not have. No scare percentages. No first-email dumps. The lane is a script. Scripts survive turnover. Expertise cosplay does not. Do not put a lawsuit prediction, a demand-letter scare, a fake deadline from a scanner, or a percentage of businesses that get sued. If you have no source, you have no percentage. This site will not invent one for you.

Fulfill this week by reproducing the gap, writing or generating the labeled draft, putting it on a preview, and booking the reviewer or sending the owner the review step in writing. That is a complete week. Published-and-blessed is a later week. If the only detector you have is compliance, and you cannot fulfill it with a reviewer, do not send. Hunt no website, no booking, or a collect-page gap. Those guides exist so you are not tempted to become a scare vendor on a slow Monday.

When to park a row that asked you to certify

Park a row that asked you to certify because matching the lie is how you inherit the demand letter, and a sequence that keeps threatening them is the scan this lane must not become. Walk away when they want the label stripped, when they want a badge you cannot defend, when they want you to ignore a reviewer, when they want a gate on reviews because the reviews mention access, or when they want HIPAA language you cannot support.

Write the walk-away in the record so a teammate does not reopen it as a hot lead. Parked: asked us to certify. Not a fit. Pulse can hold that. A sheet can hold that. If a prospect asks whether you handle ADA, answer with the object. We find the missing policy or the blocked button, we draft, we require a reviewer, we do not certify. If that sentence loses the deal, the deal wanted a costume. There are other detectors on the ranked list.

Keep a copy of the labeled draft after they publish a revised version. When a staff member pastes an unlabeled rewrite, you can show what you delivered. Steward can hold the artifact. A folder named drafts / do not strip labels can too. If you brand the draft as Atlas, keep the label on the cover in the same size as the title. A small italic line under a confident headline is how the costume sneaks back. Reviewers read covers first. Owners forward covers. The cover is the product.

This guide is not legal advice. It will not cite a statute as if the author were counsel. It will tell you how to keep the work inside a marketer's lane so you can fulfill a week without pretending you passed a bar exam. The method if you do not buy is the same sentence this page started with. Drafts, labeled. You are not a lawyer. Do not pretend.

How marketers stay in the lane after the draft is live

After the draft is live, you re-check the pages when the theme changes, when a new form appears, or when a Watchtower-style pass says the policy URL 404s. Freshness decays here too. A stale policy is a new finding, still labeled, still reviewed.

Staff will paste new chat widgets. Widgets add scripts. Scripts stale the cookie draft. Quarterly opens of the live URL are part of the retainer if you sold a retainer. If you sold a one-time FEE, say that re-checks are extra, or they will not happen and they will still call you when a banner looks wrong.

Keep health bands if you track the account. Healthy, Watch, or At-risk. A missing policy can move health. It does not print their revenue. It does not print a lawsuit probability. Bands plus leftovers are enough for Steward.

Train teammates with the same sentences. Drafts. Review recommended. No badges we do not have. No HIPAA we do not have. No scare percentages. No first-email dumps. The lane is a script. Scripts survive turnover. Expertise cosplay does not.

You can do this with a document, a preview URL, and a reviewer. Nerxus One is the version with a fixer that emits the draft and a gate that still needs a human. Useful if you buy. The method if you do not is the same sentence this page started with. Drafts, labeled. You are not a lawyer. Do not pretend.

If a teammate wants a shorter pitch, give them four words and a next step. Drafts, labeled. Book the reviewer. That is the whole offer. Anything longer is either a finding you can screenshot or a costume you should delete.

Keep a reviewer name on the record even when the owner has not booked them yet. Blank reviewer fields are how Friday publishes happen. A name or a written refusal is the only finished state. No name means the draft is still sitting, even if the preview looks done.