Implementation scope cannot be confirmed without seeing the codebase.
Before Accessibility Remediation Support can be quoted and scoped, the codebase, staging environment, and target components need to be reviewed alongside the existing findings. This service produces that assessment — and an implementation estimate for the remediation work ahead.
- Codebase and staging review
- Findings feasibility assessment
- Implementation estimate
- Required before Remediation Support
- NDA required
- IAAP CPACC certified
A review identifies issues. The codebase determines what can be fixed — and how.
Accessibility findings describe what issues exist in the interface. They do not tell you which issues are straightforward to implement, which ones depend on third-party components or library constraints, which ones require a design or content decision before implementation can proceed, or which ones fall outside the scope of standard frontend remediation.
Those questions can only be answered by reviewing the actual codebase, staging environment, and component structure alongside the findings. Scoping Confirmation does that assessment and translates the findings into an implementation estimate that reflects the real technical context.
A codebase review that maps findings to implementation reality.
The scope of this service is agreed before the work begins. Depending on the project, the review may cover:
Codebase and repository structure
Understanding the overall structure, framework, component organization, and build setup relevant to the agreed scope.
Component, library, and framework identification
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.
Feasibility and difficulty assessment per finding
Cross-referencing each finding against the codebase to assess whether it is addressable, requires further confirmation, or falls outside standard remediation scope.
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.
The starting point depends on where your findings come from.
If findings are already available from a completed Sola Studio Accessibility Review, this service focuses on codebase assessment and estimate preparation. If you are bringing findings from another source, additional work is needed to read and interpret them before the codebase assessment can begin — which is why the starting point is higher. All prices are guide minimums; final pricing is confirmed at quote stage.
With Sola Studio Review
Following a completed Sola Studio Accessibility Review
Codebase and staging environment review to assess implementation feasibility of findings from a completed Sola Studio Accessibility Review, and an implementation estimate prepared on that basis.
DurationApprox. 1–2 weeksPriceFrom USD 900Included
- Codebase and repository structure review
- Component, library, and framework identification
- Staging environment and flow walkthrough
- Cross-referencing Sola Studio Review findings against the codebase
- Feasibility and difficulty assessment per finding
- Third-party dependency and external widget review
- Identification of items requiring client decisions
- Implementation estimate for Accessibility Remediation Support
Not Included
- Reading or interpreting external audit reports or third-party issue lists
- Code changes or Pull Request creation
- Accessibility Remediation Support implementation work
With Existing Findings
Bringing external findings or an existing issue list
Codebase and staging environment review to assess implementation feasibility of existing findings from an external audit, automated check results, or internal issue list, and an implementation estimate prepared on that basis.
DurationApprox. 2–4 weeksPriceFrom USD 2,000Included
- Reading and interpreting the provided audit report, issue list, or automated check results
- Assessment of finding specificity and implementation readiness
- Codebase and repository structure review
- Component, library, and framework identification
- Staging environment and flow walkthrough
- Cross-referencing provided findings against the codebase
- Feasibility and difficulty assessment per finding
- Third-party dependency and external widget review
- Identification of items requiring client decisions
- Implementation estimate for Accessibility Remediation Support
Not Included
- Code changes or Pull Request creation
- Accessibility Remediation Support implementation work
- Final pricing is confirmed at quote stage based on codebase complexity, number of flows and components in scope, volume and detail of existing findings, and access conditions.
- 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.
- NDA is required before this service begins. Codebase, staging environment, and other non-public materials will be accessed as part of the scoping process.
- Completing this service does not commit either party to proceeding with Accessibility Remediation Support. Fees for this service are not refundable if the client decides not to proceed.
- If existing findings are found to be insufficient, outdated, or missing implementation context during the scoping review, this will be communicated before the estimate is finalized.
What needs to be in place before this service can start.
This service involves access to non-public materials — codebase, staging environment, internal findings, and potentially customer-related information. The following must all be confirmed before work begins:
NDA signed
A non-disclosure agreement is required before this service starts. Codebase, staging environment, and other non-public materials will be accessed as part of the scoping process.
Findings shared
Findings must be available before the work begins — either a completed Sola Studio Accessibility Review, or an external audit report, issue list, or automated check results.
Codebase or staging access confirmed
Repository access, staging environment credentials, or equivalent access to the implementation context must be arranged before the work can start.
Target flows and components agreed
The scope of what will be reviewed — flows, pages, components — must be agreed before the work begins.
Payment completed
Payment is completed before the work starts. The quoted fee covers the scoping and assessment work itself and is not refundable if you decide not to proceed to Remediation Support.
Scoping done by the same person who will carry out the remediation.
The implementation estimate is prepared by the same person who reads the findings and carries out the frontend remediation work — which means the assessment reflects how the issues will actually be approached in implementation, not a generic feasibility judgment.
Yoko Shiina
Interface Clarity Consultant
Findings read in the context of real implementation
Experience working across React, Next.js, TypeScript, form flows, and component-based UI means findings are assessed against how frontend code is actually structured — not just against the issue description.
Honest about what falls outside standard scope
Third-party constraints, design decisions, and items that require separate handling are flagged clearly — so the estimate reflects what Remediation Support can actually cover, not an optimistic projection.
Continuity from scoping through to implementation
The person who confirms implementation feasibility is the same person who carries out the work. What was understood during scoping carries through to the remediation — without handoff loss.
IAAP CPACC
Accessibility knowledge is connected to practical frontend review, remediation, and site-improvement work.
“Her keen eye for design and user experience, combined with her frontend skills, made her a key contributor to our projects.”
S.R.N., Reference Letter
“Yoko is an avid learner who surpasses every challenge she encounters. Her React skills allowed her to build highly functional, responsive apps in no time—and her attitude enriched every team she joined.”
A.L., LinkedIn & Reference Letter
From inquiry to implementation estimate.
- 1
Submit an inquiry
Fill in the inquiry form with your current situation — existing findings, codebase context, and what you are hoping to confirm.
- 2
Receive a quote
Based on your inquiry, the applicable entry point (Sola Studio Review or existing findings) and service fee are confirmed and sent by email.
- 3
Complete payment
Payment is completed before the NDA is signed and before any non-public materials are shared.
- 4
Sign the NDA
A non-disclosure agreement is signed before codebase or staging access is shared.
- 5
Share access
Repository access, staging environment credentials, and the agreed findings are shared.
- 6
Scoping work
Codebase, staging environment, and findings are reviewed. Implementation feasibility is assessed per finding.
- 7
Implementation estimate shared
The completed implementation estimate is shared by email. This marks the close of the service.
FAQ
Is Scoping Confirmation required before Remediation Support?
Yes, in principle. Accessibility Remediation Support requires Scoping Confirmation to be completed first. The exception is if implementation scope, codebase context, and feasibility are already sufficiently clear from prior engagement — that is assessed case by case.
We have findings from another provider. Can we use those?
Yes. Bring your audit report, issue list, or automated check results. The starting price for external findings is higher than for a completed Sola Studio Review, because reading and interpreting those materials is additional work that needs to happen before the codebase assessment can begin.
What if the findings turn out to be insufficient during scoping?
If the provided findings are too broad, outdated, or missing the specificity needed to assess implementation scope, this will be communicated before the estimate is finalized. In some cases, an Accessibility Review may be needed before Scoping Confirmation can be completed.
What if we decide not to proceed to Remediation Support after this?
That is entirely up to you. The implementation estimate gives you a clear picture of what Remediation Support would involve. If you decide not to proceed, the fee for this service is not refundable — it covers the assessment work itself, regardless of what follows.
When does the NDA need to be signed?
Before the work begins. NDA signing happens after payment is confirmed and before codebase or staging access is shared. The sequence is: inquiry → quote → payment → NDA → access → work begins.
What kind of codebase access is needed?
Repository access is the most common setup — read access to the relevant parts of the codebase is usually sufficient. Staging environment credentials may also be needed. The access requirements are confirmed at the scoping stage based on the agreed scope.
Does completing Scoping Confirmation commit us to Remediation Support?
No. Scoping Confirmation produces an implementation estimate. Proceeding to Remediation Support is a separate decision, with its own scope confirmation, contract, and payment.
Get in touch to discuss the next step.
Share what findings you have — a completed Sola Studio Accessibility Review, an external audit report, an issue list, or automated check results.
The first step is to confirm what materials are available, what codebase access can be arranged, and which entry point applies to your situation.
Important information
- This page is a general service overview. Final scope, shared output, fees, timelines, responsibilities, payment terms, and contract terms are confirmed separately in writing before work starts.
- An inquiry, call booking, or discussion does not create a contract, confirmed booking, service commitment, or obligation for either party.
- Please do not share confidential information, source code, credentials, customer data, sensitive personal information, regulated data, or other non-public materials before an NDA or other agreed confidentiality arrangement is in place.
- Prices, timelines, availability, taxes, platform fees, bank charges, currency conversion, payment processing fees, withholding or deduction requirements, and other payment-related costs may be confirmed separately in the final quote, invoice, payment guidance, or contract.
- Accessibility Scoping Confirmation is a professional service provided on an asynchronous basis. It does not constitute legal advice, a formal accessibility audit, certification, or a guarantee of accessibility compliance.
- The implementation estimate covers the codebase and findings as reviewed within the agreed scope. Constraints or dependencies that only become visible during implementation will be confirmed with the client as they arise.
- Completing this service does not commit either party to proceeding with Accessibility Remediation Support. Fees for this service are not refundable if the client decides not to proceed.
- A non-disclosure agreement is required before this service begins. Codebase, staging environment, and other non-public materials will be accessed as part of the scoping process.
- Code changes, pull requests, and implementation work are not included in this service. They are handled separately through Accessibility Remediation Support.