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

Used HTML5, CSS3(Grid), Google Font, vars, and ARIA for accessibility.

accessibility
Gabriel•40
@4ndradeGabriel
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?
  • HTML5:

    • Implemented semantic elements like <main> and <section>, and to enhance document structure.
    • Applied ARIA labels to provide better context for assistive technologies (e.g., aria-label="Instructions").
    • Used descriptive alt attributes for images to support screen readers and improve accessibility.
  • CSS3:

    • Utilized CSS Grid and Flexbox to create a responsive and well-structured layout.
    • Applied CSS variables :root for better maintainability of colors and consistent theming.
    • Styled list markers with ::marker to differentiate list items visually.
    • Used media queries to ensure the layout adapts correctly on smaller devices.
  • Accessibility Enhancements:

    • Ensured accessible navigation by adding ARIA labels to key content sections like ingredients, instructions, and nutritional information.
    • Adjusted color contrast between text and background based on WCAG guidelines.
    • <ul> and <ol> tags are used for the ingredients and instructions, ensuring that screen readers can properly interpret the sequence of items.
    • The use of <section> elements to group related content (e.g., recipe image, preparation time, ingredients, instructions, and nutritional information) improves document structure, making it easier for users with disabilities to navigate the page.
  • Responsive Design:

    • Adopted a mobile-first approach, ensuring compatibility with various screen sizes.
    • Applied max-width: 800px to prevent content from becoming too wide on larger displays.
    • Utilized place-content: center with CSS Grid to center the content both vertically and horizontally.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sania Saleem•110
    @codeBloom361
    Posted 6 months ago

    Good job completing this challenge. Your solution looks good and the code is clean.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub