Design comparison
Solution retrospective
I learned a bit more about formularies, and I used for the first time the flexbox property order. It was awesome haha.
Community feedback
- @LilithNixxPosted almost 2 years ago
It shows this error: -angle,-180deg))}}@-webkit-key but it doesn't exist in my code. The same with the other css "errors"
Then it asks me to add a h1 or other h to the sections but they are just dividers, I didn't add a div to give it a sense.
Finally, it asks me to add a text to the a but I don't want a text I want an icon.
0@MelvinAguilarPosted almost 2 years ago@LilithNixx Hi!!! I'll answer if you haven't been able to solve it yet
-
"Links must have discernible text": You should use the
aria-label
attribute to describe the links if they don't have visible text, this will help screen reader users to understand the purpose of the link.e.g.
<a href="#" aria-label="Facebook"><i class="fa-brands fa-instagram"></i></a>
- "CSS: "transform": too few values for the property "transform".": Don't worry about this error, it's generated by using the FontAwesome kit so you can ignore it or just download the icons you need.
- "Section lacks heading. Consider using "h2"-"h6" elements to add identifying headings to all sections." The section tag has a semantic meaning and to separate sections of a web page, it is recommended to add a title to provide a clear and concise description of the content that follows in each section:
<section> <h2>Our Team</h2> <div class="team-members"> </div> </section>
For example, using a <section> tag to wrap the image is not very appropriate, you can use a div instead.
Marked as helpful1 -
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