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

Recipe Page

Dnyanesh Bachhav•60
@Dnyanesh-Bachhav
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Younes Iddahamou Idrissi•60
    @iddahadev
    Posted 11 months ago

    Does the solution include semantic HTML?

    Overral it does, but a few things need to be fixed:

    • There are h2 and h4 but no h1 and h3.
    • The main title should be h1.
    • The preparation title should be h2.
    • The span to make the text bold should be a strong or b.

    Is it accessible, and what improvements could be made?

    • The alt for the image should be human readable.
    • The table row does not have a table header, it should have one with scope="row"

    Does the layout look good on a range of screen sizes?

    • It looks a bit small on desktop.
    • The layout for the mobile is the same as the one on desktop.

    Is the code well-structured, readable, and reusable?

    • The HTML is readable.
    • The CSS could use a bit of structure with variables and better named classes.

    Does the solution differ considerably from the design?

    There are differences with the design such as colors, font weights and spacing, but the structure follows the design.

  • Emmanuel•110
    @MrNaturi
    Posted 11 months ago

    You need to work on your styling and attention to details

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