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

recipe-page

accessibility
Maian Lucas de Jesus Oliveira•120
@MAIAN-HUNTER
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

using tables and design tools

What challenges did you encounter, and how did you overcome them?

design and tables tag

What specific areas of your project would you like help with?

solutions for designs varieties

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniele•300
    @dedo-dev
    Posted 12 months ago

    Hi @MAIAN-HUNTER, I reviewed your repository and I have some suggestions for you:

    1. Adopt mobile-first approach, is a good way to style the html;
    2. Try to start to use a modern approach with the css by using Logical properties example: - margin-left = margin-inline-start; - margin-bottom = margin-block-end; - Check out this article about Logical properties;
    3. To follow the design you need to remove the padding on your .container, you can add it by using @media or @container query, I used the second one, or maybe the fluid spacing;
    4. You need to set all the headings bigger than now;
    5. Don't use strong if your goal is only to highlight text, instead use the b or span to achieve that. Read this article to discover why;
    6. To make a divider use the semantic hr or a div with class .divider for example, the last one was my solution, instead of setting padding-top to the h2;
    7. Remove the default padding from ul and ol, and to style the bullet points use the same trick that you use on the li for ol (they should be bold), and play with ::before pseudo-element, this is how I did all the marker for the list; hint: left: some rem
    8. To style the border of the table you can use table {border-collapse: collapse;}, with this css the border looks like a single line;
    9. In my solution I used only tr and td to make the table, maybe this doesn't matter, but you need to highlight the right column of the table, th has font-weight: bold; as default on it;
    10. Fix the footer tag and position, on mobile view it overlaps the layout and on large screen, it sits on the left of the card;

    Hoping you find this helpful ✌️

                      Keep learning 📖 Keep coding 💻
    
    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