Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Icons FAQ Block for React

A cleaning-service FAQ built to be scanned: an icon tile on each question and three short answer lines led by a check, a clock and a shield.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

An icons FAQ for React with Base UI. A centred header sits over a framed list of seven questions: a frame open at the foot, so its sides run to the end of the block, with hairline rows inside it. Each question has an icon tile, and each answer is three short lines in the same order: a check for what you get, a clock for when and for how long, a shield for what protects you. The icons repeat, so a reader learns the pattern once and then skims. It's built from Accordion and Guides with lucide icons, with CSS transitions for the entrance and your theme's tokens for every colour. For service pages, home services and booking flows, where people want three facts, not a paragraph.

FAQ

How do I change the answers?

Edit QUESTIONS: each entry has the question, an icon (any lucide icon), and the three lines, get, when and covered. Keep each line to one sentence. If a question has nothing to say about cover or timing, drop that line from the entry and the markup together rather than padding it.

Are the icons read out?

No. Both the tiles and the line icons are decoration and hidden from assistive technology; the three lines are a real list, read in the same order as they appear. The icons add no information the words don't carry.

Are the closed answers in the page's markup?

Yes. The Accordion takes hiddenUntilFound, so every closed answer stays in the markup as hidden="until-found": search engines see all seven, and the browser's find in page opens the answer that holds a match.

How does it work with a keyboard and a screen reader?

Each question is a button inside its own h3 under the section's h2, so a screen reader's headings list shows them all. Tab moves from question to question, Enter or Space opens and closes one, and the button says whether it's expanded. The open answer is labelled by its question.

How does it fit on a phone?

The tile stays at 40 pixels and the question wraps beside it, the frame narrows to the column, and the answer lines run from the tile's start edge at full width. Nothing scrolls sideways at 320 pixels.

  • Pro

    Card Grid FAQ

    Cards and grids

    A static FAQ grid for a seed shop: six questions with their answers on show, in cells that share hairlines, each with an icon tile and a topic tag.

  • Pro

    Accordion FAQ

    Accordion lists

    A side-header FAQ for a web analytics tool: the title, one sentence and a contact prompt beside seven questions in an accordion, behind a split divider.

  • Pro

    Compact FAQ

    Accordion lists

    A dense FAQ for ski-lift passes: ten tight accordion rows with small type and one-sentence answers in a narrow framed list, a chevron at the start of each row.

  • Pro

    Numbered FAQ

    Accordion lists

    A numbered FAQ for a wine club: eight accordion rows from rail to rail, with a margin of tabular numerals, 01 to 08, behind a hairline; the open row's numeral turns to full strength.

  • Pro

    Docs Links FAQ

    Reading and sharing

    A FAQ for a mapping service where every answer ends in two guides from the docs, as links with a reading time and an arrow.

  • Pro

    Minimal FAQ

    Cards and grids

    A type-forward FAQ for a stationery brand: six questions in large type with their answers on show in a definition list, no cards or row lines, and one contact link.