Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

FAQ Accordion using Grid only responsive Design

John Carruthers•310
@techyjc
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Well, this is my attempt at the FAQ Accordion design.

Got a little stuck on the best way to code it.also need to address the jumpy movement on opening the first FAQ. Other than that I think I covered it...

You be the judge!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Melvin Aguilar 🧑🏻‍💻•61,020
    @MelvinAguilar
    Posted over 1 year ago

    Hello there 👋. Good job on completing the challenge !

    I have some suggestions about your code that might interest you.

    • Never set overflow: hidden on the body element unless you're displaying a modal. It should not have overflow: hidden because this disables scrolling, which is bad for mobile users. Even I had zoom, and I wasn't able to see the bottom part of your solution 😢.
    • position: relative is also unnecessary on the body element, and it's better to use a CSS reset to remove default browser styles than setting margin: 0 on the body element.
    • The <div class="attribution"> should be a footer element.
    • While div is excellent for positioning and styling, it's not an interactive element. It should not have a cursor pointer because it's not intended for that purpose. You should replace it with an interactive tag, like a button.

    I hope you find it useful! 😄

    Happy coding!

  • P
    Daniel 🛸•44,740
    @danielmrz-dev
    Posted over 1 year ago

    Hello @techyjc!

    Your project looks pretty good!

    I have just one suggestion:

    • Since the plus icon is a clickable element, it's nice to add cursor: pointer; to it.

    I hope it helps!

    Other than that, great job!

  • John Carruthers•310
    @techyjc
    Posted over 1 year ago

    Appears to be some errors with aria attributes. I will correct them.

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

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