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

FAQ Accordion

accessibility
Mehmet Ali Meşe•130
@mehalimes
A solution to the FAQ accordion challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am open for every comment.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ehsan Tatasadi•1,800
    @tatasadi
    Posted over 1 year ago

    Hey there,

    Excellent work on completing the Frontend Mentor FAQ challenge using React! Your implementation showcases a solid understanding of React concepts, Redux for state management, and CSS for styling. Here are a few suggestions to enhance your project further:

    Border Separation for Questions: Adding a border-bottom to each FAQ item will visually separate the questions, making the UI cleaner and more user-friendly. This small change can significantly improve readability.

    Cursor Pointer for Icons: For a better user experience, the plus and minus icons should change the cursor to a pointer on hover. This indicates that these elements are clickable and interactive, conforming to standard UI practices.

    Responsive Design Adjustments: Avoiding fixed width and height for the card is a good practice for responsive design. Instead, consider using max-width to maintain the card's aspect ratio while allowing it to adjust to different screen sizes. This approach prevents content overflow in mobile view and enhances the responsiveness of your application.

    Box-Shadow for Card: Adding a box-shadow to the card can provide depth and elevate the card from the background, enhancing the visual appeal. This subtle effect can make the interface more engaging and modern.

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