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

FAQ Accordion card using only CSS

Emilie•30
@emiliemorassi
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey guys ! First time submitting my work here ! So, I only used CSS for this one. Fun ride ! And I'm having difficulty positioning the box image and I usually don't have that kind of problem so I'm wondering if anyone could help me find out what I dit wrong here. It just doesn't get out of my head, I may need the Eureka moment/facepalm to let it go ^^ I tried different ways and none of them worked as I would want them to. It either moves when I resize the page and I want it fixed at that position (version that I kept), or, part of it disappears when it's supposed to get above the background. (Which I suppose is normal since it was placed partly outside of its container with an absolute position). Anyway, I would love some feedback on that and feel free to comment on the rest. Thanks a lot !

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • bunee•2,020
    @buneeIsSlo
    Posted almost 4 years ago

    Hey! @emiliemorassi, Congrats on completing your first FEM challenge, you've done Amazing! The page responds very well.

    • Positioning elements absolutely, does get head scratching sometimes. I applied these fixes
    .containerBox {
        position: relative;
    }
    
    .box {
        top: 40%;
        left: -95px;
    }
    

    Note: Theses fixes are not perfect, but does get the job done.

    • You can add an overflow-y: scroll; to the .content. This way the the .containerBox doesn't overflow when all the questions are opened.

    • Great job on writing semantic HTML. I'm currently working on this project myself and I wasn't aware of the details tag so, Thanks for teaching me somethin new.

    Hope this helps :)

    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