Building for the Accessible Web

The web was designed to be universal. Yet too often, we build experiences that exclude millions of users. At Purizu, we're committed to changing this — one component at a time.

Our Technical Stack

We build with Next.js, React, and TypeScript — a modern stack that gives us the power to create performant, accessible applications. But the tools are only part of the equation. What matters is how we use them.

Every component we build is tested against WCAG 2.1 AA standards. We use automated testing tools, but we also conduct manual testing with screen readers and keyboard navigation. No automated tool can catch everything.

Component Architecture

Our component library is built on Radix UI primitives, which provide excellent accessibility out of the box. We extend these with our own styling and behavior while preserving their accessible foundations.

• Semantic HTML as the foundation of every component
• ARIA attributes used correctly and sparingly
• Keyboard navigation support for all interactive elements
• Focus management for complex interactions like modals and dropdowns
• Reduced motion support for users who prefer it

Performance Is Accessibility

A slow website is an inaccessible website. Users on older devices, slower connections, or with cognitive disabilities are disproportionately affected by poor performance. That's why we treat performance as an accessibility concern.

We use static rendering where possible, optimize images aggressively, and keep our JavaScript bundles lean. Every millisecond matters.