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

News-homepage-main

accessibility, web-components, webflow, animation
ADENEKAN OKIKIOLUWA•330
@OA2302
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


please rate my work

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gustavo Gutiérrez•360
    @gustavo2023
    Posted about 1 month ago

    There are a couple of issues I noticed in your project:

    • First, it seems you are not using the correct font-family for the project.
    • There is an error when you close the sidebar because the goBack() function is not defined.
    • Instead of using a <div> element with a .nav class you should instead use a more semantic element like <header>. This helps improve the structure and navigation for assistive technologies.
    • You shouldn't use more than one <h1> heading on the same page. The <h1> tag is meant to represent the main heading or the most important title of the page. Having more than one <h1> can make the document's structure confusing for assistive technologies like screen readers, which rely on heading levels to navigate the content.
    • You also shouldn't skip heading levels. Skipping heading levels (e.g., going directly from <h1> to <h3> without an <h2>) can make it hard for screen readers to convey the content hierarchy to visually impaired users. They might not understand the relationship between sections or subsections.

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