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

FAQ Card Made Using HTML, CSS and some Basic JavaScript

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

Solution retrospective


Here my first challenge that includes JavaScript. While making layouts was easy but setting those images was a little challenging for me as there was two images which I have to stack on top of each other for the shadow effect. But I find a little hard to organize CSS, like which one to put first and next. And in JavaScript I have to make buttons to assign those functions to it cause I cant make it to work on images. So is there any way all this could be done the easy and efficient way.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nelson•2,390
    @nelsonleone
    Posted over 2 years ago

    HELLO......congrats on completing this challenge, well done🎊 🎊 I have some tips on how you can write neater and less code , you can improve your solution , or work better on the next one.

    The Faq , can be done using the <dl><dt>``<dd> tags for accessibility purposes.

    Based on your question and your solution(how you did it) You can use buttons to create the questions, the arrow doesn't need to be the toggle , it's just for design purposes mainly.

    And other than creating a DomList of elements, just get the classes of the questions and answers.

    Then use a loop to display what you want to display.

    const questions =  document.queryselectorAll('.question')
    const answers = document.querySelectorAll('.answers')
    questions.forEach((question,index) ,() => {
      question.addEventlister('click',() => {
        answer[index].style.display ="block"
      }
    })
    

    The index simply means the index in which the button(question causing the click event is) the answer in that same index should do your task

    Hope this comment was helpful and made meaning to you Have fun coding

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