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

huddle landing page with alternating feature block

accessibility
kounik•300
@Valhalla-2
A solution to the Huddle landing page with alternating feature blocks challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


it was difficult for me to build the floating section , and make responsive .

  • what is best way to build the design ?
  • what would be the best practice to make element go on top of another using css position without damaging the design yet it should be responsive ?
  • Is my design look ok ?
  • Is my code too lengthy , is it readable ?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted almost 3 years ago

    Hi

    • I think you're misunderstanding html landmark elements here... Header is a landmark, like main and footer, so should go above the main. Inside this, you'd usually have a logo and a nav. But in this design there is no nav in the header, just a logo and a call-to-action, so you do not need the nav element there at all
    • "Try it free" would most likely navigate to a new page so should be an anchor tag, not a button element
    • A lot of the layout overlap in this is caused by large % paddings. Remember you can use things like gap in flexbox/grid and max-width to create a responsive layout. And you can use other flex properties like -grow -shrink and -basis, which I can see is used in a few places but with a lot of auto values and width still added.
    • Similarly, buttons (even though they should be anchor tags) should not have % widths applied. Instead, use padding in em to make them look right. Otherwise you lose all control over how those elements will look because you are forcing them to be a specific % width of their parent (whose width you also do not know)
    • Font size should never be in px. Convert to rem instead
    • Alt text shouldn't say things like "image" or "photo" in them as they already have an image role. This text should be an actual description of how an image looks if it is meaningful content
    • I think 600px is a little early to be switching to desktop layout. The layout appears really squished at 600px so consider making that change happen at a larger point when there is more space
    • Headings must go in order. You cannot have a h1 right at the end of the page
    • Icons like 'location' etc are decorative so should have empty alt like alt=""
    • There should be a nav in the footer with one unordered list, not two. You can use column properties on larger screens to split into multiple columns. Each of the items within it is clearly meant to be clickable navigation to other pages, so these all need to be anchor tags
    • Similar with social media icons - wouldn't you expect them to be clickable? So they need to be anchor tags and labelled accessibly
    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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub