Reading your findings against the actual codebase.
A codebase review that turns your external findings into a Remediation Estimate — showing what the fixes involve, what they'll take, and what can be estimated at this point.
What the codebase review covers.
Depending on the project, the review may cover:
Codebase, components, and framework
Understanding the overall structure, framework, component organization, and build setup relevant to the agreed scope. Identifying which UI components, accessibility libraries, and framework patterns are in use, and how they relate to the findings.
Staging environment and flow walkthrough
Reviewing the agreed flows and components in the staging environment to confirm current behavior and identify implementation context that is not visible from the findings alone.
Third-party dependencies and external widget constraints
Identifying where findings relate to third-party components, embeds, or external widgets that may fall outside standard remediation scope.
Implementation scope, effort, and constraints
Cross-referencing the findings against the codebase to identify the relevant implementation areas, group findings that depend on the same change where appropriate, estimate the effort involved, and assess constraints, dependencies, and items requiring further confirmation. Review includes DOM-level and code-level observation.
Client decisions and separate-scope items
Identifying where implementation cannot proceed without a design decision, content decision, or client confirmation — and flagging items that require a separate scope.
A fixed fee for the scoping work.
Reporting
Fee
From 2,000 USD
The Accessibility Scoping Confirmation fee is individually confirmed before payment, based on the form submission and a limited check of the external findings provided.
Working period
Approx. 1–2 weeks or more, depending on scope and complexity.
The working period begins after payment, NDA execution, and receipt of the required materials and access.
Shared output
Remediation Estimate in Google Sheets
The estimate sets out the proposed remediation scope, estimated effort, fee, expected working period, and relevant assumptions. Related findings may be grouped where they depend on the same implementation work, and items requiring further confirmation may be shown without a price.
Scope
Cross-referencing formal findings from an external accessibility review provider with the agreed codebase, staging environment, relevant flows, and components to identify the proposed implementation scope, estimated effort, constraints, dependencies, and assumptions for a Remediation Estimate.
Accessibility review, re-evaluation or verification of the external findings, discovery of additional issues, code changes, and remediation implementation are not included.
Pricing notes
- Prices do not include applicable taxes or bank fees. If Japanese consumption tax applies, it will be added to the invoice.
- Payment is accepted in USD or JPY. JPY amounts are calculated from the listed USD price using the exchange rate in effect when the invoice is issued.
- Payments are processed via Stripe. Bank transfer is available as an alternative for JPY payments only.
- Formal findings from an external accessibility review provider are required. Sola Studio does not provide accessibility review services.
- The fee is individually confirmed before payment, based on a limited check of the provided findings.
- This fee covers the Scoping Confirmation only and is separate from the Accessibility Remediation fee.
- This fee is for the scoping work itself — it's separate from Remediation and isn't credited toward it.
From enquiry to Remediation Estimate.
Once you have external findings in hand, here is how a Scoping Confirmation runs — from the first enquiry through to the Remediation Estimate.
- 01
Enquiry and findings
Submit the enquiry form — agreeing to the Business Terms of Service and Privacy Policy — then provide an access-controlled link to your external findings, either within the form or by email afterwards. Google Drive or an equivalent works fine.
- 02
Limited review to confirm fit and fee
The findings are reviewed only as far as needed to decide whether the project can be accepted and what the fee should be — whether they are formal results from an external provider, whether the subject sits within the standard service area, and their form, volume, granularity, and structure. Interpreting individual findings, verifying their accuracy, cross-referencing against code, or preparing an estimate are not part of this — those are the paid work itself. Sharing findings does not form a contract, and some projects are declined at this point.
- 03
Fee confirmed
If the project is accepted, the fixed fee for the scoping work is confirmed before anything is payable.
- 04
Payment
The confirmed fee is paid before the NDA is signed and before any codebase, repository, or non-public environment access is shared. Payment before NDA is the standard sequence here.
- 05
NDA signed
A non-disclosure agreement is required for this service. It covers the codebase, staging environment, and other material accessed during the scoping work.
- 06
Codebase or staging access confirmed
Read access to the relevant parts of the repository is the most common setup. Staging environment credentials may also be needed. Exact requirements are confirmed against the agreed scope.
- 07
Target flows and components agreed
The pages, flows, and components to be reviewed are agreed before the work starts, so the review has a defined boundary.
- 08
Scoping work and Remediation Estimate
The codebase review is carried out against the findings, and the Remediation Estimate is prepared and shared.
Start with the findings you already have.
Share the findings you already have, along with a short description of the pages, forms, or flows involved. The findings are reviewed to confirm the project is a fit and set the fee — nothing is payable until that's confirmed, and if it isn't a fit, you'll be told directly.