Measured entry
tailark-veil-faqs-3
A static FAQ section shipped as a shadcn registry block and React client component. It maps local question copy into a single-open accordion and adds a Next.js support link. It depends on Tailwind theme utilities, the @/ alias, Next.js Link, and Tailark's Veil accordion registry item.



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 | 57.8 KB (123.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 963ms error during build: [vite]: Rollup failed to resolve import "@radix-ui/react-accordion" from "<sandbox>re-cd29658bae42/src/components/ui/accordion.tsx".
Verdict
Do not adopt it from the current registry: the build fails because the referenced Tailark Veil accordion resolves to an unavailable shadcn registry URL. Teams needing a working drop-in should avoid it. Even after that dependency is repaired or replaced, it needs a shadcn-style setup to mount.
Use it if
- You want a centered, single-open FAQ section with fixed local copy and a support link.
- Your team can replace or restore the unavailable Veil accordion dependency before adoption.
- Your application already uses Next.js, Tailwind theme utilities, and shadcn-style component aliases.
Skip it if
- You need a registry block that installs and builds without repairing a missing upstream dependency.
- Your application is not based on Next.js and Tailwind theme utilities.
- You need FAQ content from a CMS, search, or multiple panels open at once.
Install
| Declared dependencies | clsx, tailwind-merge |
|---|---|
| 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 |
A non-shadcn project must add a compatible accordion implementation, wire the @/components/ui/accordion alias, provide Tailwind plus the referenced theme and container utilities, and replace Next.js Link or install Next.js. The unavailable Tailark registry dependency must be restored or substituted first.
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/tailark/blocksAlternatives
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