Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive New HomePage

accessibility
Arya Dixit•20
@AryaDixit
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my step to the world of Web Development. Please let me know if I can improve anything. I would love to get your suggestions.🥰

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adarsh Pratap•5,515
    @adarshcodes
    Posted over 1 year ago

    Hi @AryaDixit, first of all, welcome to this amazing community! You did nice work on this solution👏.

    Few things I've liked and noticed about your solution:

    Design aspect: Your design is very similar to the given design file. Only a couple of things I've noticed that you can change the font colors for the paragraphs.

    Responsive aspect: It's responsive and will work on most of the screens. Good work.

    Functionality aspect: It's working fine.

    Code: While everyone has their own style and approach to code few things make the code clear and clean and you really did amazing work on that.

    Accessibility and HTML Issue: You can check the report and you'll notice very small issues causing those issues, you can always fix that and regenerate the report here.

    You did amazing work👍. Keep practicing. Happy coding :)

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.

Oops! 😬

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

Log in with GitHub