Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

News_Homepage_HTML_SCSS_GRID_TYPESCRIPT

sass/scss, typescript, bem
P
Julien Gilbert•500
@juliengDev
A solution to the News homepage challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time? Accessibility Features

Accessibility has been a priority throughout the site. Here are the key implementations:

  • Semantic Elements: Proper use of HTML5 elements ensures logical content organization.
  • ARIA Attributes:
    • aria-expanded and aria-hidden to indicate the state of the mobile navigation menu.
    • aria-label and aria-labelledby for descriptive labels on links, sections, and images.
  • Screen Reader Support:
    • sr-only class hides visual elements but keeps them accessible to screen readers.
    • Navigation links and buttons are descriptive and provide context for their actions.
  • Keyboard Navigation: The site is fully navigable via keyboard, with logical focus order and interactive elements like buttons and links.

Handling Responsive Navigation with the Burger Menu

The responsive navigation is managed using a burger menu for mobile devices. Here’s how it works:

  1. Checkbox Input: A hidden <input type="checkbox"> element toggles the menu's visibility.
  2. ARIA States:
    • aria-expanded dynamically updates to reflect whether the menu is open or closed.
    • aria-controls links the toggle button to the corresponding navigation element for assistive technologies.
  3. CSS Styling:
    • The sidebar (<aside>) is styled to be off-screen by default and slides into view when the checkbox is checked.
    • Media queries ensure the desktop navigation (<nav class="desktop-nav">) is displayed instead of the burger menu on larger screens.
  4. Progressive Enhancement: The approach ensures that the menu is usable even if JavaScript is disabled.

This implementation ensures that the navigation is both responsive and accessible across a variety of devices and user needs.

What challenges did you encounter, and how did you overcome them?

This is the first time I build an Animated Hamburger Menu With Only CSS, hopefully I was able to follow some youtube tutorial to get some help. It was fun to do.

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

Feel free to give my any feedback :) much appreciate

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 Julien Gilbert'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 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.