Web development and accessibility remediation — as an external partner.
Two services for client delivery: website, ecommerce and frontend development, and accessibility remediation for audited projects. Both can be arranged to fit within your existing delivery process.
Services overview
Web development within your client delivery process.
Sola Studio supports client projects across website, ecommerce and frontend implementation, working within your team’s existing delivery process.
Websites and ecommerce experiences for client projects.
Build new websites, stores, product and campaign pages, or improve existing experiences across WordPress, Shopify, HTML, CSS and JavaScript.
Websites
Build new pages or improve an existing website using HTML, CSS, JavaScript and WordPress.
- Business and brand websites
- New pages and website sections
- WordPress development and customisation
- Responsive implementation
- Navigation, forms and calls to action
- Updates and improvements to an existing site
Ecommerce
Develop and improve the pages customers use to discover, understand and purchase products.
- Shopify theme and page customisation
- Ecommerce storefront improvements
- Product and collection pages
- Product information and page structure
- Promotional content and landing pages
- Mobile and interaction improvements
Campaigns and ongoing improvements
Deliver campaign pages and continue improving the website as client needs change.
- Campaign and landing pages
- Pages connected to advertising or social activity
- New content and promotional updates
- Interface and customer journey improvements
- Pre-launch checks
- Ongoing website and ecommerce implementation
The exact scope, deliverables and responsibilities are agreed for each engagement.
Available as a defined project or ongoing support.
Project-Based
Individually quoted
For a defined website, page, campaign or improvement project. Pricing is confirmed based on the agreed scope, requirements, timeline and delivery needs.
Ongoing Support
Reserved monthly capacity.
Reserved monthly capacity.
A fixed number of development hours is reserved each month for ongoing frontend development work. Choose 32, 64, 96 or 128 hours, depending on the amount of support you need.
| Monthly capacity | Weekly workload equivalent | Hourly rate | Monthly fee |
|---|---|---|---|
| 32 hours / month | Approx. 7 hours per week | EUR 68 | EUR 2,176 / month |
| 64 hours / month | Approx. 15 hours per week | EUR 65 | EUR 4,160 / month |
| 96 hours / month | Approx. 22 hours per week | EUR 62 | EUR 5,952 / month |
| 128 hours / month | Approx. 30 hours per week | EUR 60 | EUR 7,680 / month |
Period and termination
You can start with the smallest capacity — 32 hours — for the first month. The initial term is one month, with no automatic renewal. If both sides want to continue, the next month's capacity and terms are confirmed before the term ends, and the engagement then renews monthly. Ending or reducing capacity needs notice — 14 days in the first six months, 30 days after that.
Frontend implementation for client projects and development teams.
Build features, improve interfaces and contribute to existing React, Next.js and TypeScript products and codebases.
Product and feature implementation
Build new frontend functionality or contribute to an existing product and codebase.
- Frontend implementation
- New UI features and components
- Implementing defined screens and user interactions
- Working within an existing component system
- New frontend builds where the requirements and implementation inputs are sufficiently defined
The work can involve React, Next.js, TypeScript, JavaScript, HTML/CSS, Tailwind and Material UI.
UI and code improvements
Improve existing frontend experiences and the code supporting them.
- UI improvements
- Refactoring
- Reusable component improvements
- Code review
- Clarifying screen states, behaviour and edge cases during implementation
- Improving consistency across related interfaces
Working within an existing codebase
Contribute within established codebases, development workflows and code conventions.
- Coordinating with existing engineers, designers and vendors
- Working with established development workflows and code conventions
- Raising implementation questions as they arise
- Helping turn specifications and designs into working frontend behaviour
The exact scope, deliverables and responsibilities are agreed for each engagement.
Available as a defined project or ongoing support.
Project-Based
Individually quoted
For a defined frontend feature, interface, improvement or delivery period. Pricing is confirmed based on the agreed scope, requirements, timeline and delivery needs.
Ongoing Support
Reserved monthly capacity.
Reserved monthly capacity.
A fixed number of development hours is reserved each month for ongoing frontend development work. Choose 32, 64, 96 or 128 hours, depending on the amount of support you need.
| Monthly capacity | Weekly workload equivalent | Hourly rate | Monthly fee |
|---|---|---|---|
| 32 hours / month | Approx. 7 hours per week | EUR 75 | EUR 2,400 / month |
| 64 hours / month | Approx. 15 hours per week | EUR 72 | EUR 4,608 / month |
| 96 hours / month | Approx. 22 hours per week | EUR 68 | EUR 6,528 / month |
| 128 hours / month | Approx. 30 hours per week | EUR 65 | EUR 8,320 / month |
Period and termination
You can start with the smallest capacity — 32 hours — for the first month. The initial term is one month, with no automatic renewal. If both sides want to continue, the next month's capacity and terms are confirmed before the term ends, and the engagement then renews monthly. Ending or reducing capacity needs notice — 14 days in the first six months, 30 days after that.
Clear roles within your delivery process.
Roles and delivery
Your team
Your team sets priorities and remains responsible for the end-client relationship, project scope and approvals.
Sola Studio
Sola Studio carries out the agreed development work within your delivery process, raises implementation questions through your team’s channels and can join end-client meetings where agreed.
- Working language: English.
- Meetings, reviews and coordination count towards the agreed project scope or reserved monthly capacity.
- Unless separately agreed, visual and brand design, backend and infrastructure work, and overall project management remain outside the service.
Availability and communication
Current availability is confirmed at the time of inquiry.
Work is fully remote and async-first, with overlap with European business hours. Meetings are scheduled, and messages are handled on a business-day basis.
Accessibility remediation for your audited projects.
Accessibility remediation for issues identified through a formal audit. Sola Studio works from existing findings to implement the identified fixes across forms, keyboard interaction, focus behaviour, semantic structure, ARIA, and component states.
Two engagement routes
The process depends on who contracts Sola Studio.
Engage Sola Studio as a subcontractor
Your organisation contracts Sola Studio directly to implement accessibility fixes based on formal audit findings. The work is delivered in stages within your existing audit and delivery process, with each stage scoped and agreed in advance and billed for the actual hours worked.
Refer an end client
If you prefer to introduce an end client, the client can contract and work with Sola Studio directly. Sola Studio's end-client accessibility process applies, beginning with Accessibility Scoping Confirmation before any remediation work is agreed.
What the work starts from
The work starts from a formal accessibility report or equivalent documented findings. The findings should identify the affected interface, expected outcome, and relevant test context clearly enough to guide the remediation work.
Automated scan results, internally collected notes, or developer tickets can provide useful context — the formal report remains the starting point for the work.
What the remediation typically starts from
- Audit report or documented findings
- Access to the relevant codebase
- A staging or equivalent review environment
- Target standard and relevant browser or assistive-technology context
- Known project, design, or technical constraints
A typical remediation workflow
Stages, handoff points, and review arrangements can be adapted to fit your existing audit and delivery process.
- 01
Findings and project access
Your team shares the formal audit findings, relevant codebase, review environment, target standard, known constraints, and expected timeline. Sola Studio reviews the material and raises any points for clarification before the remediation begins.
- 02
Stage scope and agreement
Before work begins, we agree which findings the initial stage will cover — for example, starting with the highest severity issues, or focusing on a specific component or page type. We also confirm known assumptions and constraints, decision boundaries, and the handoff method. If further work follows the review, we agree how to scope and group it as the next practical stage.
- 03
Remediation, review, and handoff
Sola Studio implements the initial fixes. When that initial body of work is complete, it is handed back for review with notes on what changed, what was checked, any unresolved questions, and the actual hours worked. If the review confirms that the issues are resolved, the remediation may finish at this point.
- 04
Stage completion and further work
An invoice is issued for the actual hours worked when a stage reaches its agreed completion point. If review identifies related follow-up adjustments, they can be grouped as a further stage and handled until a sensible completion point, rather than invoiced one by one. Additional stages may also be agreed if new or unexpected work arises, or where your review process creates another natural work boundary. Final verification and, where applicable, certification follow your team’s process.
Pricing and billing
Standard rate
EUR 70 / hour
Project-based accessibility remediation is billed for the actual time worked in each agreed stage.
Actual hours, not a fixed fee
Each stage is billed for the actual hours worked, not a fixed fee.
Invoice at stage completion
An invoice is issued when an agreed stage reaches its completion point. Related follow-up adjustments are not normally invoiced one by one; they can be grouped into a stage and invoiced when that group of work reaches a sensible completion point.
Early notice
If the work is taking significantly longer than expected, Sola Studio will raise this before continuing.
Payment can be handled through Stripe or Deel. If your organisation uses a different contractor, purchasing, or payment process, this can be discussed before the project begins.
Responsibilities and review
Responsibilities are agreed for each project. This is the typical division of work when Sola Studio joins your delivery process as a remediation subcontractor.
Sola Studio
- Carry out the agreed frontend remediation.
- Make decisions about the fixes within the agreed boundaries and raise decisions that affect product behaviour or fall outside them.
- Check the fixes in the environments available to Sola Studio.
- Share what was changed, what was checked, and any unresolved items at handoff.
- Raise unexpected technical constraints or scope changes early.
Your team
- Provide audit findings and relevant project context for the remediation work.
- Review or re-test changes after handoff.
- Manage final verification and the end-client relationship.
Checks on the fixes
Checks typically include automated testing, manual keyboard review, and basic screen reader checks in the environments available to Sola Studio. For issues specific to Windows, Android, or another unavailable setup, Sola Studio can work from the audit findings, with verification by your team or nominated reviewer in the relevant environment.
Discuss accessibility remediation
If you have accessibility findings that need remediation support, share a brief overview of the findings, technology, expected timeline and review process. Detailed reports and project access can be arranged after the initial fit and confidentiality requirements are confirmed.
Please do not send confidential audit reports, source code, or credentials with the initial inquiry.
Building a partner network for future projects? You are welcome to get in touch even if you do not have an active project yet.
Project-based work or ongoing support.
The appropriate model can be confirmed after the work and expected level of support are discussed.
Project-Based
For a specific client project or defined body of work. Scope, responsibilities, timing and pricing are agreed before the relevant work begins. An engagement may include more than one agreed stage.
Ongoing Support
For recurring development or remediation across one or more client projects. A fixed amount of capacity is reserved each month, with work prioritised within the agreed capacity and working arrangement.
Who you'd be working with
I'm Yoko Shiina, an independent contractor operating under Sola Studio. I work within existing teams and delivery processes, taking ownership of agreed web development and accessibility remediation work while raising questions early when requirements, designs, behaviour or technical specifications need clarification. I'm a Certified ScrumMaster and Certified Scrum Product Owner, and I hold the Certified Professional in Accessibility Core Competencies (CPACC) credential.
Setup
Contracting, payment, access, and working arrangements are confirmed before an engagement begins.
Contracts and payment
Agreements and contractor route
Your standard subcontractor or framework agreement can be used as a starting point. If you do not have one, Sola Studio can prepare a simple draft for review.
Your organisation can contract Sola Studio directly. Deel can also be used if you prefer to manage a cross-border contractor agreement, payments, and tax documentation in one place.
Payment methods
Stripe and Deel are available.
Stripe
Pay by credit or debit card through a payment link.
Deel
Contract and payment in one place, with bank transfer available.
Currency
Standard prices are set and quotes are normally issued in EUR. Payment may be made in EUR, GBP, USD, JPY, or another agreed currency. For a quote issued in EUR, if payment in GBP, USD, JPY, or another currency is preferred, the invoice amount is converted from the quoted EUR amount using the exchange rate in effect on the invoice date. Quotes are normally valid for 14 calendar days unless a different period is stated.
Where required by your organisation's purchasing or contracting process, a different quote currency may be agreed in advance. In that case, the accepted quote currency and amount also apply to the invoice.
Taxes and payment fees
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.
Billing schedule
| Service | Timing | Detail |
|---|---|---|
| Web Development Partner — Project-Based | As agreed for the project | Fees and payment timing are confirmed in the applicable quote, contract, SOW, or individual agreement. |
| Web Development Partner — Ongoing Support | Monthly in advance | Reserved monthly capacity is generally invoiced and paid in advance. |
| Accessibility Remediation — Project-Based | At the completion of each agreed stage | Actual hours are invoiced at stage completion. |
A different billing cycle can be discussed where required by your organisation’s purchasing or compliance process.
Project setup
Confidentiality
Confidentiality can be covered by your main agreement or by a separate NDA. A template is available if needed.
For accessibility remediation, appropriate confidentiality terms are agreed before detailed audit findings, source code, or project access are shared.
Environment and access
I work on a MacBook Pro running macOS.
Any project-specific environment, dedicated account, security setup, or client-managed device requirements are confirmed before work begins.
Tools and communication
GitHub, Slack, and Figma are the usual baseline.
I can also work within your existing tools for tickets, documentation, and communication, including Jira, Linear, Notion, or similar platforms.
Ongoing Support terms
Initial term and renewal
The initial Ongoing Support term is one month and does not renew automatically. Continuation for the following month is normally confirmed by both sides no later than 10 business days before the initial term ends and remains subject to availability. If continuation is agreed, the engagement renews monthly. Ending the engagement or reducing monthly capacity requires 14 days' notice during the first six months and 30 days' notice after that. Notice received after the applicable deadline takes effect from the following renewal date.
Not sure where to start?
If you're not sure which service fits, want to talk through a specific project, or are building a network of trusted partners for future needs — feel free to reach out at info@solastudio.studio or via the options below.