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

Responsive Landing Page using CSS Grid and Flexbox

accessibility
James•160
@jameschein
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


// I read somewhere it's OK to use an anchor element as a parent to multiple child elements. Was wondering if this is accepted practice?

// I have chosen to not use css background images but only img elements [also picture/ figure/ etc]. I have used 'aria-hidden=true' to hide decorative imagery for inclusivity. I fear I may been a little over-zealous here. Any thoughts?

// I have converted supplied imagery with web versions - is this permitted within the brief?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dusan Brankov•860
    @dusan-b
    Posted over 2 years ago

    Hello James,

    I just looked at your code and I like your approach towards web accessibility and semantic HTML. However, there are some changes I would consider.

    I see you've used the <a> element for your menu button. Instead you should use the <button> element, since its purpose is to perform an action (opening and closing the menu). Anchor elements are only there to navigate you to another page. Otherwise keyboard users wouldn't be able to go through the menu when it's hidden, and visually impaired users would get confused when using a screen reader.

    Another thing is, it's unfortunately not valid (yet) to specify the aria-hidden attribute on <picture> elements. A reasonable solution would be to leave the alt attribute empty. It's acutally even better this way, since this method has been established a lot longer and will be accepted by more assistive technologies. But keep in mind, this is only applicable to decorative images.

    Also, the <main> element should contain all the content which is unique to the page, in this case everything except header and footer. Otherwise you would keep getting the warning "All page content should be contained by landmarks".

    I hope this helps. Keep up the good work!

    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