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 behaviour and identify context for the fixes 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.
Remediation scope, effort, and constraints
Cross-referencing the findings against the codebase to identify the relevant areas for remediation, group findings that depend on the same change where appropriate, estimate the effort involved, and assess constraints, dependencies, and items awaiting further confirmation. Review includes DOM-level and code-level observation.
Client decisions and separate-scope items
Identifying where remediation depends on a design decision, content decision, or client confirmation — and flagging items to be handled under a separate scope.
A fixed fee for the scoping work.
Reporting
Fee
From 1,750 EUR
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
- Tax is not normally added to the listed or quoted fee. For clients in Japan, Japanese consumption tax is added where applicable. Standard payment processing is included. Your bank or payment platform may charge its own fee separately.
- Prices are listed and quotes are normally issued in EUR. Payment may be made in EUR, GBP, USD, JPY, or another agreed currency.
- For payment in a currency other than EUR, the amount shown on the invoice or payment request is converted from the agreed EUR amount using the exchange rate in effect on its issue date. Where a quote is issued, it is valid for 14 calendar days unless otherwise stated.
- Payments are generally handled through Stripe or Deel, depending on the service and agreed setup. Stripe supports credit and debit card payments. Deel can support card and bank-transfer payments as part of its contractor payment process.
- 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, 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 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.
- 05
NDA signed
A non-disclosure agreement is signed before access to the codebase, staging environment, or other non-public project material is shared.
- 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 form part of the setup. Exact access arrangements 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.