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

Responsive Accordion with JS

accessibility
Abdelrahman-Almansory•470
@Abdelrahman-Almansory
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?

First time looping through classes using getQuerySelectorAll, its still difficult but i managed to pull it. I like the end result and waiting for feedback.

What challenges did you encounter, and how did you overcome them?

removing minus class for buttons of a section when another sections open

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grego•1,430
    @Grego14
    Posted 4 months ago

    Hello! Congratulations on completing the challenge. 🎉

    I recommend using buttons instead of a <div> for the icon elements and clicking on the text next to the icon also expands the accordion, as this would improve the user experience.

    I see that you're using multiple loops to do things that one would do. You can add an ID to the parent element of all accordions, the accordions-section, then get that element using:

    const accordionParent = document.getElementById('accordion-parent-id')
    

    Doing this would no longer require the icons or the text, as you could easily obtain it using the accordionParent variable. And you can use the event delegation technique to improve your code:

    accordionParent.addEventListener('click', (event) => {
      const target = event.target
    
      // if the clicked element is not an icon or a accordion text do nothing
    
      if(!target.classList.contains('icon') 
      || !target.classList.contains('accordion-header')) return
    })
    

    To avoid using a loop and removing the minus class from each element, you can simply get the current element that contains the class, remove it, and add it to the currently clicked element:

    // inside the accordionParent click event after the **if**
    
    // get last open accordion and accordion text
    const lastOpenAccordion = accordionParent.querySelector('.accordion:has(.minus)')
    const lastOpenAccordionText = lastOpenAccordion.querySelector('.accordion-content')
    
    // get next open accordion and accordion text
    const clickedAccordion = target.closest('.accordion')
    const clickedAccordionText = clickedAccordion.querySelector('.accordion-content')
    
    lastOpenAccordion.classList.remove('minus')
    lastOpenAccordionText.classList.remove('open')
    
    clickedAccordion.classList.add('minus')
    clickedAccordionText.classList.add('open')
    
    // Handle adding and removing heights ...
    

    The closest method will look up for any first parent element that matches that selector.

    When an image is an icon or non-semantic, hide it from screen readers using the aria-hidden attribute with the value true, also remember to add width and height attributes in images to prevent CLS.

    <img src="assets/images/icon-star.svg" alt="star SVG" aria-hidden="true" width="40" height="40">
    

    I hope this helps! 😁

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.

Oops! 😬

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

Log in with GitHub