Submitted over 2 years ago
Responsive Fylo landing page with two column layout
@jhonmicc
Design comparison
SolutionDesign
Solution retrospective
Please give feedback on my result landing page.
Community feedback
- @vanzasetiaPosted over 2 years ago
Hello there, Jhon! 👋
Congratulations on completing this challenge! 🎉
I have some feedback on this solution:
- Accessibility
- The first
section
of the page should not live inside aheader
. The only element that lives inside theheader
is thenav
element. So, the first section should live inside amain
landmark. Usually, the first section of the page is called hero section. - Wrap all the
section
elements withmain
landmark. - By doing those two things, the document or page structure should look like this:
- The first
<body> <header> nav element lives here... </header> <main> all section elements live here... </main> <footer> the last page content (e.g secondary nav, address, logo, etc)... </footer> </body>
- The alternative text for the logo should not be hyphenated. It should be human-readable.
- Also, alternative text for images should not contain any words that related to image (e.g. picture, photo, logo, icon, graphic, etc). It's already an image element so the screen reader will pronounce it as an image. 🙂
<button>Get Started</button>
Always specify thetype
of thebutton
. In this case, set the type of them astype="submit"
. It's going to prevent the button from behaving unexpectedly.- Create a custom
:focus-visible
styling to any interactive elements (button
, links,input
,textarea
). This will make the users can navigate this website using keyboard (by usingTab
key) easily. - Not all images need alternative text. These images are known as decorative images. So, for any decorative images, each
img
tag should have emptyalt=""
andaria-hidden="true"
attributes to make all web assistive technologies such as screen reader ignore those images. In this case, all images are decorative only except the logos. <h4>Kyle Burton</h4>
Don't skip heading level! Useh3
instead. Heading tags can be used by users of assistive technology to navigate the website. If headings are not in a logical order, those users might get confused.- Add
aria-label
to each social media link. Use the social media platform name as the value of thearia-label="Facebook"
. - The logo inside the
footer
element is also as important as the logo inside theheader
. - Use
rem
or sometimesem
unit instead ofpx
. Usingpx
will not allow the users to control the size of the page based on their needs. - Styling
- On
769px
width, the firstul
and the secondul
element are too close to each other. I would recommend adjusting the breakpoint for the media query. - I would recommend writing the styling using the mobile-first approach. It often makes me write less code.
- There's no error state for the email form. You can create form validation with only HTML and CSS. CSS Tricks has a great blog post about it. Also, add
required
attribute to theinput
element to prevent the user submits an empty value.
- On
I hope this helps! Happy coding! 😁
Salam kenal dari Lampung! 👋
Marked as helpful0@jhonmiccPosted over 2 years ago@vanzasetia Wow that's such great feedback for me, I got much knowledge 🙏. Thank you, Salam kenal dari Malang! 👋
1 - Accessibility
- @NaveenGumastePosted over 2 years ago
hay! Jhon Nice work
0 - @abdoachhoubiPosted over 2 years ago
Great work! Visually... But technically you still have some CSS errors that needs to be fixed, and also some accessibility issues...
0@jhonmiccPosted over 2 years ago@abdoachhoubi thank you man, I will see and fix it later
1
Please log in to post a comment
Log in with GitHubJoin 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