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

FAQs Accordition solution

Pichika Chandu•140
@Pichikachandu
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I'm most proud of how I was able to implement the interactive toggling feature for the FAQ answers. The dynamic show/hide functionality works well, and it’s fully accessible with keyboard navigation, which was one of my goals. Additionally, I’m happy with how I implemented a mobile-first design approach, ensuring the layout looks good on both small and large screens.

Next time, I would focus more on refining the accessibility aspects, especially by adding ARIA attributes to improve screen reader support. I would also consider adding animations or transitions to make the interactions smoother and more visually engaging.

What specific areas of your project would you like help with?

One of the challenges I faced was figuring out how to manage the toggling of answers. Initially, I had trouble making sure that only one answer was displayed at a time, as clicking on a question would sometimes cause multiple answers to display simultaneously. I overcame this by clearing all answers before showing the clicked one. This involved selecting all the answer elements and resetting their display property before toggling the one that was clicked.

Another challenge was ensuring that the layout was responsive. I spent extra time tweaking the styles for mobile devices and making sure the design was clean and easy to navigate. Flexbox and media queries were really helpful in addressing this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•9,710
    @MarziaJalili
    Posted 7 months ago

    Hi there!

    The project works as expected. It looks great.

    Some sort of suggestion:

    • Frist, you use the grid to center the card instead of positiong it:
    body {
      display: grid;
      place-items: center;
      min-height: 100vh;
    }
    

    This ensures that the card will be centered even if the answer expands.

    • Second, instead of just using an <div> for the toggle buttons, use the <button> element an then wrapp the image inside. This gives more information to the screen readers and specifies it's a button rather than an actual image.
    <!--current code => --> 
    <div class="icon">
      <img src="./assets/images/icon-plus.svg" alt="icon-plus">
    </div>
    
    <!--change it too => -->
    <button class="icon">
      <img src="./assets/images/icon-plus.svg" alt="icon-plus">
    </button>
    

    The <button> element comes with some default styles. So, get rid of them using the code below:

    button {
      border: none;
      background-color: transparant;
    }
    

    This will improve the project even further😎

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