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

Html and CSS

Daodu Aisha•130
@Daodu111
A solution to the Recipe page 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

  • Mohammed Ibrahim•640
    @MohammedOnGit
    Posted 10 months ago

    Hi Daodu Aisha, congratulations on completing this challenge. Your HTML structure is well-organized and demonstrates a solid understanding of semantic elements. However, here are some recommendations and comments in terms of web development best practices:

    1. Accessibility: Alt attribute: Your <img> tag is missing a proper description for the alt attribute. Providing meaningful alt text ensures accessibility for users relying on screen readers.
    <img src="./assets/images/image-omelette.jpeg" alt="Omelette image">

    Headings hierarchy: The heading tags (<h2>, <h3>, <h4>) should follow a logical progression. Consider using <h1> for the main heading (e.g., "Simple Omelette Recipe") and maintain a clear structure for subheadings. This enhances accessibility and SEO.

    1. SEO Optimization: Meta description: You can add a meta description for search engine optimization.
    <meta name="description" content="A quick and easy omelette recipe, perfect for any meal. Learn how to prepare a classic omelette with optional fillings.">
    1. CSS Best Practices: Avoid inline styles: It's better to move inline styles, such as the ones within ) instead of a table for representing nutritional information.
    <dl> <dt>Calories</dt> <dd>277kcal</dd> <dt>Carbs</dt> <dd>0g</dd> <dt>Protein</dt> <dd>20g</dd> <dt>Fat</dt> <dd>22g</dd> </dl>
    1. Performance Optimization: Lazy loading: Use lazy loading for images to improve performance, especially for users with slower internet connections.
    <img src="./assets/images/image-omelette.jpeg" alt="Omelette image" loading="lazy">

    By implementing these suggestions, your project will align more closely with best practices in accessibility, SEO, and maintainability.

    Marked as helpful
  • Thomas•550
    @TomSif
    Posted 10 months ago

    nice work :)

    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.

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