Fylo landing page with two column layout using SASS

Hi Dodeun, Glad it was helpful.

• Hiding Content for Everyone:display: none;hides the content but also removes it from the accessibility tree so screen readers won’t read it similar to hidden attribute.
• Hiding Content for Screen Readers: aria-hidden="true"
• Showing Additional Content for Screen Readers: To hide content visually while keeping it in the accessibility tree for screen readers:

.sr-only {
  border: 0; 
  clip: rect(0 0 0 0); 
  height: 1px; 
  margin: -1px;
  overflow: hidden;
  padding: 0;
  position: absolute;
  width: 1px;
}

Hopefully this makes it clear. Happy coding!

Hello Dodeun,

Congratulation on completing this challenge. Excellent work! I have few suggestions regarding your solution, if you don't mind:

HTML

• look up a bit more about how and when to write alternate text on images. Learn the differences between decorative/meaningless images vs important content like icon-phone, icon-arrow , icon-quotes and icon-email.... For decorative images, you set an empty alt to it with an aria-hidden=”true” to remove that element from the accessibility tree. This can improve the experience for assistive technology users by hiding purely decorative images.
• Forms with proper inputs and labels are much easier for people to use. To pair the label and input, one way is an explicit label’s for attribute value must match its input’s id value. Input fields without accompanying labels can lead to accessibility issues for those who rely on screen readers. If a screen reader comes across an input field without a label it will try to find some accompanying text to use as the label. (To hide the label visually but present for assistive technology, you may use sr-only class ).
• For class="contacts", you may use like <address> ... tag to wrap the contact information for the author/owner of a document or an article (email and phone number). By adding semantic tags to your document, you provide additional information about the document, which aids in communication.
• Instead of using a generic div to wrap the links class="internal-links" , you put your links within an unordered list structure so that a screen reader will read out how many things are in the list to give visually impaired users the most information possible about the contents of the navigation.
• The social icons need interactive elements around them which is <a> like: <li><a href=”#” aria-label=”visit our facebook ”> <i class=”fab fa-facebook”></i></a></li>
• Links must have discernible text. The social links wrapping the icons must have aria-label or sr-only text indicate where the link will take the user. Your icons are purely decorative, you'll need to manually add an aria-hidden attribute to each of your icons.
• You can have a look on my solution , it might help. If you have any suggestions, please do leave a feedback.

Aside these, you did great work. Hopefully this feedback helps.