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

Responsive News Page using CSS Grid

P
Aakash Dasgupta•360
@a-d14
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


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

I would like someone to check my website for accessibility and tell me if I missed something. I think the hamburger menu should be good (followed a video for that) but the rest of the website might need a little work.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Andrey•4,200
    @dar-ju
    Posted 7 days ago

    Hi, Aakash Dasgupta!

    Very cool work! The semantics are all excellent, the responsiveness is super, the layout is perfect.

    I looked at accessibility. You can immediately remember that if the button has no text or it is not clear what it does, then the aria-label should be filled in without thinking, while it should be clear what the button does, for example, not just Close, but aria-label="Close mobile menu", for hamburger - Open mobile menu. Let's look further, the Read more button - the inscription is there, it is clear, it refers to the block, here we do not specify anything for accessibility.

    And the second point, accessibility from the keyboard, needs to be checked. There is no focus on the links of the story-content blocks.

    Also. The section tag should have an h1-h6 heading, if the section does not have a heading, then you should think about using a section or div.

    Good luck with future projects, you are doing great!

    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 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