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

Responsive FAQ accordion card, using HTML, CSS & JS

Hoophelie•110
@HOOPhelie
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Everybody! 🖐

This challenge was trickier than I thought:

  • To avoid the overflow:hidden from the white card to apply on the box image on desktop mode: I used an empty div to position the box. The empty div has the same dimensions as the white card, so the box will move accordingly to the white card's resizing.
  • I added a transition so the answer can unwind smoothly when clicking on the question. I had to include the height + the padding-bottom in the transition.
  • I tried making it pixel perfect, but it means the card is not centered

I'm not sure I proceeded correctly for these points. Any feedback is welcome! 😊 Thank you in advance

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted over 4 years ago

    Greetings, Hoophelie! 👋

    Nice to see you complete another challenge! 😀 Good job on this one! 👏 Your solution looks great and the accordion works well! 👍

    Two minor suggestions I have are making sure there is always a little bit of space between the accordion card and the bottom of the page (even when multiple FAQs are opened) and adding cursor: pointer to the FAQs so that users can even more easily tell that they are clickable. 😉

    Keep coding (and happy coding, too)! 😁

  • Samuel Palacios•615
    @samuelpalaciosdev
    Posted over 4 years ago

    Hi, Hoophelie👋

    Great job on this challenge. Your solution looks good and scales pretty well👍

    I hope you have a nice day, keep coding!💙

  • Agata Liberska•4,075
    @AgataLiberska
    Posted over 4 years ago

    Hi @HOOPhelie, well done on this challenge. Don't worry about making it pixel perfect, it really doesn't need to be!

    Nice work with the transitions, I think it would be great if you added one to the toggle arrows as well :)

    There is one problem though (and it's the same mistake I made with this challenge) - at the moment the accordions are not accessible as there is no way to get to them using the keyboard. To make them accessible, you could use buttons as clickable elements :)

    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, SASS, 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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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

Oops! 😬

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

Log in with GitHub