Examples

FAQ / Disclosure standard

Public FAQ and disclosure content should use native `<details>/<summary>` so the experience works with and without JavaScript.

Why use native details/summary?

It removes JS/hydration dependency for basic disclosure behavior and improves no-JS resilience.

What should be checked after migration?

Expand/collapse behavior in JS browsers, no-JS readability, and visual spacing consistency.

When is a custom accordion acceptable?

Avoid it for public FAQ/disclosure content unless there is a documented, reviewed exception.

General

What is this organization?

A volunteer-led community rescue group focused on feeding, rescuing, and rehoming stray animals.

What area do you serve?

We primarily serve the local community and surrounding areas. Contact us for out-of-area resources.

How do I adopt?

Submit an application on the Adoption page. Our team reviews applications and follows up on potential matches.

Is there an adoption fee?

Yes. Fees help offset vaccinations, spay/neuter surgery, and medical care costs.

How can I volunteer?

Visit our Volunteer page or contact us directly. No prior experience is required.

- JS on: disclosures expand/collapse and chevron alignment remains correct.

- JS off: content is still accessible and no hydration mismatch blocks interaction.

- Verify keyboard support (Enter/Space on summary) and focus visibility.

- Confirm no duplicate fallback content blocks were left behind from prior migrations.