Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Responsive FAQ using flexbox and JS

Zachariah Kozlowski-Best•75
@zach7815
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone, I am wondering if I have too much CSS code for such a project as I tried to make it responsive for all sizes.

What techniques, or methods could I follow/ read up on to make my code cleaner and more dry for the future?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    👋 Hi Zach!

    I have some feedback on this solution:

    • Accessibility
      • Use the native HTML tag to create the accordion, details and summary. This will make the assistive technology like screen-reader can understand that it is an accordion.
      • For any decorative images, each img tag should have empty alt="" and aria-hidden="true" attributes to make all web assistive technology such as screen readers ignore those images. In this case, all images are decorative only.
      • Swap the attribution div with footer to fix the accessibility issue.
    • Visual
      • To make this website responsive:
        • I would recommend letting the content inside the container control the height of the container.
        • Simplify the @media query, in this case, you don't need to care about the user height size. Focus on the width (min-width, with mobile-first approach).
      • The background-color of the container or the card should be white, which means you don't need any filter property at all.
    • JavaScript
      • Don't use inline styling ( the same rule apply when writing JavaScript ). Use CSS classes to handle any styling and use JavaScript to add or remove the class.
      • I would recommend using forEach instead of for loop to make your JavaScript easier to understand.
      • I would recommend separating the classes for styling and for JavaScript by prefixing the class name with js-. The js- classes are only for JavaScript purposes only ( no styling at all). This will make it easier to maintain, since if you want to change the styling, then the functionality will still remain.

    That's it! Hopefully, this is 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