FAQ
Common questions,
answered up front.
Anything not covered here, drop it on the intake form and we'll answer in the reply.
inbox / intake-replies
Resolved thread
2h · todayBBrand lead· 09:14
Build sits behind our staging VPN and there's a basic-auth gate on top. Can you still run a full QA pass before Friday?
TtestStrategy· 11:02
Yes — VPN + basic auth is a common setup. Once the paperwork is signed we'll set up access with you over a secure channel, and findings will be in your dashboard by Thursday.
replied in 1h 48mresolved · scoped
- How much does an engagement cost?
- Engagements start at $299 for a paid discovery — a 30-minute call plus a written scope and flat quote. Full QA passes are quoted after the discovery, since price depends on page count, copy length, languages, environments, and the depth of accessibility / tracking checks you need. The discovery fee is applied to the engagement if you move forward.
- How fast can you turn around a QA pass?
- Most one-off pre-launch passes land in 24–72 hours from the moment we have the build, the copy deck, and any access we need. Tighter windows are possible — say so on the intake form and we'll tell you on the discovery call whether we can hit it.
- Do we need to grant you VPN or proxy access?
- Sometimes. If your build sits on an internal staging environment behind a VPN, SSO, or IP allowlist, we'll need either temporary access (your VPN client, a guest SSO account, an IP we can whitelist) or a publicly reachable preview URL with basic auth. The intake form has a question for this — flag it early so we can plan it into scope.
- What's in the report?
- A dashboard summarising findings by severity and screen, a side-by-side copy-deck diff, annotated screenshots for every visual issue, and a CSV of all findings for ticketing. PDF export is included. The report is structured so you can hand it to a client without redacting anything.
- Do you sign NDAs?
- Yes — happy to sign a mutual NDA before the discovery call. Send yours, or we can use a standard one. When an engagement ends, tell us what you'd like deleted and we'll confirm in writing once it's done.
- How do you handle accessibility?
- Reviews follow WCAG 2.2 AA. We cover semantics, alt text, heading structure, landmarks, focus states, keyboard navigation, tap-target size, and color contrast. Findings are grouped by severity so your team can prioritise WCAG-blocking issues separately from polish.
- Do you do load testing or security testing?
- No — we focus on functional, content, accessibility, analytics, and integration QA. For load and security, we'll happily refer you to specialists.
- What's outside scope on a standard pass?
- Anything that requires changes to your codebase, infrastructure, or vendor contracts. We surface issues, repro them, and explain the impact — your team or your agency does the fixes. We can re-test once fixes ship.
Still have a question?
The contact form takes a minute. Phone, email, and LinkedIn are on the same page if you'd rather start there.