FAQ
An FAQ collects questions people often ask before deciding or getting help. The answers use the words and situation those people know.
Is every example original?
Yes. We made every scene for this guide.
Can I use the prompt?
Yes. Change it to fit your product.
A real example
A pricing FAQ covers cancellation, invoices, data export, and plan changes. It links to full policies.
Main parts
- 01Trigger or task context
- 02Primary control surface
- 03Feedback, focus, and dismissal
Use it when
Use it when real questions keep coming up and short answers can remove doubt.
Do not use it when
Never invent easy questions or hide key terms. An FAQ can't replace site navigation.
Name used in code
<section> / <details> Before you ship
Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.
Outcome: Use FAQ to solve this user need without losing the current context. User context: A pricing FAQ covers cancellation, invoices, data export, and plan changes. It links to full policies. Recommended pattern: FAQ. Why it fits: Use it when real questions keep coming up and short answers can remove doubt. Do not use it when: Never invent easy questions or hide key terms. An FAQ can't replace site navigation. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of FAQ. Definition: An FAQ collects questions people often ask before deciding or getting help. The answers use the words and situation those people know. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.