Measured entry
meraki-faq-collapse
A minimal FAQ layout shipped as a standalone HTML document with Tailwind utility classes, inline SVG icons, and dark-mode styling. It relies on Tailwind for presentation but includes no script or framework dependency. Despite the collapse label, the supplied markup only depicts open and closed rows; it does not implement toggling.



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 | 17.9 KB (83.3 KB build, 65.4 KB baseline) |
| Bare mode | OK |
| Provider required | NO |
| Demo used | none |
Verdict
A clean, dependable FAQ shell, but the name overstates what ships. Treat it as styling reference rather than a finished collapse component, since toggling, state, hidden content, and disclosure attributes are left to the implementer.
Use it if
- You want a restrained FAQ layout and will connect the rows to your own disclosure state.
- Your project already uses Tailwind and can reuse its spacing, color, and dark-mode utilities.
- You need a simple visual starting point that is easy to translate into a framework component.
Skip it if
- You need a working accordion without writing the interaction logic yourself.
- You need production-ready disclosure semantics and keyboard state already implemented.
- Your project does not use Tailwind and you do not want to translate a utility-heavy template.
- You want polished transitions, configurable behavior, or reusable component APIs out of the box.
Install
| Declared dependencies | none declared |
|---|---|
| Missing on install | none |
| Bare install | builds and mounts without the shadcn-style helpers |
| Provider | no provider required in the harness |
In a non-shadcn project, add Tailwind CSS with dark-mode support or replace the utility classes with local styles. Add your own disclosure state and event handling, then connect each trigger and panel with appropriate expanded, controls, and hidden semantics.
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/merakiui/merakiuiAlternatives
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-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
- 8bitcn-faq2skeuomorphism
- Renders
- YES
- A11y
- 0
- Gzip
- 30.2KB
- Bare
- fail
- Prov
- NO