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

Responsive accordion layout; SCSS with BEM

LEUILLIER•120
@JulienLEUILLIER
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Second FrontEndMentor challenge completed !

I complicated things at first by trying to make the images responsive in size with the screen width, to be able to have a flexible width for mobile. I ended up just leaving a fixed size but learned some awesome ways to get responsive images ! I also tried to implement BEM to get some, I think, clean and maintainable SCSS code.

Any comment would be highly valued !

Code
Select a file

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. Layout looks great in desktop, it is responsive and the mobile state looks great as well.

    You already got some feedbacks on this, just going to add some small suggestions:

    • Do not use a tag for the accordion toggle since those are not links, use button instead because it is a control element for the accordion.
    • If you are going to use button don't forget to add a default aria-expanded="false" attribute on it, it will be set to true if the users toggles the button and vice-versa. This will let your users know that is has expanded something to be seen.
    • The dropdown svg should be hidden so add aria-hidden="true" on it. Remember to always hide decorative images.

    Aside from those, great work again on this one.

    Marked as helpful
  • Ken•4,915
    @kens-visuals
    Posted almost 4 years ago

    Hey @JulienLEUILLIER 👋🏻

    I just have one small suggestion, I suggest adding aria-hidden to the box image, like this <img src="/images/illustration-box-desktop.svg" alt="" aria-hidden="true" class="hide-for-mobile card__box">. You can read more about aria-hidden here.

    I hope this was helpful 👨🏻‍💻 looks good on every viewport width size, well done. Cheers 👾

    Marked as helpful
  • Al-Baraa Bakri•330
    @Al-Baraa-Bakri
    Posted almost 4 years ago

    good job :) I just finished this challenge .. What About Add Some Transition ?

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

Oops! 😬

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

Log in with GitHub