A diving website should answer questions before visitors need to send an email.
Where is the business located?
Are beginner programs available?
Does a particular activity require certification?
And most importantly, is that activity actually operating?
These questions become especially important when a website contains both historical service descriptions and current availability notices.
For this tutorial, we'll use Kaanapali scuba diving as our example and build a simple, accessible FAQ page for visitors researching ocean activities around Kaanapali and nearby Lahaina.
We'll use:
- Semantic HTML
- Native disclosure elements
- Responsive CSS
- Clear availability messages
- A small content review checklist
The result will work without a JavaScript framework.
Let's build it.
1. Start With the User's Questions
Before writing code, think about what someone actually needs to know.
A visitor researching scuba diving near Kaanapali may have questions about certification, meeting locations, swimming requirements, and current availability.
The FAQ should answer those questions directly.
It should not turn every answer into a sales message.
Our example will use four questions:
- Can beginners try scuba diving?
- Is Kaanapali Beach the meeting location?
- Are diving tours currently available?
- What should visitors know about marine life?
Notice that these questions have different purposes.
Some explain general information.
Others require confirmation from a real business.
That difference will influence how we write the answers.
2. Create the HTML Structure
Create a file named index.html.
Start with a basic semantic page layout.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport"
content="width=device-width, initial-scale=1">
<title>Kaanapali Scuba Diving FAQ</title>
<link rel="stylesheet" href="styles.css">
</head>
<body>
<main class="container">
<header class="intro">
<h1>Kaanapali Scuba Diving FAQ</h1>
<p>
Helpful answers about scuba diving,
training, and ocean activities around
Kaanapali and nearby Lahaina.
</p>
</header>
<section aria-labelledby="faq-heading">
<h2 id="faq-heading">Common Questions</h2>
<!-- Add FAQ items here -->
</section>
</main>
</body>
</html>
We use a <main> element to identify the page's primary content.
The FAQ has its own section and heading.
This provides a clear document structure for visitors and assistive technologies.
The text is written for human readers rather than repeating the target keyword in every sentence.
3. Build an Accordion Without JavaScript
A common approach is to build an FAQ accordion using JavaScript.
But native HTML already provides a useful option.
The <details> element can expand or collapse content.
The <summary> element provides its visible label.
Let's add our first FAQ inside the section.
<details class="faq-item">
<summary>
Can beginners try scuba diving near Kaanapali?
</summary>
<div class="faq-answer">
<p>
Some supervised introductory scuba programs
are designed for eligible beginners.
Requirements depend on the provider,
training standards, health screening,
and current activity availability.
</p>
</div>
</details>
That's it.
No JavaScript needed.
Visitors can use the summary to expand or collapse the answer.
The browser provides much of the basic interaction behavior.
Using native elements also reduces the amount of custom code we need to maintain.
However, native components still need testing with keyboards, browsers, and assistive technologies.
4. Make Service Availability Clear
Now comes the part that many websites overlook.
An activity may have a detailed description without being currently available.
This is a real issue for some ocean businesses around Lahaina.
Following the 2023 Lahaina wildfires, Dive Maui / Hawaiian Rafting Adventures published notices explaining that certain diving trips and courses were unavailable.
A website should not hide an important availability notice inside a long promotional description.
Let's create an example question that handles uncertainty clearly.
<details class="faq-item">
<summary>
Are diving tours currently available?
</summary>
<div class="faq-answer">
<p>
Current availability has not been verified
for this example page.
</p>
<p>
Some historically listed activities may be
unavailable. Confirm the specific program
directly with the operator before making
travel plans.
</p>
<p class="status-note">
Status: Confirmation required
</p>
</div>
</details>
This is more useful than writing:
"Book your amazing diving adventure today!"
The second statement might create a false expectation if the activity is unavailable.
Our version communicates uncertainty without pretending to have real-time information.
The key lesson:
Do not turn missing information into a positive availability claim.
5. Explain the Difference Between Business Location and Dive Location
Another common issue involves meeting points.
A business might have a street address in Lahaina while its activities, when operating, use different locations.
Let's make that distinction explicit.
<details class="faq-item">
<summary>
Does every dive start at Kaanapali Beach?
</summary>
<div class="faq-answer">
<p>
No. A business address does not automatically
identify the meeting point or water entry
location for every activity.
</p>
<p>
Confirm the specific meeting instructions
directly with the provider.
</p>
</div>
</details>
This answer is short.
But it addresses a real visitor concern.
It's also a good example of why useful local content does not need excessive keyword repetition.
6. Add an Environmental Responsibility Question
Let's include a question about marine wildlife.
<details class="faq-item">
<summary>
What should divers know about sea turtles?
</summary>
<div class="faq-answer">
<p>
Hawaiian green sea turtles are protected
wildlife. Observe them without touching,
feeding, chasing, or blocking their path.
</p>
<p>
NOAA recommends staying at least 10 feet
away from sea turtles in Hawaii.
</p>
</div>
</details>
A page about ocean activities can be more useful when it includes practical environmental guidance.
But make sure factual claims are supported by reliable sources.
Never invent wildlife guarantees to make a page sound more exciting.
7. Add Mobile-Friendly CSS
Now create a file named styles.css.
We'll use a clean layout with comfortable text sizes and enough spacing between FAQ items.
:root {
--text: #183047;
--accent: #075a7a;
--border: #d6e2e8;
--surface: #f4f9fb;
--focus: #c04b30;
}
* {
box-sizing: border-box;
}
body {
margin: 0;
font-family: Arial, sans-serif;
line-height: 1.7;
color: var(--text);
background: #ffffff;
}
.container {
width: min(100% - 32px, 820px);
margin: 0 auto;
padding: 40px 0 64px;
}
.intro {
margin-bottom: 36px;
}
h1 {
font-size: clamp(1.8rem, 5vw, 2.7rem);
line-height: 1.25;
}
h2 {
font-size: 1.5rem;
}
.faq-item {
margin: 14px 0;
border: 1px solid var(--border);
border-radius: 10px;
background: var(--surface);
}
.faq-item summary {
padding: 18px 22px;
font-weight: 700;
cursor: pointer;
}
.faq-item summary:hover {
color: var(--accent);
}
.faq-item summary:focus-visible {
outline: 3px solid var(--focus);
outline-offset: 3px;
}
.faq-answer {
padding: 0 22px 18px;
}
.faq-answer p {
margin: 10px 0;
}
.status-note {
font-weight: 700;
}
@media (max-width: 600px) {
.container {
padding-top: 24px;
}
.faq-item summary {
padding: 16px;
}
.faq-answer {
padding: 0 16px 16px;
}
}
This creates a responsive FAQ layout.
The content stays readable on smaller screens.
We also preserve a visible focus indicator so keyboard users can identify the active element.
Notice that the design does not rely on color alone to communicate availability.
The status is written in text.
That is important for accessibility.
8. Do We Need ARIA Attributes?
Not always.
A frequent mistake is adding extra accessibility attributes to elements that already have native semantics.
The <details> and <summary> elements provide built-in disclosure behavior.
You generally do not need to recreate that behavior using custom JavaScript and ARIA.
Adding unsupported roles or manually maintained expanded states can make an interface harder to manage.
Start with semantic HTML.
Then test how the actual page behaves.
Use additional accessibility code only when there is a clear reason.
9. What About FAQ Structured Data?
Developers working on local business websites often ask whether every FAQ page needs FAQPage JSON-LD.
The short answer is no.
Google has restricted FAQ rich results primarily to well-known, authoritative government and health websites.
Most ordinary commercial websites should not expect FAQ rich-result displays.
That does not make an FAQ page useless.
A clear FAQ can still help real visitors understand services, requirements, and important limitations.
If you implement structured data, follow the relevant specifications and ensure the markup accurately reflects visible page content.
Do not add schema simply to promise a search result feature that may not be available.
The quality of the answers matters more than the presence of a script tag.
10. Review the Content Before Publishing
A technically correct page can still contain misleading information.
That's why the final step is editorial.
Review each FAQ answer.
Ask yourself:
- Does this answer address the question directly?
- Is the information current?
- Have uncertain services been identified clearly?
- Are locations and meeting points distinguished?
- Are safety-related statements appropriately qualified?
- Can visitors read and use the page on mobile?
- Does the page work with a keyboard?
- Have important claims been checked against reliable sources?
For an ocean business, review dates are especially useful because schedules and service availability can change.
A simple internal record might look like this:
Content review record
Page: Kaanapali Scuba Diving FAQ
Page type: Educational resource
Business location: Lahaina, Hawaii
Service availability: Verification required
Meeting location: Verification required
Last review date: Not recorded
Next action: Confirm current information
The fields are deliberately conservative.
They record what still needs to be checked without inventing a date or claiming verification has happened.
11. A Real Example From West Maui
Kaanapali and Lahaina are neighboring coastal areas in West Maui.
Visitors may search for diving information in Kaanapali while researching a business based in Lahaina.
Dive Maui / Hawaiian Rafting Adventures is a family-run scuba diving and ocean activity business with a listed address at 1223 Front Street in Lahaina.
Its official website includes information about diving, courses, equipment, and ocean experiences.
Some previously offered diving trips and training programs remain marked unavailable following operational challenges connected to the Lahaina wildfires.
For developers researching Kaanapali scuba diving and local Dive Maui information, the official website is a useful example of why service descriptions and current availability notices should be read together.
A historical trip page should not automatically become an active booking offer on a new website.
Likewise, the business address should not be presented as a confirmed departure point for every activity.
Accurate content requires those distinctions.
12. Test the Finished FAQ
Before publishing, open your local index.html file in a browser.
Try the following:
- Use the Tab key to move through the page.
- Press Enter or Space to expand an FAQ.
- Collapse it again.
- Resize the browser window.
- Check whether any text overflows on mobile.
- Test with a screen reader where possible.
- Read the page as someone unfamiliar with scuba diving.
The last step matters just as much as the others.
A visitor should not need to understand web development or scuba terminology to find a simple answer.
Final Thoughts
An effective FAQ page does not need a complicated framework.
Native HTML, thoughtful CSS, and accurate content can produce something genuinely useful.
For a topic like Kaanapali scuba diving, visitors need more than attractive images and short promotional phrases.
They need to know whether an activity matches their experience, where they would meet, and whether it is actually available.
The technical work makes the information accessible.
The editorial work makes it trustworthy.
And both parts deserve attention.
Build for the person asking the question, not just for the search engine reading the page.
Top comments (0)