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

Responsive Recipe Page with Semantic HTML and Custom CSS Variables

accessibility
Abdulgafar-Riro•250
@Abdulgafar-Riro
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?

What I am most proud of:

Successfully creating a fully responsive recipe page that maintains a clean, professional layout across various screen sizes.

Implementing semantic HTML to ensure the page is accessible and follows best practices.

Utilizing CSS variables to streamline theme management and improve maintainability.

Incorporating custom fonts for a visually appealing and unique design.

What I would do differently next time:

Optimize the project further by compressing image files for faster load times.

Include ARIA roles and additional accessibility features to enhance usability for screen readers.

Add animations or transitions to improve the user experience and make the interface more interactive.

Explore using a preprocessor like SASS for better CSS organization in larger projects.

Test the design across more devices and browsers to ensure consistent performance.

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

Challenges Encountered:

  1. Ensuring Responsiveness Across Devices:

Designing a layout that adapts seamlessly to different screen sizes was challenging, particularly for smaller devices.

Solution: I utilized CSS Flexbox and media queries to create a responsive design and tested it across various screen resolutions.

  1. Font Integration Issues:

Embedding and loading custom fonts correctly caused minor formatting inconsistencies.

Solution: I ensured proper file paths and formats for the fonts and verified compatibility across browsers.

  1. Maintaining Accessibility:

Ensuring the design was accessible to all users, including those relying on screen readers, required additional effort.

Solution: I used semantic HTML, descriptive alt attributes for images, and consistent heading structures to improve accessibility.

  1. Styling Complex Elements:

Designing the nutrition table to look clean and readable without breaking the layout was tricky.

Solution: I applied a minimalistic design using CSS variables and adjusted padding and borders for clarity.

  1. Managing Consistent Styling:

Keeping the styles consistent across different sections and ensuring scalability posed a challenge.

Solution: I implemented CSS variables for colors, spacing, and typography to maintain uniformity.

Through persistence, testing, and iterating on the design, I was able to address these challenges effectively.

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

Areas I Would Like Help With:

  1. Accessibility Improvements:

Suggestions for further enhancing accessibility, particularly for users relying on assistive technologies.

  1. Responsive Design Optimization:

Feedback on ensuring a flawless layout on larger screens and more complex resolutions.

  1. Code Optimization:

Recommendations for making the code more concise, reusable, and scalable.

  1. Typography and Styling:

Advice on improving the visual hierarchy and overall aesthetic appeal of the project.

  1. Performance Optimization:

Techniques to improve load times, especially for assets like custom fonts and images.

Your insights would help refine the project further and ensure it meets best practices.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Abdulgafar-Riro's solution.

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

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.