fylo-landing-page-with-two-column-layout-

Community feedback

• 

  PhoenixDev22•16,950

  @PhoenixDev22Posted about 2 years ago

  Hi Blakky,

  Excellent work! I have some suggestions regarding your solution:

  HTML

  • Use the <nav > landmark to wrap the navigation instead of generic div .nav

  • The logo's alternate text is needed on the logo image . You can use the website's name as an alternate text. You may set alt=”Fylo". If you are going to leave the logo not wrapped by <a>, it’s better to place it out the <nav> as it does not navigate the user in anywhere (only an image).

  • Instead of using a generic div to wrap the links class="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.

  • 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 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.

  • When you use the<nav > landmark to wrap the footer navigation , you should add aria-label=”secondary “ or aria-label=”footer” to it . A brief description of the purpose of the navigation, omitting the term "navigation", as the screen reader will read both the role and the contents of the label. Thenav element in the header could use an aria-label="primary" or aria-label=”main” attribute on it. The reason for this is that, you should add the aria-label for a nav element if you are using the nav more than once on the page.you can read more in MDN

  • Use <form> to wrap the class="input".

  • 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 ).

  • It’s recommended to specify the type of the button, in this form the button type is type=”submit”.

  • Profile images like that avatar are valuable content images, not decorative .For the alternate text of the avatar testimonial should not be empty. You can use the avatar’s name alt=" kyle burton". The alternate text should not be hyphenated, it should be human readable.

  • You may use like to use <address> tag to wrap the contact information class="address" 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.

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

  Marked as helpful

  1
• 

  Blakky•310

  @BlakkyWebPosted about 2 years ago

  Thanks for your feedback, I would surely implement your suggestions

  0