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

FAQ Accordion HTML, CSS, JS

WannaBeDev•90
@GColville
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This one was a struggle for me with a lot of work to be done.

I'm not sure I went about this the right way, positioning the elements was really tricky.

Looking at the code, is there a better way to have approached this?

UPDATE:

I've re-done the code after some practice and looking around for pointers. Still not perfect, there are some bugs to fix:

  1. Card height increases when each answer is expanded. Not sure if this should really happen.
  2. Font-weight for the question text is giving me trouble
  3. Arrow rotate to be done (had issues)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, awesome work on this one, though the default layout looks like the mobile design which should not be. Did you code this on a wide screen? You must account that there are 1366x767 resolution screen for desktop.

    Some suggestions would be:

    • Avoid using height: 100vh on a large container, this makes the element's height limited to the remaining screen/viewport's height. Instead, use min-height: 100vh, this takes full viewport but allows the content to expand if it needs to. Also remove the width: 100% on the body tag, block element like the body tag have a default width: 100%.
    • You are missing the cube image on the desktop layout, you might want to check that one out.
    • It would be better if the question name can be toggled to show the answer as well. Since you are using button for the dropdown icon, you can wrap the question name inside the button so that they will activate it as well. But to be honest, I would just use details element on this one. Since using regular button needs to be manipulated in javascript to make it more accessible for users, details is already accessible which is great.

    Aside from those, great work again on this one. But maybe try to lower down your breakpoint so users won't have to zoom out just to see the desktop layout.

    Marked as helpful
  • P
    Kevin Davis•280
    @webdev1kev
    Posted almost 4 years ago

    Yea this one was tricky for me as well!

    For positioning elements I would definitely try to take advantage more of flexbox so you don't have to hard code a lot of margins, especially for the faq-container, since its more grid-like and uniform unlike the image, not sure how to effectively use flexbox on the image lol.

    Also try to use more percentage or relative values in margins, padding, so that items can position themselves more dynamically when the screen size changes.

    Other than that keep at it!

    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