Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Clipboard Landing Page (Grid CSS) ❤🧐

accessibility, bem
Ezequiel•1,250
@3eze3
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Well, first of all I've been a little busy with a lot of things, but I still finished this project and the ones I'm missing haha 🤷♂️, I really liked this project, it made me review topics that I thought I already mastered as Css grid, the problem of collision of margins and some other issues, however I finished it and I feel I did well. As you know if you have any help to improve my code or design please comment.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • David Gichuru•360
    @dxiDavid
    Posted over 2 years ago

    Hi, Ezequiel Córdova Sotomayor! 👋

    This solution is awesome, congrats 🎉

    I have a few suggestions for you to improve the code

    You might want to set the breakpoint a little higher than 490px to allow

      .track__snippets {
        flex-direction: column;
      }
    

    to stack items in that section on top of each other starting at a larger screen size (somewhere around 900px)

    You could also try to put the sections inside <main> to avoid the warnings

    <main>
        <section class="track">
        <section class="access">
        <section class="workflow">
        <section class="clipboard">
    </main>
    

    I hope you find this helpful 😁

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted over 2 years ago

    Hi, Ezequiel Córdova Sotomayor! 👋

    I have some suggestions to improve this solution.

    • Add download attribute for each download link. The value of the href attribute should point to a file instead of the external link. Also, remove the target="_blank".
    • Alternative text of the logo should be the name of the company—alt="Clipboard".
    • Not every image needs alternative text. Decorative images should not have alternative text (alt=""). This will tell the screen reader to skip over the image. As a result, it saves screen reader users time navigating the page.
    • For your information, decorative images are images that don't add any information and serve only aesthetic purposes.
    • Alternative text for images should not contain any words that are related to "image" (e.g. picture, photo, logo, icon, graphic, avatar, etc). It is already an image element (<img>) so the screen reader will pronounce it as an image.
    • Wrap each social media icon with an anchor tag. Then, use the alternative text of the <img> to label the link.

    I hope you find this useful. 🙂

    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