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

FAQ accordion card

Mohamed•325
@MohamedBehhar
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hy developers, hope you all are doing well, this my solution for The Accordion FAQ challenge, i struggled to make the accordion close when Im clicking on another question, I'll be grateful if someone can help me with that.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mohamed•325
    @MohamedBehhar
    Posted over 3 years ago

    Thank you very very much for this explicit comment, i'll do my best to make my works looks better.

  • Aakash Verma•9,500
    @skyv26
    Posted over 3 years ago

    Hi! Mohamed, I just checked you work and also tested mobile responsiveness. I noticed some issues that I am going to write and will try to add some suggestions or tips for betterment of your solution.

    1. Your Card is too wide and I noticed that you have applied condition, if user only click on the arrows then and only then the accordian tab will open.

    You have to keep in mind most probably any user will try to click on the accordian tab's question not directly on arrow. So add this condition too,so that if any click event occurs on the accordian question then it also work same as that of arrow.

    1. I saw that for the very first time I clicked on question and the tabs expands with it answer's height, but along with this accordian height also changed with expansion of accordian tab and it should not be like this.

    Add the fix height for accordian so that it never expand and still at its right position. Also you please on click of any accordian tab, only current tab expand and rest of all should be in collpased state. Because it is the requirement of this challenge, you have to follow the requirement.

    1. Your design is responsive but because of above problems it makes it overflowed. You can also check this.

    2. For solving your accessibility issue, you have to wrap your .card and .attribution div inside the main tag and from now on use this tag as your container in next challenge's solution.

    3. I saw that you haven't enter alt text, so it is good practice to add alt text in your img tag so that any user if comes to your website and any how he/she not able to see the page images then alt text will help to make them understand about the image.

    Overall Good work, and I hope you understand above issues.

    Good Luck

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