Become a sponsor to Sinisa Kusic

Who I am

I am Sinisa Kusic, a senior frontend engineer based in Rijeka, Croatia, with 18+ years of professional experience building production systems in React, Next.js, and TypeScript. My focus is on frontend architecture, accessibility, and long term maintainability, not on shipping the trendy thing of the month.

What your sponsorship supports

This profile funds my ongoing open source work. The same standard runs through all of it: accessibility and semantic correctness are not optional, simple solutions beat clever ones, and production quality is the baseline rather than the goal.

Current projects:

• nuka-ui, an accessibility-first React UI library available on npm as @nuka-ui/core. https://github.com/ku5ic/nuka-ui
• Foxhole, a frontend audit tool available on npm as @ku5ic/foxhole. It ships as both a CLI and an MCP server, auditing URLs, local builds, and SPA route lists for accessibility violations, performance regressions, semantic HTML issues, and bundle problems, then emitting structured output for both human-readable reports and AI agents. The CLI and MCP server are open source and free. https://github.com/ku5ic/foxhole

More projects will land here over time. Sponsorship supports the work across all of them rather than any single repository.

Concretely, sponsorships go toward:

• Bug fixes and issue triage
• WCAG 2.2 AA conformance work
• Documentation and usage examples
• Keeping each project current with React, TypeScript, and modern tooling
• New components, checks, and features driven by real user needs, not roadmap theater

Why this matters

Most tooling treats accessibility as a checkbox. I treat it as a correctness requirement, the same way I treat type safety or test coverage. If a component has the wrong ARIA semantics, it is broken, not "almost ready." If an audit tool misses a real violation or cries wolf on a false one, it is not doing its job. That standard takes time, and sponsor support is what makes it possible to hold the line instead of cutting corners under delivery pressure.

Who should sponsor

• Individual developers who use these projects and want them to keep improving
• Companies shipping products on top of the libraries and tools who rely on stable releases
• Peers and clients who value accessibility and semantic correctness as first-class engineering concerns

What sponsors get

Every sponsor helps keep this work sustainable. Beyond that, the practical benefit is simple: maintained projects, responsive issue handling, and a maintainer who takes production quality seriously.

If you represent a company with specific needs around accessibility, component architecture, frontend auditing, or migration work, reach out directly and we can talk about what a larger sponsorship unlocks.