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

mobile first FAQ accordion component build with SCSS, and JavaScript

animation, bem, sass/scss, vite
Johnny•490
@johnnysedh3lllo
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey guys, here i am again attempting another Frontend Mentor Challenge and i can't begin to describe how impactful this community has been to my growth. All the comments and suggestions helped me gain a substantial amount of confidence when i was working through the HTML/CSS projects when i first started here and i learned so much from the way other people did things and the broadened my view on things and i just want to say thank you to everyone here for being part of this community, because without you there would be no community and without this community, where would i be?

so if you're reading this right, i just want you to know i grateful for you being here. and yes this was a thank you speech 😁 but if you do have any comments about my HTML Structuring especially in regards to my choice of Semantic Elements to use, BEM naming, CSS, or JavaScript and you believe there is a better way i could've done things, please leave a comment, suggestion or recommendation (whatsoever), thank you very much.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Somnath Golui•210
    @somu-code
    Posted over 1 year ago

    This submission looks great kudos to you. Can you guys also review my profile and all the submissions i have made. Here my username @somu-code

  • Lucas 👾•104,160
    @correlucas
    Posted over 1 year ago

    Nice work my friend! I'm back!

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