Measured entry
meraki-faq-cards
A static FAQ card stack shipped as a standalone HTML document. It uses Tailwind utility classes, including dark-mode variants, plus inline SVG icons. One answer is shown by default, while the remaining rows look expandable but have no script, disclosure state, or interaction behavior.



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 | 1 |
| 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 usable visual starting point, not a finished FAQ interaction. It builds and mounts cleanly across the tested layouts, but teams must add disclosure behavior, accessible state, and corrected contrast before production use.
Use it if
- You need a simple FAQ layout whose content can remain fully visible or be wired to your own disclosure logic.
- Your project already uses Tailwind and you are comfortable replacing the sample copy and visual-only controls.
- You want a responsive card stack that mounts without framework providers or component-library setup.
Skip it if
- You need a working accordion immediately, since the buttons do not expand or collapse answers.
- You require an accessibility-ready component without remediation, since the tested styling has a serious color-contrast issue and lacks expanded-state semantics.
- Your design system does not use Tailwind and translating utility classes would cost more than recreating this small layout.
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 |
A non-shadcn project needs Tailwind CSS configured for the utility and dark-mode classes, or equivalent styles rewritten in its own CSS. Add disclosure logic, expanded-state attributes, keyboard-safe button behavior, and adjusted text colors that meet contrast requirements.
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-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