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

Clipboard landing page

Yazdun•1,310
@Yazdun
A solution to the Clipboard landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello FEM community ! Here is my first junior challenge and I have some questions:

  • If you're on mac : I've been told my theme switch method doesn't work on mac but I couldn't find out why since I don't have access to any macOS system, so I'll appreciate it if you can inform me about theme functionality.
  • Does animation works properly for you ? and do you have any good resource to learn css animations to share with me ?
  • I spent some time to learn accessibility and I applied what I've learned to this project but I really need some advice on accessibility, any resources or feedbacks regards to accessibility is very valuable to me.
  • What is best tag for alerts and modals in html ? I used div since I didn't know any other tags for them, Is it a good approach?

AND HERE ARE SOME GOOD RESOURCES I FOUND ALONG THIS PROJECT

  • Here is a very good and straight forward article about applying dark mode using sass.
  • I learned a lot from this video by legendary Kevin Powell, It's very short video but probably you will find it useful if you're struggling with accessibility like me.
  • Here is another great content by Kevin Powell which taught me to add animation to elements on scroll.

✅ That's all, I'm looking forward to your feedbacks. If you have any other thoughts about my solution, don't hesitate to share it with me.

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 Yazdun'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
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 1st-party linked stylesheets, and styles within <style> tags.

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.