Support and frequently asked questions

Up to 25 pages of any website, against the WCAG 2.1 Level A and AA success criteria. We discover pages from your sitemap or follow links from your starting URL, or you tell us exactly which pages to scan on the intake form.

The Web Content Accessibility Guidelines version 2.1, Level AA. It is the international standard for making websites usable by people with disabilities, and the technical standard the U.S. Department of Justice cited in its April 2024 Title II web rule. There are 30 Level A criteria and 20 Level AA criteria; Site Brace tests against all 50. Read the full plain-English primer for more.

Roughly 30 to 40 percent of WCAG issues can be caught automatically. The remaining 60 to 70 percent require human judgment: alt text quality, link context, screen-reader behavior, focus order in complex layouts. We tell you exactly what we caught and exactly what still needs human eyes. The methodology section of every report lists the manual checks you should still run.

Site Brace works on any website. We have tested it across Shopify, WordPress, Webflow, plain static HTML, Sphinx-generated documentation, custom React applications, and government sites. The recommended fixes and the LLM prompts are framework-aware where we can detect the stack.

Reports live on a private subdomain (audit.sitebrace.com) that is blocked from search engines and AI crawlers via robots.txt, HTTP headers, and meta tags. The URL is sent only to the email you provide. We use no analytics, no cookies, and no third-party tracking on either the marketing site or the report subdomain. Read the full privacy policy for details.

Yes. The report URL is generated as a 32-character random string (about 192 bits of entropy, the same security strength as a long password), so no one can guess it or enumerate other reports from it. The URL is your access gate. Treat it like a shared password: anyone with the link can view the report for the full 12-month retention period. Avoid pasting it into public Slack channels, public GitHub issues, public forums, or any service that might index it.

Under 10 minutes from payment to report email for a 25-page audit. Most scans complete in 4 to 7 minutes.

If our scanner cannot reach your site (404, timeout, bot blocking) or if more than half of the requested pages fail to scan, we email you a refund and an explanation. You are not charged for failed audits.

Yes. Your $149 audit includes 12 re-scans within the 12-month retention period. Use them at any pace: monthly for ongoing accessibility monitoring, or burn through them in one week if you are iterating aggressively. Each report shows your remaining count and the access-expiration date. After you ship your fixes, click the re-scan link in your report. We re-scan the same URLs, save the new report alongside the original, and email you a diff: violations fixed, violations still failing, new regressions. Each re-scan covers the same URL set as the original audit. Auditing additional pages beyond the original 25 requires a new audit.

No. ADA compliance is a legal determination that depends on facts about your site, your users, and your jurisdiction. It is not an audit deliverable. What we deliver is precise: WCAG 2.1 Level AA technical conformance as automatedly testable, plus the manual checks we recommend you still run with a person familiar with WCAG.

Section 508 (the U.S. federal accessibility law) references WCAG 2.0 Level A and AA, which is older but compatible with our 2.1 testing. The European Accessibility Act (in force June 2025) and the Accessibility for Ontarians with Disabilities Act both reference WCAG conformance. Our WCAG 2.1 Level AA results are useful starting evidence for any of these frameworks but are not by themselves a legal certification under any of them.

The scanner needs public access to fetch the page. If you need to audit a staging site, make it temporarily accessible: a Cloudflare Access bypass token, an IP allowlist for our scanner, or a temporary public URL all work. Reach out via contact if you need help thinking through the setup.

Chromium 131, the same rendering engine that powers Chrome, Edge, Opera, and Brave (about 85 percent of the global browser market). axe-core's WCAG rules are about HTML, CSS, and ARIA semantics rather than browser-specific rendering, so the same violations would surface in Safari and Firefox; we just do not currently exercise those engines. For Safari-specific behavior (VoiceOver interaction model, etc.) you still need manual screen-reader testing.

The report is delivered as HTML that you view in your browser. To get a PDF, open the report and use File then Print then Save as PDF. The HTML is designed to print cleanly.

After 12 months, the report and audit data are auto-deleted from our storage. The email address you submitted is retained only as long as the audit it was associated with. Read the privacy policy for the full data-retention details.

Watch ($129/yr) runs an automatic scan once a week and emails you a diff. Watch Pro ($399/yr) runs it once a day. Both cover the same 25 pages as your original audit. Both also send a regression alert when a new critical or serious issue surfaces. The detection latency is the difference: with Watch you find out within a week of the issue appearing; with Watch Pro, within 24 hours. The simple picker: if your team ships to production more than once a week, you want Watch Pro. Otherwise Watch is enough. Full feature table on the Watch page.

Email [email protected] and we will move you between Watch and Watch Pro. Self-serve tier swap is on the roadmap; for now it is operator-handled so the credits and timing get reconciled correctly.

No. Watch is a single annual charge, not a subscription. About sixty days before your Watch ends we email you a reminder, and again thirty days before. If you want another year, click the renew button in the email. If you don't renew, your Watch simply ends on the expiration date.

The scan records the unreachable pages as failed. The diff email you receive includes a "scan errored on N pages, will retry next cycle" banner. We do not consume your manual re-scan credits for cron scans, so a failed cron run does not reduce what you can trigger yourself.

No. The 12 manual credits in your base audit are separate from Watch. Cron-driven Watch scans are unlimited within your tier's cadence (weekly for Watch, daily for Watch Pro). Your 12 manual credits stay available to trigger yourself at any time.