Measured entry
ruixen-faq-auto-accordion
faqunclassifiedmotion on file
A client-side React FAQ that keeps a single answer open, advances through items on a timer, pauses on pointer hover, and animates the active marker, answer reveal, and list reflow. It ships as a shadcn registry component and depends on Motion, Tailwind theme utilities, and the shared cn helper imported through the usual app alias.



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 | 69.8 KB (135.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 25.29s error during build: [vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/faq-auto-accordion.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'
Verdict
A polished fit for an animated marketing FAQ, with clean verified mounting and responsive behavior. It needs a shadcn-style setup rather than dropping into a bare React project, and teams should review the timed cycling for focus and reduced-motion expectations.
Use it if
- You want a compact FAQ that can cycle through answers automatically while still allowing direct selection.
- Your product already uses shadcn conventions, Tailwind theme tokens, and Motion.
- A single-open accordion with a traveling active marker suits the page hierarchy.
Skip it if
- Visitors need to compare several answers at once, since opening an item closes the current one.
- Automatic content changes are inappropriate for the audience or the page context.
- You want a dependency-light accordion without a motion library.
- Keyboard focus must pause the automatic cycle, since the supplied pause behavior is pointer based.
Install
| Declared dependencies | motion |
|---|---|
| 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 Motion, configure Tailwind with foreground and muted-foreground theme tokens, provide a cn class-merging helper, and either configure the app import alias or replace that import with a local path. The component must run on the client.
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/ruixenui/ruixen.comAlternatives
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