Measured entry
efferd-faqs-3
faqminimal-flatmotion on file
A full-height FAQ section that pairs introductory copy with a single-open accordion, switching from a split layout to a stacked one on smaller screens. It ships as a shadcn registry block and depends on Tailwind theme classes, the local accordion component backed by Radix UI, Lucide icons, and the usual path aliases and class-name utility.



Measured
Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.
| Build | OK |
|---|---|
| Mount | OK |
| Console errors | 0 |
| Uncaught page errors | 0 |
| Horizontal overflow | clean at 375, 768, 1440 |
| Axe critical | 0 |
| Axe serious | 0 |
| Axe moderate | 0 |
| Axe minor | 0 |
| Gzip marginal | 39.8 KB (105.2 KB build, 65.4 KB baseline) |
| Bare mode | FAIL |
| Provider required | NO |
| Demo used | written from the component source API |
What the harness recorded
BARE BUILD
✗ Build failed in 1m 24s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/components/ui/accordion.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A solid, restrained FAQ block with responsive composition, working accordion behavior, and no observed accessibility or overflow problems. It is not drop-in for a bare React app: it needs a shadcn-style setup, including the expected utility module and local accordion wiring.
Use it if
- You need a prominent FAQ section with supporting copy and a contact link beside the questions.
- Your product already uses shadcn conventions, Tailwind theme tokens, and a Radix-backed accordion.
- You want only one answer open at a time and are comfortable editing the bundled static question data.
Skip it if
- You need answers driven by a CMS or API without adapting the hard-coded data array.
- You need multiple answers to remain open at once.
- You want a compact FAQ embedded inside a page rather than a section designed to fill the viewport.
- Your project does not use Tailwind or shadcn conventions and you do not want to recreate their theme and utility layer.
Install
| Declared dependencies | radix-ui |
|---|---|
| Missing on install | none |
| Bare install | fails once the shadcn-style helpers are removed, so it needs that setup |
| Provider | no provider required in the harness |
In a non-shadcn project, add Tailwind with matching color and typography tokens, configure the at-sign source alias, provide the class-name utility under the expected library path, install Lucide React and Radix UI, and create the compatible local accordion wrapper with its open and close animation styles.
Source and credit
This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.
Author repository
github.com/shabanhr/efferd-uiAlternatives
Other published entries for the faq pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.
- hyperui-faq-1editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.6KB
- Bare
- pass
- Prov
- NO
- hyperui-faq-2editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.6KB
- Bare
- pass
- Prov
- NO
- hyperui-faq-3editorial
- Renders
- YES
- A11y
- 0
- Gzip
- 17.7KB
- Bare
- pass
- Prov
- NO
- meraki-faq-collapseminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 17.9KB
- Bare
- pass
- Prov
- NO
- meraki-faq-centeredminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO
- meraki-faq-gridminimal-flat
- Renders
- YES
- A11y
- 0
- Gzip
- 18.0KB
- Bare
- pass
- Prov
- NO