On this page
@addTagHelper *, Webority.Ui.RazorQuestions and answers
Use a questions section near the foot of a page, where visitors look for doubts cleared before sign-up.
Three questions, centred
The section writes no structured data. Set the SEO package's seo.Faq from the same list the page renders, so the FAQPage and the visible answers cannot differ.
Questions we hear often
Still stuck? Write to us.
Left-aligned heading
Left-align the heading when the questions sit in a column, so the heading and the answers share one edge.
Left-aligned, three questions
Questions we hear often
Questions open at start
Open the questions a visitor is most likely to ask, so the answer shows without a click.
First and third open
Questions we hear often
No. You pay the monthly plan only, and Starter is free.
Split layout
Put the heading beside a numbered list when the questions are the page's main content. Give the open toggle a word with close-label.
Split, with a close word
Questions we hear often
Still stuck? Write to us.
Every option
Every value of every prop, one cell each.
title
title="Questions we hear often"
Questions we hear often
children / (content)
(content): an app-accordion of questions
Questions we hear often
(content) omitted: the heading only
Questions we hear often
as
as="h1"
Questions we hear often
as="h2" (default)
Questions we hear often
as="h3"
Questions we hear often
as="h4"
Questions we hear often
as="h5"
Questions we hear often
as="h6"
Questions we hear often
eyebrow
eyebrow="Support"
Support
Questions we hear often
subtitle
subtitle="Still stuck? Write to us."
Questions we hear often
Still stuck? Write to us.
openItems / open-items
open-items omitted (default): each question's own open
Questions we hear often
open-items="0"
Questions we hear often
No. You pay the monthly plan only.
open-items="0,2"
Questions we hear often
No. You pay the monthly plan only.
align
align="center" (default)
Questions we hear often
align="start"
Questions we hear often
variant
variant="default" (default)
Questions we hear often
variant="muted"
Questions we hear often
variant="split"
Questions we hear often
closeLabel / close-label
close-label="Close" (split layout only)
Questions we hear often
id
id: labels the section by its heading, no visible change
Questions we hear often
className / class
class: extra classes on the root, no visible change (React className)
Questions we hear often
Guidance
What to do, and what to avoid.
Use it when
- Questions buyers ask before they sign up.
- The last section before the call to action.
Reach for something else when
- Long help articles. → a help centre page
Reference
Try every prop, read the full list, and check keyboard and screen reader behaviour.
10 props. The 5 most used come first.
Used on most screens 5 props
| Prop | Type | Default | Description |
|---|---|---|---|
| titledefault - | string | - | The section's heading. Required. |
| asdefault h2 | h1 | h2 | h3 | h4 | h5 | h6 | h2 | The heading element. |
| eyebrowdefault - | string | - | A short label above the heading. |
| subtitledefault - | string | - | A sentence or two under the heading. |
| aligndefault center | start | center | center | Where the heading block sits. |
Less common 5 props
| Prop | Type | Default | Description |
|---|---|---|---|
| variantdefault default | default | muted | split | default | The section's background, or split for a heading beside a numbered list. |
| close-labeldefault - | string | - | In the split layout, the text an open question's toggle shows in place of the chevron. |
| iddefault - | string | - | Labels the section by its heading ({id}-title). |
| open-itemsdefault - | string | - | Comma-separated positions of the questions that start open, counted from 0 ("0,2"). They are handed to the nested app-accordion. |
| (content)default - | markup | - | The <app-accordion> of questions. |
Screen reader
3 notes- The section is labelled by its heading, through aria-labelledby, when an id is passed.
- The title is a real heading element chosen by as, so set it to fit the page outline.
- The questions sit in an AppAccordion, whose titles are buttons with aria-expanded, and closed answers stay in the page text.