Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

FAQ Accordion

CloudOfAlemar•220
@CloudOfAlemar
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everyone, I just completed the FAQ Accordion Frontend Mentor Challenge. It was fun building this component. I really enjoyed using Javascript to dynamically set the max-height of the li elements to hide its content. I really took my time to make sure that some small functionality details were handled as best as possible, which made me use the ResizeObserver API to fix some issues when the screen was being resized. I had lots of fun building this component overall, please let me know if there is anything I can improve on, thank you! :D P.S - I didn't use the design files for this project :p

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Dean•480
    @Deanogit
    Posted over 1 year ago

    Wow! @CloudOfAlemar! This is impressive!

    I've been wondering for a while now how its possible to get these cool on loading animations!

    I've noticed at the bottom of your CSS file you're using

    @keyframes introFaqCard {
      0% {
        opacity: 0;
        transform: translateY( 20% );
      }
      100% {
        opacity: 1;
        transform: translateY( 0% );
      }
    

    This really looks great!! What an inspiring solution, I'll dig into the JS more when I have more time, I'd also like to implement the accessibility features in the brief.

    Amazing work!

  • Eugenia Antonova•430
    @EugeniaAntonova
    Posted over 1 year ago

    Hello! I really like your solution and as i am a newbie, i have more of a question, than advise: why did you decide to put background images directly into the murkup and not to use background-image? I read it is better practice

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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