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

HTML, CSS - GRID - FLEX, JS

Mathias de la Fuente•40
@mathiconh
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback would be appreciated!!!

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 Mathias!

    👍Good job on completing this challenge! This challenge has a tricky position for the images 😅.

    I have some feedbacks on this solution:

    • Wrap all your page content with main tag except the attribution. For the attribution, swap the div with footer.
    • Currently the accordions are not accessible using keyboard (toggle the accordion panel) and screen reader. I recommend to use summary and details tags instead of div. For the JavaScript, you're going to only allow the user to open one accordion panel at a time (like what you have done).
    • Also don't forget to add :focus-visible style to all accordion panel. This is helpful for users that navigate your website using keyboard.
    • For 0 value on CSS, you don't need to put any units after it. Just write 0.
    • Use rem or sometimes em unit instead of px. Using px will not allow the users to control the size of the page based on their needs.
    • Don't limit the height of the body element, it will not allow the users to scroll the page if the page content needs more height. Use min-height instead.
    • Make sure that your solution looks good on all screen sizes, currently on mobile landscape mode and on desktop view doesn't look good.
    • About the container, I guess you can don't need to set any height for it, I recommend to let the padding and the elements inside it that control the height. This will make your container more responsive.
    • Remove this CSS code unless you have a reason of doing it. If you have the reason, please tell me.
    html {
      height: 100%;
    }
    
    • Consider using js- as the prefix for any DOM elements that you want to manipulate through JavaScript and don't put any styling to any js- class (it's only for JavaScript). This will make your code more maintainable!
    • I recommend to use let instead of var to any variables that you want to reassign.

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