React Sites with Chakra UI: Accessible Components & Dark Theme
You integrate a third-party design system into a React app and end up with inconsistent HTML/CSS classes, a broken dark theme, and inaccessible interactive elements. We've encountered this on dozens of projects, so for clients who prioritize accessibility and rapid prototyping, we recommend Chakra UI. With 5+ years in web development and 50+ React projects, we've refined an approach where a landing page takes 1–2 days to build, not a week. Savings on layout costs reach 30% thanks to ready-made components—confirmed by client feedback.
Chakra UI is not just another UI library; it's a system where every component meets WCAG 2.1 out of the box. The Style Props API lets you manage CSS directly in JSX, eliminating extra files. The built-in dark theme uses semantic tokens that automatically switch colors without a rebuild. For example, in one project we replaced 500 lines of CSS variables with 20 lines of tokens—the dark theme worked flawlessly with zero bugs.
How Chakra UI Solves the Dark Theme Problem
Before Chakra UI, developers stored color variables in CSS and manually swapped them via [data-theme="dark"]. In Chakra v3, the dark theme is a built-in feature: you define a token's dark color using _dark. The provider automatically reads the data-theme attribute on <html> and applies the correct palette. Configuration example:
import { createSystem, defaultConfig, defineConfig } from '@chakra-ui/react';
const customConfig = defineConfig({
theme: {
tokens: {
colors: {
brand: { 500: { value: '#3b82f6' } },
},
},
semanticTokens: {
colors: {
'bg.canvas': { value: { base: '#f9fafb', _dark: '#0f172a' } },
},
},
},
});
const system = createSystem(defaultConfig, customConfig);
export default system;
Now a component like Box bg="bg.canvas" adapts to the theme automatically. No media queries, no class toggles. The maintenance cost of such a theme is 2–3 times lower compared to custom solutions.
Why Chakra UI is Faster Than Material-UI for MVPs
| Parameter |
Chakra UI (v3) |
Material-UI (MUI) |
| Style props |
Yes, built-in |
Via sx prop, more boilerplate |
| Dark theme |
Tokens + _dark, 5 minutes |
Themes via ThemeProvider, ~15 minutes |
| Accessibility |
WCAG AA out of the box |
Partial, requires extra work |
| Bundle size |
~25 kB gzip |
~40 kB gzip |
| Responsiveness |
Objects in props: w={{ base: 'full', md: '50%' }} |
Via useMediaQuery or breakpoints in sx |
Chakra UI wins in prototyping speed: 2–3 times less code for responsive grids and forms. Additional savings come from the built-in token system that eliminates style duplication.
Chakra UI v2 vs v3 Comparison
| Feature |
Chakra UI v2 |
Chakra UI v3 |
| Provider |
ChakraProvider + ColorModeScript |
Single ChakraProvider with config |
| Tokens |
CSS variables + useColorMode |
Semantic tokens with _dark |
| Style props |
Via chakra factory |
Built into all components |
| Size |
~30 kB gzip |
~25 kB gzip |
Migrating from v2 to v3 requires updating the provider and replacing useColorMode with _dark tokens, but pays off through simplified architecture.
How to Set Up a Chakra UI Theme in 3 Steps
-
Install the package:
npm install @chakra-ui/react @emotion/react.
-
Create a configuration in a separate file (as in the example above), define base tokens and semantic tokens for the dark theme.
-
Connect the provider at the root of your app:
import { ChakraProvider } from '@chakra-ui/react';
import system from './theme/system';
function Root() {
return (
<ChakraProvider value={system}>
<App />
</ChakraProvider>
);
}
After that, style props and automatic dark theme support are available in all components.
Hero Section with Style Props
Style props are the key to speed: responsive padding is set via an object py={{ base: '12', md: '20', lg: '28' }}. The entire section is written in one JSX block:
import { Box, Flex, Heading, Text, Button, Stack } from '@chakra-ui/react';
const Hero = () => (
<Box as="section" bg="bg.canvas" py={{ base: '12', md: '20' }}>
<Flex maxW="7xl" mx="auto" direction={{ base: 'column', lg: 'row' }}>
<Box flex="1">
<Heading as="h1" size={{ base: '2xl', lg: '4xl' }} color="text.primary">
Product Title
</Heading>
<Text fontSize={{ base: 'md', lg: 'lg' }} color="text.muted" mb="8">
Value proposition
</Text>
<Button colorPalette="brand" size="lg">Get Started Free</Button>
</Box>
</Flex>
</Box>
);
Card Grid and Form with Validation
For cards, use SimpleGrid, which automatically adjusts columns based on breakpoint. Forms use standard Field + Input, validation via React Hook Form and Zod:
import { Field, Input, Button, Stack } from '@chakra-ui/react';
import { useForm } from 'react-hook-form';
import { z } from 'zod';
const schema = z.object({ name: z.string().min(2) });
const Form = () => {
const { register, handleSubmit, formState: { errors } } = useForm({ resolver: zodResolver(schema) });
return (
<Stack gap="5">
<Field.Root invalid={!!errors.name}>
<Field.Label>Name</Field.Label>
<Input {...register('name')} />
{errors.name && <Field.ErrorText>{errors.name.message}</Field.ErrorText>}
</Field.Root>
<Button type="submit">Submit</Button>
</Stack>
);
};
Color Mode via Semantic Tokens
In Chakra v3 you don't need to change CSS—just use the useColorMode hook. A toggle button example is described above. To save space and reduce code redundancy, we often extract toggle logic into a separate hook. We guarantee that every component passes Core Web Vitals testing: bundle optimization, lazy-loading icons, and eliminating N+1 requests.
Common Mistakes When Building with Chakra UI
- Using
!important—overriding tokens via the css prop breaks the system.
- Omitting
_dark in semantic tokens—dark theme won't appear.
- Missing
base breakpoint—responsiveness breaks on mobile.
- Ignoring the
as prop—semantic markup is broken.
- Direct DOM manipulation instead of state—Chakra UI components are reactive.
What's Included in Our Chakra UI Layout Work?
We deliver not only finished code but also documentation on tokens, components, and color schemes. Deliverables include:
- Configured Chakra UI theme with semantic colors and fonts
- All project pages adapted for mobile and desktop breakpoints
- Forms with validation (React Hook Form + Zod)
- Style documentation (Storybook or Markdown)
- Access to repository with commit history
- Team training (1–2 hours) on style props and theme configuration
Contact us—we'll propose a turnkey solution with Chakra UI. Savings on layout costs reach 30% thanks to ready-made components and no custom CSS classes.
Timelines and Cost
Estimated timelines:
- System and theme setup: 3–4 hours
- Landing page: 1–2 days
- Product site (5+ sections, form, dashboard): 4–7 days
Final cost is calculated individually. Book a consultation to get an accurate estimate. Each client has a single manager and full technical oversight (certified specialists, 5+ years of React experience).
Do you have a React project needing dark theme and accessibility? Get a turnkey solution with Chakra UI—reach out to us.
Frontend Development with React: From Audit to Production
Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.
Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.
Why is Next.js the Standard Choice for SEO?
React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.
But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.
How Does TypeScript Prevent Bugs in Production?
TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.
Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.
Vue 3 + Nuxt 3 — An Alternative SSR Stack
Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.
Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.
Performance: Metrics and Tools
Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.
Dynamic imports for heavy components:
const RichEditor = dynamic(() => import('@/components/RichEditor'), {
ssr: false,
loading: () => <EditorSkeleton />,
});
Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.
Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.
State Management: Without Overengineering
For most applications, it's enough to have:
-
React Query / TanStack Query — for server state (API data, caching, invalidation)
-
Zustand — for global client state (lightweight, no Redux boilerplate)
-
React Hook Form — for forms
Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.
How to Choose the Right CSS and Design System?
Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.
React DevTools Profiler — the official tool from the React team.
Testing
| Level |
Tool |
What We Test |
| Unit |
Vitest |
Utilities, hooks, pure functions |
| Component |
Testing Library |
Render, interactions |
| E2E |
Playwright |
Critical user flows |
| Visual |
Chromatic (Storybook) |
UI regression |
E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.
What's Included in the Scope (Deliverables)
Every frontend project we deliver includes:
-
Source code in Git with full commit history and branching strategy
-
Architecture document — component tree, data flow, routing decisions
-
Component documentation – Storybook with stories for all reusable components
-
CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
-
Access to staging environment during development and after launch
-
Team training – 2‑3 live walkthrough sessions with your developers
-
3‑month warranty on any bugs found in production
-
Performance report – LCP, TTI, TTFB, bundle size before/after
We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.
Estimates and Scope
| Task |
Timeline |
| SPA (dashboard, CRM interface) |
8–16 weeks |
| Next.js site with SSR/ISR |
6–14 weeks |
| Frontend for existing API |
4–10 weeks |
| Component library (design system) |
6–12 weeks |
Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.
What Does a Typical Performance Audit Reveal?
A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.
Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.
We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.
What Stack to Choose for Frontend Development with React?
We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.
Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.
