Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Responsive accordion using HTML, Vanilla CSS and JS

accessibility
Alvin•140
@alvyynm
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


A little additional functionality is needed. I want to close an open accordion when I open another automatically. My current situation is that I can open all accordions by individually clicking on each. Can someone help me with this?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•5,480
    @thisisharsh7
    Posted almost 3 years ago

    Hey Alvin, great work! your solution looks perfect. In order to resolve your query to close an open accordion when you open another. You can make a new function outside the for loop in your code and then calls it inside the add event listener after the end of if-else statement. Consider an example function like this

    function whichButtonClicked(x){ //here x takes the value which button clicked by user
          for(let i=0;i<btns.length;i++){
                  if(i!=x){ //do this for all non-clicked button by the user
                             answers[i].classList.add("hidden");
                             btnQuestion[i].classList.remove("active");
                             accordionIcon[i].classList.remove("rotate-icon");
                    }
             }
     }
    

    Now call this function before the end of add Event listener in your code like this whichButtonClicked(i);

    I hope this answers your query..

    Marked as helpful
  • Felipe Chaves•240
    @loopchaves
    Posted almost 3 years ago

    Hi, Alvin!

    You can use the <details> tag instead of <button> to make the accordion. When you click on a <details>, the "open" attribute is added, which means that <details> is open. Just remove the "open" attribute from the rest of the <details> using JavaScript.

    See more about details tag in this link.

    Marked as helpful

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.

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