# FAQ Section

## Objective

Add an expandable list of questions and answers to any page, in the order you choose.

A reorderable set of question and answer pairs rendered as an accessible expand-collapse list on any page.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Build it on real disclosure semantics with a button that toggles its own panel, so keyboard and screen reader users get the behaviour for free.
2. Give every question a stable anchor derived from its text and keep it after edits, so a support reply can link straight to one answer.
3. Allow answers to contain formatted text, lists, and links, and reuse the app's existing content editor and its sanitisation rules rather than accepting raw markup.
4. If the app already has an AI FAQ generator or a help centre, let this section draw from those existing question records instead of holding a separate copy of the same answers.
5. Do not force only-one-open behaviour by default. Allowing several open at once is what people expect when they are comparing answers, and it avoids the collapse-and-jump problem entirely.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- A link to a single question must open that item and scroll it into view on load, including when the link is followed while the page is already open.
- If only-one-open behaviour is used, collapsing a tall answer above the one being opened yanks the page. Anchor the scroll position to the item the user clicked so it stays where they are looking.
- Rich answers containing lists and links must not be reachable by keyboard or read by screen readers while the panel is collapsed. Hide the region properly rather than clipping it with height.
- In-page search, including the browser's own find, cannot see text inside closed items. Expand any item containing a match when the page has a search control, and warn authors that browser find will miss collapsed content.
- Printing must render every answer expanded. A printed page of unanswered questions is useless.
- The expand and collapse transition must be skipped when reduced motion is requested.
- An empty answer or a question with no answer yet must not render as an item that opens onto nothing.
- Reordering questions must not change their anchors, or every previously shared link points at a different answer.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] Questions expand and collapse by keyboard and are announced with their expanded state.
- [ ] Each question has a stable anchor that survives edits and reordering.
- [ ] A deep link opens the target question and scrolls it into view.
- [ ] Collapsed answers are hidden from keyboard navigation and assistive technology.
- [ ] Print output shows every answer expanded.
- [ ] Answers support formatted text and links through the app's existing sanitised editor.
- [ ] Transitions respect reduced-motion preferences.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.