About
Build Components is a catalogue of accessible UI parts you set up on the page and take home as plain code.
Why it exists
The parts people most often get wrong are the ones that look simple: a date picker, a combobox, a mega menu, a basket. Getting their keyboard support, focus handling and screen reader output right takes days. Each part here does that work once, follows the matching WAI-ARIA Authoring Practices pattern, and is tested before it reaches you.
How it differs from a component library
- Your options are baked in. Labels, behaviour, add-ons and colours are written into the file you take, so there is nothing to wire up afterwards.
- Every output from one set of options. React + Tailwind CSS v4; HTML, CSS and JavaScript with no build step; and Vue, Svelte, Astro, Angular, Solid and Web Component files built on that plain output (the Vue and Svelte files tested server-rendered too, as Nuxt and SvelteKit run them).
- The exported code is what gets tested. Not a demo: the same axe, keyboard and browser tests run on every output.
- No runtime dependency. Copy the files, or install them with the shadcn CLI. Nothing is loaded from this site afterwards.
What is in stock
137 parts today, from form controls to navigation and overlays. Browse the catalogue, or read how they are checked in the accessibility statement.
Who makes it
Built by Adesh Shukla, a UI developer, as part of devstash.me. Found a bug or want a part that is not here? Get in touch through devstash.me.
What we count
How many times each part and template is installed, downloaded or copied, a total per month, to decide what to build next. Nothing about who: no cookies, no addresses, nothing about your browser or device.