Specific user question.
public-product pattern
FAQAccordion
Answer high-trust product questions with native disclosure semantics and visible scope limits.
complyeaze/core · candidate · @sanchika/patternsProduct job
Expand a specific trust or scope question and inspect its answer and source.
Answer high-trust product questions with native disclosure semantics and visible scope limits.
Anatomy and required fields
Plain-language answer with boundary.
Optional supporting public source.
- question
- answer
Default and edge states
Question remains visible.
- question
- disclosure state
Answer and source are visible.
- question
- answer
- boundary
Composed synthetic exemplar
Does Sanchika make compliance decisions?
No. It supplies interface contracts that keep sources, uncertainty, and human review visible.
Are the records on this page real?
No. Every gallery record is synthetic and exists only to demonstrate the package contract.
Can a consumer skip its own accessibility testing?
No. Package evidence is a starting point; the composed consumer workflow still requires testing.
State coverage
Default and consequential edges remain inspectable.
Trust, source, and consumer obligations
- Do not imply government affiliation, guaranteed outcomes, or unstated production readiness.
- Name account, upload, local-processing, external-destination, and human-review boundaries before action.
- Supply current product copy, sources, destinations, prices, review ownership, and all runtime behavior.
- Keep disclosure targets at least the control-height minimum.
- Do not split a question from its answer.
- Retain labelled boundaries, native link underlines, focus outlines, and status text without authored color.
- Keep all claims, proof, boundaries, and actions visible without entrance or layout motion.
Compact API reference
- Package
@sanchika/patterns- CSS
@sanchika/patterns/styles.css- Base class
sk-pattern-faq-accordion- Group
public-product