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

Accessible and Responsive Recipe Page: Flexbox, BEM and Media Queries

accessibility, bem, sass/scss, lighthouse
Paulo Wells•530
@wellspr
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?

There are various subtle details in this project, and I made my best to pinpoint as much of then. I'm very satisfied with the result. I think I did a good job including semantic tags for accessibility and organizational structure, leading to legible and self-explained code. The BEM methodology was applied to enhance the use of Sass, leading also to a very legible SCSS stylesheet. Next time, I would like to get into the subject of delivering responsive images.

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

A difficult part was finding a way to style the list bullets and numbers differently than the contents themselves. I solved this by applying the desired bullets or numbers styling to the whole list (ul, ol), wrapping the li content in a span, and applying the content styles to this span.

Also, I liked styling a table, which led me to refresh some basics of this subject (and I think it is always a good idea to know how to style a table). For example, I produced the table division lines styling the bottom border of the td's, but had to set the table's border-spacing to zero to avoid a visible gap.

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

I would love to get feedback on any point of this project, including the way I apply the BEM methodology, the use of semantic tags, etc. Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Daniel Lasauskas•330
    @mazinger086
    Posted 4 months ago

    Hey mate, you really made it, for that challenge it was a little bit hard, depending on how do you handle in mobile and desktop version. It' take me a while but I think you handle better than me. Awesome work.

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