Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 20 days ago

container at-rule for background image change

P
Claudia•260
@cla91
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?

The problem I encountered was that the rem unit in the media feature behaved differently from rem unit in other elements. To overcome the problem, because I wanted the breakpoint to be at 375px which is the size of the mobile background image, I used the container at-rule even if it's still pretty recent.

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

Where would you put the breakpoint for the background image?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•5,180
    @thisisharsh7
    Posted 20 days ago

    Excellent work on completing the challenge! 👏

    👍 Strengths:

    • Great use of container-type: size and @container for the background breakpoint — future-facing and precise!
    • Clean, semantic HTML with meaningful structure using <section> and <article>.
    • Your JavaScript handles state toggling accessibly with aria-expanded and alt updates — well done!

    🔧 Suggestions:

    • Background image breakpoint: Your use of @container (width > 37.5rem) works well, but for broader support you could consider a fallback using @media (min-width: 600px) alongside the container query.
    • Accessibility: Consider adding aria-controls on buttons to associate them directly with their answer <p> elements.
    • Performance: Preload or use loading="lazy" for icons if reused in large UIs.

    Overall, great work - happy coding!

  • UmairFaiser•100
    @UmairFaiser
    Posted 19 days ago

    Heh nice work.i think the animation needs to be more smooth but overall nice work.well done

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