Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 months ago

Faq-accordion using HTML, CSS and JavaScript

ldonnianni•130
@ldonnianni
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am most proud that I could make a Java Script Code in order to be able to interact with the elements. It was the first time. It was not easy. What I would do differently in my next project is to set the layout correct, then the Java Script and finally do the styles. I find it easier not to get hang up in CSS while trying to make the both layout for mobile and desktop and the JS

What challenges did you encounter, and how did you overcome them?

It was difficult to understand how to make page keyboar navigation. Still not sure wether what I did was correct. While trying to solve this I read several post in the help channel and google for different options.

What specific areas of your project would you like help with?

I would like to know wether I make a good use of the aria-expanded and control or not. And if it is indeed this what the challenge ask for. I am also in doubt with the background change from desktop to mobile. It was difficult to check if the transition from one to another is ok. And how indeed I can see the project in a mobile.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ashwini Magar•100
    @Ashwini202213
    Posted 10 months ago

    Great job on the code! You've done an amazing job with the design, and the task looks really well-executed. please check for mobile view /responsiveness as well.😊

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