Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 4 months ago

Interactive and mobile responsive FAQ accordion using CSS and JS

accessibility, sass/scss, lighthouse
Raymond•20
@RaymondRabago
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I have created reusable accordion that I can easily plug and play into my future projects.

I learned to use outline to highlight keyboard-accessible elements, improving their accessibility. Here is the implementation:

/* Establish a default outline style for all elements, 
** which will not affect layout or spacing */
* { 
    outline: 2px dashed transparent;
    outline-offset: 3px;
}

/* Add color to the outline when the element 
** has focus due to keyboard navigation */ 
*:focus-visible { 
    outline-color: hsl(292, 16%, 49%);
}

I also learned the use of aria-expanded="{boolean}" and aria-controls="{idValue}" to create a more accessible and dynamic experience for users, specifically in the context of collapsible elements, by providing a clear indication of their expanded or collapsed state and establishing a clear relationship between the toggle control and the content it controls.

Here is the sample implementation:

<article class="accordion js-accordion">
    <button aria-expanded="false" aria-controls="accordion-content-0">
        <span>Questions</span>
    </button>
    <div class="content" id="accordion-content-0">
        <div class="inner">
            <p>Answer</p>
        </div>
    </div> 
</article>    
What specific areas of your project would you like help with?

I believe there's room for improvement in how I've structured my HTML5, SASS, and JavaScript. If there are any best practices or suggestions that could help enhance my code, I’d really appreciate learning about them.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Raymond's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.