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

NO JS / only CSS (checkbox hack)

Ozan GOKDEMIR•50
@ozangokdemir
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi guys !

I looked over a challenging exercice to pratice my newbie Javascript skills, but on this one I finally managed to used only CSS and get a good result that I'm proud of :)

There are few things I wanted to fix, but I couldn't find any solution for them, maybe because I don't have enough experience for it... I would be grateful if you would give me some leads on those :

  1. I used checkbox hack with radio buttons to have only one field opened at a time. The problem with this solution is that it seems a radio button cannot be unchecked using only CSS... Means I can't close all the fields once I opened one of them.

  2. I had to set a maximum height: 400px; to avoid fields from going over the div they are located in. I wonder if there is a better way to do it, for example by extending my div when it happens. I don't know if it's possible using only CSS.

  3. I had to play with selectors to put labels in bold and rotate arrows, but I didn't manage to do it without putting my checkbox before my label. I therefore had to set checkbox width: 0;, but this leaves a little space before my label.

Anyways, this taught me few things, but unfortunately not in JS !

For my next challenge, I will try to use SCSS for the first time, and still work on my JS skills :)

Thanks for your feedback. Peace !

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ozan GOKDEMIR's solution.

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.