Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

Mobile First Approach Using Just HTML&CSS

Arda•85
@ardaberrun
A solution to the FAQ accordion card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Ugh, I've had more trouble on this challenge than I thought but somehow I finished :d. Any feedback will be appreciated. Thank you :)

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted about 4 years ago

    Hey, great work on this one. The layout on desktop is good, it's just a bit small but is fine and the mobile state is really good as well.

    Suggestion/s would be:

    • Selecting an accordion, some pop ups resizes the container right, it adds some height on it. To prevent that, if you want, you could remove the max-height: 50rem first on the accordion selector. Then in the question-area, you could add a max-height: 440px I used 440px since when you inspect your container, without any selected accordion, the initial height is 440px. Then just add overflow-y: scroll on the selector again. This make sure that the height will stay at 440px even if an accordion's content is big and it won't resize the container. But by doing this, this will add a scrollbar. To remove it, simply add
    .example::-webkit-scrollbar {
      display: none;
    }
    
    /* Hide scrollbar for IE, Edge and Firefox */
    .example {
      -ms-overflow-style: none;  /* IE and Edge */
      scrollbar-width: none;  /* Firefox */
    }
    

    Just change the selectors name to the container with max-height. That is from w3schools.

    Though that only, since you made this really good and clean markup, just a thing with those radio buttons, making it display: none keeps functionality but removes accessibility. Overall, great work^^

  • omisc•115
    @csimomelian
    Posted about 4 years ago

    Yep, looks good. Any challenge, no matter how simple it may seem, has its complications.

    You can increase the line-height value to allow the text breath more, and don't forget to define the alts in the images, is a good pratice.

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