Interfaces Your Users Will Not Fight

Yes, in two ways. Outside the platform as a standalone app authenticating via OAuth and calling the REST API - suitable for customer-facing portals. Or inside Salesforce, though there Lightning Web Components are usually the better choice since they are native to the platform. We will tell you which pattern fits your requirement.

If the application has public pages that need to rank in search, or you want server-side rendering for first-load performance, then yes. For an authenticated internal tool behind a login, plain React with Vite is simpler and has less operational overhead. Next.js is excellent but brings a hosting and rendering model you should choose deliberately.

Semantic HTML first, ARIA only where semantics genuinely fall short, and testing with keyboard navigation and a screen reader as part of each slice. We check contrast and focus management explicitly. Retrofitting accessibility after a build is several times more expensive than building it in.

Yes, and it is a common arrangement. We can lead the architecture and hand over progressively, or supplement an existing team on specific workstreams. Where we are handing over, we build the component library and documentation from the start rather than at the end.