Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

FAQ Accordion Card - Semantic HTML + SASS/SCSS Only Solution

accessibility, vite, sass/scss
Gabriel Montplaisir•210
@GabrielMontplaisir
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I decided to try to tackle the bonus challenge to only create this in CSS. Additionally, I've been wanting to tackle a little bit of SASS, so I thought this would be a nice challenge to try out. I feel like I've added an extra day's worth of work to myself by attempting all of this when it could have been done in a quarter with JS. Oh well, learning!

  • I really wanted to attempt this with the semantic use of <detail> and <summary>, as they're a "built-in" HTML accordion box.

  • I wanted to animate the accordion a bit by transitioning the height of the answers when they dropdown, but some of these effects are harder to achieve when using CSS-only options. If I tried using a max-height: 99rem (to mitigate long answers), the animation sometimes only worked one out of five times, or became "choppy". For that reason, I had to limit it to about 10rem, with the caveat that if a question were added later, the developer would have to increase the max-height value to say 15,20,30rem, etc. If there's a way to make it a little more responsive, I'm all ears!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Gabriel Montplaisir'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

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.