Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

Submitted

Two Column Fylo Landing Page Built With CSS Flexbox & Mobile First.

#accessibility
Johnny 470

@johnnysedh3lllo

Desktop design screenshot for the Fylo landing page with two column layout coding challenge

This is a solution for...

  • HTML
  • CSS
2junior
View challenge

Design comparison


SolutionDesign

Solution retrospective


johnny says h3lllo once again, it's been a while since i submitted a solution. I've been heavily swarmed but it feels really good to submit this.

difficulties -this particular solution was a bit frustrating because i kept repeating myself in the CSS -i couldn't figure out how to get the form validation to work with just HTML & CSS.

uncertainty -I'm not exactly sure of my HTML in terms of semantics. -i repeated myself a whole lot 😅

questions -if you have an idea on how to validate forms with just HTML & CSS your comments would be very much appreciated. -if you have advice on better semantic HTML practices in this case please leave a comment. -does anyone have any idea in terms of better code refactoring practices? please i would appreciate all your feedback. thanks guys

Community feedback

Adriano 33,950

@AdrianoEscarabote

Posted

Hi Johnny, how are you?

I really liked the result of your project, but I have some tips that I think you will like:

1- All page content should be contained by landmarks, you can understand better by clicking here: click here

We have to make sure that all content is contained in a reference region, designated with HTML5 reference elements or ARIA reference regions.

Example:

native HTML5 reference elements:

<body>
    <header>This is the header</header>
    <nav>This is the nav</nav>
    <main>This is the main</main>
    <footer>This is the footer</footer>
</body>

ARIA best practices call for using native HTML5 reference elements instead of ARIA functions whenever possible, but the markup in the following example works:

<body>
     <div role="banner">This is the header</div>
     <div role="navigation">This is the nav</div>
     <div role="main">This is the main</div>
     <div role="contentinfo">This is the footer</div>
</body>

It is a best practice to contain all content, except skip links, in distinct regions such as header, navigation, main, and footer.

Link to read more about: click here

2- Why it Matters

Navigating the web page is far simpler for screen reader users if all of the content splits between one or more high-level sections. Content outside of these sections is difficult to find, and its purpose may be unclear.

HTML has historically lacked some key semantic markers, such as the ability to designate sections of the page as the header, navigation, main content, and footer. Using both HTML5 elements and ARIA landmarks in the same element is considered a best practice, but the future will favor HTML regions as browser support increases.

Rule Description

It is a best practice to ensure that there is only one main landmark to navigate to the primary content of the page and that if the page contains iframe elements, each should either contain no landmarks, or just a single landmark.

Link to read more about: click here

The rest is great!!

Hope it helps...👍

Marked as helpful

0

Johnny 470

@johnnysedh3lllo

Posted

thanks Adriano, this is really helpful

1

Please log in to post a comment

Log in with GitHub
Discord logo

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