/* 
   FAQ Page Styles for Aglaea 
   Now using native <details>/<summary> for the accordion — no
   custom JS needed to open/close a question, and it gets correct
   keyboard support and semantics from the browser for free.
   One real trade-off worth knowing: native <details> opens and
   closes instantly rather than sliding smoothly the way the old
   JS-driven version did. Getting a smooth slide back would mean
   reintroducing JS specifically for that animation, which works
   against the point of simplifying this away from JS in the first
   place — so this is deliberate, not an oversight.
*/

/* FAQ Hero */
.faq-hero {
    background: linear-gradient(135deg, var(--cream) 0%, var(--stone) 100%);
    padding: 5rem 0 4rem;
    text-align: center;
    border-bottom: 1px solid var(--stone);
}

.faq-hero .container {
    max-width: 800px;
    margin: 0 auto;
    padding: 0 1.5rem;
}

.faq-hero h1 {
    font-family: var(--font-display);
    font-size: 3.5rem;
    font-weight: 400;
    margin-bottom: 1rem;
    color: var(--charcoal);
    letter-spacing: -0.5px;
}

.faq-subtitle {
    font-size: 1.25rem;
    color: var(--slate);
    font-weight: 300;
}

/* FAQ Content */
.faq-content {
    padding: 5rem 0;
    background: white;
}

.faq-content .container {
    max-width: 900px;
    margin: 0 auto;
    padding: 0 1.5rem;
}

.faq-category {
    margin-bottom: 4rem;
}

.faq-category:last-child {
    margin-bottom: 0;
}

.faq-category-title {
    font-family: var(--font-display);
    font-size: 2.5rem;
    font-weight: 500;
    color: var(--charcoal);
    margin-bottom: 2rem;
    padding-bottom: 1rem;
    border-bottom: 2px solid var(--gold);
    letter-spacing: -0.5px;
}

/* FAQ Items — now <details> elements */
.faq-item {
    border-bottom: 1px solid var(--stone);
}

.faq-item:last-child {
    border-bottom: none;
}

/* FAQ Question — now a native <summary>. list-style/marker rules
   hide the browser's own default disclosure triangle so our own
   +/− indicator (below) is the only one shown. */
.faq-question {
    width: 100%;
    list-style: none;
    padding: 1.75rem 0;
    font-family: var(--font-display);
    font-size: 1.65rem;
    font-weight: 500;
    color: var(--charcoal);
    cursor: pointer;
    display: flex;
    justify-content: space-between;
    align-items: flex-start;
    transition: color 0.3s ease;
    line-height: 1.4;
}

.faq-question::-webkit-details-marker {
    display: none;
}

.faq-question:hover {
    color: var(--gold);
}

.faq-question:focus-visible {
    outline: 2px solid var(--gold);
    outline-offset: 4px;
}

/* The +/− indicator is pure CSS-generated content on the summary
   itself — not a separate element in the markup, so there's
   nothing here that needs an aria-hidden treatment; generated
   content like this isn't exposed to the accessibility tree the
   way a real element with text would be. */
.faq-question::after {
    content: '+';
    font-size: 2rem;
    color: var(--gold);
    font-weight: 300;
    flex-shrink: 0;
    margin-left: 1.5rem;
    line-height: 1;
    transition: transform 0.3s ease;
}

.faq-item[open] .faq-question::after {
    content: '+';
    transform: rotate(45deg);
}

.faq-answer {
    padding: 0 0 2rem 0;
}

.faq-answer p {
    color: var(--slate);
    line-height: 1.8;
    margin-bottom: 1.25rem;
    font-size: 1.063rem;
    font-family: var(--font-body);
}

.faq-answer p:last-child {
    margin-bottom: 0;
}

.faq-answer ul,
.faq-answer ol {
    margin: 1.25rem 0 1.25rem 2rem;
    color: var(--slate);
    line-height: 1.8;
    font-family: var(--font-body);
}

.faq-answer li {
    margin-bottom: 0.75rem;
    font-size: 1.063rem;
}

.faq-answer strong {
    color: var(--charcoal);
    font-weight: 600;
}

/* FAQ CTA */
.faq-cta {
    background: linear-gradient(135deg, var(--gold) 0%, #B8935A 100%);
    padding: 5rem 0;
    text-align: center;
    color: white;
}

.faq-cta .container {
    padding: 0 1.5rem;
}

.faq-cta-content {
    max-width: 700px;
    margin: 0 auto;
}

.faq-cta-content h2 {
    font-family: var(--font-display);
    font-size: 2.75rem;
    font-weight: 400;
    margin-bottom: 1.25rem;
    letter-spacing: -0.5px;
}

.faq-cta-content p {
    font-size: 1.188rem;
    margin-bottom: 2.5rem;
    opacity: 0.95;
    line-height: 1.6;
    font-family: var(--font-body);
}

.faq-cta .btn-primary-large,
.faq-cta .btn {
    background: white !important;
    color: var(--gold) !important;
    border: 2px solid white !important;
    font-weight: 600;
    padding: 1rem 2.5rem;
    font-size: 1.063rem;
    transition: all 0.3s ease;
    display: inline-block;
    text-decoration: none;
    border-radius: 8px;
}

.faq-cta .btn-primary-large:hover,
.faq-cta .btn:hover {
    background: transparent !important;
    color: white !important;
    transform: translateY(-2px);
}

/* Mobile Responsiveness */
@media (max-width: 768px) {
    .faq-hero {
        padding: 4rem 0 3rem;
    }

    .faq-hero h1 {
        font-size: 2.5rem;
    }

    .faq-subtitle {
        font-size: 1.125rem;
    }

    .faq-content {
        padding: 3rem 0;
    }

    .faq-category {
        margin-bottom: 3rem;
    }

    .faq-category-title {
        font-size: 2.05rem;
    }

    .faq-question {
        font-size: 1.35rem;
        padding: 1.5rem 0;
    }

    .faq-question::after {
        font-size: 1.5rem;
        margin-left: 1rem;
    }

    .faq-answer p,
    .faq-answer li {
        font-size: 1rem;
    }

    .faq-cta {
        padding: 4rem 0;
    }

    .faq-cta-content h2 {
        font-size: 2rem;
    }

    .faq-cta-content p {
        font-size: 1.063rem;
    }
}

@media (max-width: 480px) {
    .faq-hero h1 {
        font-size: 2rem;
    }

    .faq-question {
        font-size: 1.2rem;
        padding: 1.25rem 0;
    }

    .faq-category-title {
        font-size: 1.75rem;
    }

    .faq-hero .container,
    .faq-content .container {
        padding: 0 1rem;
    }
}