Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

FAQ accordion

P
Hector Ramirez•450
@hectorlil48
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?

I'm most proud of how clean and efficient the accordion functionality turned out. The transitions are smooth, and the responsiveness works well across different devices. I also like how I kept the design simple and user-friendly while still making it visually appealing.

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

One challenge I faced was ensuring the accordion transitioned smoothly when expanding and collapsing. Initially, the animation appeared choppy, particularly on slower devices. To solve this, I experimented with different CSS transition properties and adjusted the timing functions until I found a combination that looked and felt smooth. I also tested the accordion on various screen sizes to make sure the transitions remained consistent.

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

I struggled to get the background image to fit properly, especially on larger screens. While I was able to make it responsive for most viewports, it still doesn’t stretch past 1440px, which makes it look cut off on ultra-wide monitors. I tried different CSS properties like background-size: cover and background-repeat: no-repeat, but I couldn’t get the desired result. I’d appreciate guidance on how to make the background image stretch consistently across larger screen sizes.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Andrey•4,360
    @dar-ju
    Posted about 1 month ago

    Hi!

    Why doesn't background-size: contain; work for you? It works best here.

    If you want the same height for all screen resolutions, it would be better to make a separate container for the background image and give it a height.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub