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

Responsive FAQ accrodion

Binyam•460
@binzam
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 1 year ago

    Hi, I hope this feedback is helpful

    1. Header is a very important landmark. It cannot be included and then have no content inside! It needs to be removed
    2. It's not recommended to add empty divs to html purely for styling reasons. If the image is changing between screen sizes it would be much better to use the picture element for good performance. If the image never changes then background image is OK
    3. The star image is decorative so should have empty alt. So is the plus you have incorrectly labelled as "icon"
    4. Headings must be in order. This is extremely important for accessibility and SEO. You cannot jump from a h1 to h4
    5. It is essential to use the correct elements for interactivity. Heading elements are not clickable so this is inaccessible. Accordions like this are called "disclosures" — Read this to find out what you need
    6. It is more performant to link the fonts in the html head instead of css imports
    7. Css should always start with a modern css reset at the start of the styles in every project
    8. Font size must never ever be in px
    9. Max width on the component should be in rem not px. You will want to have control of its max width and shouldn't need to change this at different screen sizes. With % you have no control and are forced to change max widths often.
    10. It is very confusing naming classes the same as established html landmarks when they are used elsewhere. At least use something like "faq-header" instead of just "header" so it's less confusing reading the css
    11. Use padding on the component not max width in %
    12. Media queries must be defined in rem or em for responsive sites. You only need one media query in this challenge. Once the above is fixed you should be able to delete others.
    13. Once the html is fixed you will need to change the js a little as it will need to toggle aria- state. You will be able to do most of what you are doing now all in the css instead of js.
    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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub