Fylo landing page with two column layout

Hello James,

Congratulation on completing this challenge.

Excellent Work! I have some suggestions regarding your solution if you don't mind:

HTML

• The action attribute specifies where to send the form-data when a form is submitted. Possible values: - an absolute URL or a relative URL

• For the alternate text of the testimonials avatar should not be User avatar. It’s meaningless, you can use the avatar name alt=" kyle burton".

• [look up a bit more about how and when to write alt text on images. Learn the differences with decorative/meaningless images vs important content] (https://www.w3.org/WAI/tutorials/images/decorative/) like icon-phone, icon-arrow, icon-quote, and icon-email are decorative. 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.

• Wrap the social icons in <a>. The links wrapping the icons must have aria-label or sr-only text indicate where the link will take the user. Then you set aria-hidden =”true” to the icons to be ignored by assistive technology.

• You may use the <address> tag to wrap the contact information for the author/owner of a document or an article (email and phone number.)

• Addingrel="noopener"or rel="noreferrer" to target="_blank"links. When you link to a page on another site using target=”_blank” attribute , you can expose your site to performance and security issues.

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

• Consider specifying the type of the button in the form to avoid any unexpected bugs.

• Use the<nav > landmark to wrap the footer navigation with aria-label=”secondary “ or aria-label=”footer”. 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. The nav 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. This will make it unique.you can read more in MDN

Aside these, Great work ! Hopefully this feedback helps.