Interface clarity, frontend implementation, and accessibility support for international teams.
Sola Studio is an independent practice for international teams working across interface clarity and UX review, frontend implementation, and accessibility support.
The work is shaped around clear scope, written context, and practical handoffs — designed to make the next step easier to discuss, prioritize, and act on.
An independent practice for interface clarity, frontend implementation, and accessibility-aware support
Many product issues do not sit in one layer only — a screen-level problem may involve frontend patterns, interface behavior, accessibility, data flow, or unclear assumptions about what users need before acting. Sola Studio works across those boundaries to make friction easier to locate, explain, and prioritise.
The work looks beyond whether a screen or flow exists, and asks whether users can understand it, trust it, and move through it with enough confidence to act.
Yoko Shiina
Independent Frontend Consultant
Interface Clarity / Frontend / Accessibility
Yoko Shiina — UX-aware, frontend-grounded, and implementation-focused
I help international teams connect interface clarity, frontend implementation, accessibility, and the practical decisions that sit between them.
I work as an independent frontend consultant and engineer, mainly with React, Next.js, TypeScript, API integration, and accessible web development.
Before specializing in frontend engineering, I worked across advertising, customer-attraction strategy, web production, information architecture, and client-facing project work. In that earlier work, I learned to connect business goals, local context, audience behavior, wording, and what people need before they decide to act.
I have worked across B2B SaaS, internal tools, dashboards, Web3 learning products, distributed product teams, and international working environments including Japan, remote teams, and Malta.
That mix of experience shapes the way the work connects across different teams, contexts, and market assumptions — understanding what users need before they act, how information order affects decision-making, and what trust signals matter in a given context.
Sola is the studio name. In business-facing contexts, external records, and professional profiles, you may also see my full name, Yoko Shiina.
A few things to know
- in web-related work
- 10+ years
- frontend-focused engineering
- React / Next.js / TypeScript
- accessibility certification
- IAAP CPACC
- working across implementation, interface clarity, and accessibility in one practice
- Frontend + UX + Accessibility
Structured collaboration for distributed frontend and product work
Remote collaboration works best when communication is clear by design.
The work is structured around written handoffs, defined scope, visible decisions, and check-ins at agreed times.
This setup works well for teams that already use tickets, async updates, documentation, and structured delivery habits.
- Async-friendly collaboration
- Clear context, rationale, and next steps
- Comfortable with agile workflows, tickets, and iterative delivery
The technical base behind the work
The work is grounded in frontend implementation and practical product delivery, while staying connected to UX, accessibility, and product decisions.
Frontend
- JavaScript10+yrs
- TypeScript4.5yrs
- React5yrs
- Next.js3.5yrs
- HTML510+yrs
- CSS310+yrs
Backend / Data
- Ruby1yrs
- Ruby on Rails1.5yrs
- Java0.5yrs
- Supabase3.5yrs
- API連携4.5yrs
- DB設計1.5yrs
- SQL1.5yrs
State & Data
- REST APIs4yrs
- Redux2yrs
- Zustand0.5yrs
- Context API2.5yrs
UI
- Material UI2.5yrs
- Tailwind CSS3yrs
- SCSS4yrs
- Storybook1.5yrs
- Figma4yrs
- Sketch2yrs
Testing
- Jest4yrs
- React Testing Library4yrs
- Cypress0.5yrs
- Playwright0.5yrs
Public tools from Sola Studio
Sola Studio also creates public tools shaped by practical work across frontend implementation, accessibility, UX clarity, and product-facing workflows.
Some tools help with faster interface checks, some support practice or preparation, and others make practical decisions easier to handle. They are built from real questions that come up in day-to-day work.
How this work took shape
Client-facing foundation
From client strategy and web production
Earlier work in advertising and customer-attraction strategy in Tokyo shaped the way I look at audience, local context, business goals, wording, and what people need before they decide to act. That work later connected into web production, information architecture, wireframes, and client-facing project work.
This became the foundation for connecting business context, user expectations, language, trust signals, and how information is presented in product and service interfaces.
Engineering transition
Into software engineering and distributed collaboration
Through Microverse and remote engineering work, I moved further into software development through distributed teamwork, pair programming, peer review, and collaboration across regions and time zones.
This shaped the way I work with written communication, peer review, async collaboration, and distributed teams.
Product engineering
Frontend work across SaaS, internal tools, and MVPs
Recent work includes B2B SaaS, internal tools, dashboards, Web3 learning products, API collaboration, data flow, and frontend implementation in async teams.
This is where the current Sola Studio focus became clearer: product-facing frontend work that connects implementation with usability, accessibility, component behavior, and team decision-making.
International context
Working and living across multiple environments and contexts
Through international teams, remote collaboration, and life in Malta, I learned to see product, communication, and interface assumptions from both inside and outside a given context.
This shaped a way of seeing interfaces and communication from multiple contexts — useful when the work involves teams, users, or product decisions that span different market and cultural assumptions.
Sola Studio
Independent frontend and product support
Sola Studio brings these threads together: interface clarity and UX review, frontend implementation, accessibility review and remediation, and structured collaboration for teams that need practical support.
The work is designed for teams that need someone who can see across screens, copy, implementation, and accessibility — and help clarify what the practical next step should be.
Credentials and technical foundation
These credentials support the main areas of Sola Studio's work with international teams: interface clarity and UX review, frontend engineering, accessibility, product collaboration, and structured delivery.
- IAAP CPACC2025-11
Accessibility foundation across disability types, standards, inclusive design, and organizational accessibility practice.
- Certified ScrumMaster®2025-02
Scrum, team collaboration, sprint-based work, retrospectives, and delivery process awareness.
Product ownership, prioritization, backlog thinking, and product value decisions.
- Google UX Design Certificate2025-04
User-centered design, UX research basics, information architecture, prototyping, and design iteration.
Remote software development training with pair programming, code review, and international collaboration.
Software design fundamentals, maintainability, and object-oriented design thinking.
Additional credentials and professional history are available on LinkedIn. LinkedIn
What people say about working with me
Selected recommendations from people I have worked with across engineering, product, and project settings.
"Yoko’s projects were consistently high quality and often ahead of schedule. She combines best practices with creative problem solving, and uplifts everyone around her."
"She possesses a rare combination of technical prowess and language proficiency. Her adaptability and contribution to our TypeScript/React projects were invaluable."
"Her keen eye for design and user experience, combined with her frontend skills, made her a key contributor to our projects."
"She breaks down complex topics into simple steps and completes projects ahead of schedule. Her working style makes collaboration smooth and effective."
Writing on UX, accessibility, frontend work, and product friction
Writing is one way Sola Studio makes its thinking visible — observing the gaps, frictions, and language choices that shape how digital services are understood and used.
Some essays have also been Medium Boosted or featured by UX publications.
Selected Medium essayMedium BoostedFeatured by UX CollectiveThe UX Lesson I Learned in a Quiet Tokyo SalonA personal essay about turning local observation and a salon owner’s quiet vision into customer-facing messaging — an early lesson in emotional insight, trust, and UX before the term “UX” entered the frame.
human-centered designemotional designstorytellingux design
Selected Medium essayFeatured by UX CollectiveFrom Universal Design to Personalized Interfaces — Rethinking AccessibilityAn essay questioning whether “one interface for everyone” is enough for real inclusion, and exploring how accessibility, Universal Design for Learning, and adaptive UI can point toward more personalized digital experiences.
inclusive designuniversal designuxaccessibility
UX Lens field noteSola Journal / UX LensCasual Chat, Serious CancellationA cancellation chat felt lightweight, but lacked the confirmation and traceability needed for a higher-stakes service request.
customer supportcancellation flowconfirmation & traceability
Who this is built for
A good fit for teams that need:
- screens, flows, or copy that are not working as clearly as they should — and need structured review before moving into implementation
- frontend implementation support without opening a full-time role
- accessibility review and scoped frontend remediation support, especially for forms, flows, and component-based UI
- someone who can work across UI, code, API collaboration, and product clarity
- clear written communication and structured async collaboration
- independent senior-level support rather than a large agency setup
Better handled elsewhere if you need:
- a large agency team with multiple roles bundled together
- brand identity or visual design as the primary scope
- backend infrastructure ownership
- constant real-time availability as the main working model
- individual coaching, mentoring, or personal support services
- full-service localization delivery or professional translation production as the primary scope
Have an interface clarity, frontend,
or accessibility question?
Some projects start with a clear implementation need.
Others start with a pattern the team can already sense but has not fully mapped yet: a confusing flow, an unclear decision, a screen or flow that does not yet feel ready, or a gap between what the interface says and what users need to understand.
The first step is to make the situation easier to read together,
then identify what is worth considering next.