Measured entry
efferd-faqs-2
faqminimal-flatmotion on file
A full-page FAQ block with a split desktop layout, a stacked mobile layout, a single-open accordion, and a footer contact prompt. It ships as a shadcn registry component, imports the local accordion wrapper, and relies on Radix UI behavior plus Tailwind utility classes and theme tokens.



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.6 KB (105.0 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 41s 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, low-decoration FAQ for shadcn-based marketing pages, with responsive behavior and accessible accordion semantics. It does not mount bare and needs a shadcn-style setup, and its viewport-led layout plus placeholder content make it a starting block rather than a drop-in final section.
Use it if
- You want a restrained, editorial FAQ section that can occupy most of a landing page.
- Your app already uses shadcn conventions, Tailwind theme tokens, and the shared accordion primitive.
- Your answers suit a single-open accordion and you want the first item expanded initially.
Skip it if
- You need several answers open at once or persistent deep links to individual questions.
- The FAQ must fit naturally inside a short page section rather than a viewport-height composition.
- You need CMS-driven content or a working support destination without editing the hardcoded questions and placeholder link.
- Your project does not use Tailwind and you do not want to recreate the layout and theme-token styling.
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 the Radix-backed accordion primitives, a class-name merge helper at the expected local utility path, the matching import aliases, and Tailwind with the referenced theme tokens. Then replace the bundled questions and wire the contact link to a real destination.
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