Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

Huddle responsive landing page with flexbox

Alex•95
@ImmuneMoon
A solution to the Huddle landing page with a single introductory section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


New to HTML/CSS, I'm sure this is probably messy and there are better ways to do this. Still working on the accessibility/ HTML issues, if you have suggestions I'd love to hear them, thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great job on this. It would be a lot easier if you deployed this on github pages, that way we could inspect the layout easier. But still, the layout in desktop looks fine and mobile as well.

    Some suggestions would be:

    • The img for the website-logo should have used alt="huddle" as an attribute, the image already has the text so better using it as the alt value.
    • The alt for the image in the hero-section should be using alt="". Also, when you use img element, always use the alt attribute. If the image is just decoration, use alt="" on it, but if the image adds content, then use a meaningful alt value, always have that alt.
    • I think the register would be a lot great if it was an anchor tag a, since there aren't any modal popups on this one where button is used.
    • The a tag that wraps each social media link should have aria-label and the value of that attribute is the name of the social media. For example, the a tag that wraps the facebook icon should be:
    <a href="facebook.com" aria-label="facebook" />`
    

    This way, users will know where this link would take them. Use them on the other a tag as well. You use this attribute, if the element have no text-element inside it.

    Aside from those, great job again on this one.

    Marked as helpful
  • Lesego•95
    @lesego16
    Posted almost 4 years ago
    1. Try fixing ACCESSIBILITY ISSUES and HTML ISSUES

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

Oops! 😬

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

Log in with GitHub